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 Fri, 19 May 2006 09:42:24 GMT
Uuuuppps … just a smalll bug here ;)

 

                        <fd:union id="view" case="viewType">

                                   <fd:widgets>

                                               <fd:struct id="page_1">

                                                           <fd:widgets>

                                                           ….

</fd:widgets>

                                               </fd:struct>

                                               <fd:struct id=" page_2">

                                                           <fd:widgets>

                                                           ….

</fd:widgets>

                                               </fd:struct>

                                               <fd:struct id=" page_3">

                                                           <fd:widgets>

                                                           ….

</fd:widgets>

                                               </fd:struct>

                                   </fd:widgets>

                        </fd:union>

 

Chris

 

[ c h r i s t o f e r   d u t z ]

IT-Berater
univativ GmbH & Co. KG
Robert-Bosch-Str. 7, 64293 Darmstadt

fon:  0 61 51 / 66 717 -0
fax:  0 61 51 / 66 717 -29
email:  christofer.dutz@univativ.de
 <http://www.univativ.de/> http://www.univativ.de

Darmstadt, Stuttgart, Karlsruhe, Düsseldorf

 

  _____  

Von: Christofer Dutz [mailto:dutz@c-ware.de] 
Gesendet: Freitag, 19. Mai 2006 11:33
An: users@cocoon.apache.org
Betreff: AW: paged cforms

 

Hi

 

If you are using just a big form, then you can use unions to achieve paging.
Note that this doesn’t work if you want pages for a large repeater.

For the big-form-paging you simply use the following structure:

 

                        <fd:field id="viewType">

                                   <fd:datatype base="string"/>

                                   <fd:selection-list>

                                               <fd:item value="page_1">

                                                           <fd:label>Page
1</fd:label>

                                               </fd:item>

                                               <fd:item value="page_2">

                                                           <fd:label>Page
2</fd:label>

                                               </fd:item>

                                               <fd:item value="page_3">

                                                           <fd:label>Page
3</fd:label>

                                               </fd:item>

                                   </fd:selection-list>

                        </fd:field>

                        <fd:union id="view" case="viewType">

                                   <fd:widgets>

                                               <fd:struct id="details">

                                                           <fd:widgets>

                                                           ….

</fd:widgets>

                                               </fd:struct>

                                               <fd:struct id="details">

                                                           <fd:widgets>

                                                           ….

</fd:widgets>

                                               </fd:struct>

                                               <fd:struct id="details">

                                                           <fd:widgets>

                                                           ….

</fd:widgets>

                                               </fd:struct>

                                   </fd:widgets>

                        </fd:union>

 

You can then make a button to update the hidden widget “viewType” which
submits on change and you have what you want.

 

Hope this helps,

            Chris

 

[ c h r i s t o f e r   d u t z ]

IT-Berater
univativ GmbH & Co. KG
Robert-Bosch-Str. 7, 64293 Darmstadt

fon:  0 61 51 / 66 717 -0
fax:  0 61 51 / 66 717 -29
email:  christofer.dutz@univativ.de
 <http://www.univativ.de/> http://www.univativ.de

Darmstadt, Stuttgart, Karlsruhe, Düsseldorf

 

  _____  

Von: Lee Carroll [mailto:leecarroll150@aol.com] 
Gesendet: Freitag, 19. Mai 2006 10:28
An: users@cocoon.apache.org
Betreff: paged cforms

 

Hi I'm using xsp generated xml to bind to a cform model. On submit of the
form i use a save xsp to update the backend. 

 

The form presents a lot of data entry and would benifit from paging the
data. On each submit the flowscript would need to present the next part of
the data until all done.

 

Has anyone done anything like this ? It sort of sounds like a commom problem
which people may well have solved ?

 

Any pointers greatly appreciated

 

lee c


Mime
View raw message