One year ago I've posted a solution to load your template from a database, or generate it dynamically in Tapestry 3. I think that it wouldn't be too different in T4. When I say "dynamic", I only mean only once, because of the page pooling thing. You can do a good abstraction to create your templates. If tapestry wants to implement really dynamic form generation, it will have to provide some way to mark a page as not poolable, or store components as it do with persistent properties.
On 3/3/06, Apache <[EMAIL PROTECTED]> wrote: > > I think Tapestry already makes a big step forward > but still there is a lot of things that could be made more dynamic and > free programmers of templates and component definitions. > > In my opinion everything could be in the database instead of configuration > files. > > In my idea world there should only be Java Classes > and no XML/Html/Page files. > > I only want to tell the system to "genrate a form with the fields I tell > you" and to tell it which fields are editable - the rest should be done > automatically. Maybe you could tell how to order or align them, but I dont > want to write any html templates. > > > -------------------- m2f -------------------- > > Sent from www.TapestryForums.com > > Read this topic online here: <<topic_link>> > > http://www.tapestryforums.com/viewtopic.php?p=14479#14479 > > -------------------- m2f -------------------- > > > >
