Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tapestry Wiki" for change notification.
The following page has been changed by superoverdrive: http://wiki.apache.org/tapestry/WishList ------------------------------------------------------------------------------ + Toby: + + There should be a way in Tapestry5 to create input fields dynamically, e.g. by reading the configuration from a database in order to achieve + dynamic input fields. + + An example of a data model that would allow this is here: + + Category + + ||ID || Name + || + ||1 || Country + ||2 || Language + + + Value + + ID Name Category_fid + + 1 USA 1 + 2 UK 1 + 3 Spain 1 + 4 English + 5 Spanish + + + + FormElement + + ID NAME Category_FID MINOCCURS MAXOCCURS + 1 ResidentCountry 1 1 1 + 2 CountryOfOrigin 1 1 1 + 3 TravelDestinatiopns 1 0 10 + 4 SpokenLanguages 1 1 10 + + + Form + + + ID NAME FORM_FID + + 1 UserRegistration + + + FormFields + + ID FORM_FID FORMELEMENT_FID + + 1 1 1 + 2 1 2 + 3 1 3 + + + + + RichardL: Is there any chance that a dynamic block component similar to the one at http://www.behindthesite.com/blog/C1931765677/E1630021481/ could added to the contrib library in Picasso please? Dynamic blocks add a huge amount of power and flexibility to Tapestry because far more complex page logic can be expressed more clearly and efficiently with OGNL (or, indeed with Java via an OGNL call) than with the built in blocks, render blocks and conditional components. I have a dynamic block component implementation that I could probably donate (subject to clearance from my employer) that is a bit more functional than the one mentioned above (it's a similar implementation but it supports default parameter values in dynamic components and allows dynamic components to be referenced by direct links along with some other enhancements). Unfortunately, because dynamic blocks need to use the internals of Tapestry to function, the implementation is quite sensitive to changes to the Tapestr y framework so it would be much better if a dynamic block could become a part of Tapestry, along with an associated set of unit tests. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
