cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antonio Gallardo <agalla...@agssa.net>
Subject Re: Design help/questions for cforms application
Date Thu, 19 Jan 2006 23:55:04 GMT
Hi Duncan,

using flow and jumping between screens, see the calculator demo:

http://cocoon.zones.apache.org/demos/release/samples/flow/

In the same way is posible to use cforms.

Best Regards,

Antonio Gallardo.

Duncan McLean wrote:

>Hi Thanks again
>
>I'd like to ask a further question:
>
>Effectively, there is a set of 7 forms that are distinct from each other
>in as much as they capture different data, but are still logically linked
>(i.e previous input effects behaviour in subsequent forms and their
>handling, and the final result will be that all captured data is gathered
>and sent to be calculated and a result returned).
>
>Can someone give me an example of how this is achieved in flowscript - I
>seem to be getting a bit mixed up, and cannot really find a good example
>of something like this. Will the same function in flowscript handle the
>transitioning from one form to another, or do I use a separate function
>for each form, in which case how is the overall data collected at the
>conclusion/final submission of the form.
>
>Apologies again but I'm new to Cforms and conceptually its taking time to
>get up to speed!
>
>Thanks
>
>Duncan
>
>
>
>
>  
>
>>Duncan McLean wrote:
>>    
>>
>>>So can anyone take my other question - can someone explain the uses of
>>>data binding in forms (java bean or xml) citing some examples of where
>>>it might be useful? (I guess I am interested in what gains it could give
>>>us in our situation)
>>>      
>>>
>>I'll take a stab at it briefly...
>>
>>The CForms binding framework is simply a way to map values back and
>>forth between the form model (essentially a tree structure of widgets)
>>and a "business object".  For instance, your business processing layer
>>probably already defines JavaBeans for transferring data around, but the
>>CForms form object has a different structure.  So once a user fills in
>>the form object with their values, somehow those values need to get
>>mapped onto the JavaBean.  A binding allows you to define the rules for
>>how those two specialized objects' contents can be synced up.  You could
>>of course do it manually by copying the values over one-by-one in your
>>Java/JS code, but the binding framework lets you define the mapping
>>declaratively in an XML format, which can be more convenient.
>>
>>Hope that's a good start.
>>--Jason
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>>For additional commands, e-mail: users-help@cocoon.apache.org
>>
>>
>>
>>    
>>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>For additional commands, e-mail: users-help@cocoon.apache.org
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message