cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christofer Dutz" <d...@c-ware.de>
Subject AW: paged cforms
Date Sat, 20 May 2006 13:54:50 GMT
Hi,

 

Unfortunately the union-stuff works for separate widgets. A repeater is one
single widget. No matter how many entries it has, so you can't page it using
this approach.

On the other side I would recommend evaluating if CForms is necessary. While
working on a logistic portal using CForms using a repeater only to display
information and perform simple actions on the rows (delete, actions on
selected rows) and not to directly edit them, I found out, that avoiding
CForms for the big tables speed up my application about 14 times. I then
could use very simple techniques to implement paging.

 

As someone else on this list mentioned there are some attempts to implement
paging repeaters, don't know how work is proceeding.

 

Chris

 

  _____  

Von: Lee Carroll [mailto:leecarroll150@aol.com] 
Gesendet: Samstag, 20. Mai 2006 12:23
An: users@cocoon.apache.org
Betreff: RE: paged cforms

 

hi Chris,

Thanks for the response.

 

My form is a repeater, with a variable length depending upon the number of
records in the db table. I'd page say after 20 records?

 

The union approach looks cool but as you say would not work here.

 

lc

 

 

 


Mime
View raw message