tapestry-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fran├žois facon <fra.fa...@gmail.com>
Subject Re: Components architecture
Date Tue, 01 Mar 2011 20:05:32 GMT
Hi Sandeep,

Have a look at http://jumpstart.doublenegative.com.au/jumpstart/
It 's a good entry point to see tapestry in action.

if you need multi part in your form perhaps you will need formfragments.
for that see

or http://tapestry-test.appspot.com/formfragmentdemo


2011/3/1 Novice <sandeep.kunwar@gmail.com>

> Hi all,
> Well I am a novice and pardon me if I sound dumb.
> As per my understanding Tapestry is Component oriented architecture.
> But what exactly does component mean? is it just collection of basic
> elements in a form on a single page?
> Because I developed few components which are basically some sections of a
> big form.
> Now I am finding it very difficult to include components(collection of
> basic
> elements) in a page under 1 form.
> In summary, my page = FORM(Cmp1 + Cmp2) where Cmp1=Text1 + text2 etc
> Management of same and validations etc are making it difficult.
> Any suggestion or pointers will be highly appreciated.
> Regards
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Components-architecture-tp3405514p3405514.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message