It is 1:1 the text from the mailing list as far as I remember..just with a formatted table on the Wiki.
So you mean it could work by extending BeanEdit Form? Anyway, so I think, considering the time to do this, it was a good decision to use Wicket for this part and T5 for the frontend part...so combining the best of both worlds....otherwise it would have taken too long. Maybe I replace this later on by T5 too if this should become a feature of T5.... I am not a T5 developer, just a casual T5 "user" - I can only contribute by making suggestions and pointing out stuff I have noticed... Thanks for your reply.... > For others' reference, your addition is: > http://wiki.apache.org/tapestry/WishList?action=diff&rev2=98&rev1=94 > > I think what you ask is feasible: it's not that different from what is > done by BeanEditForm, just the source of the field list is not > determined by reflection but loaded from an external source. > I agree it would be a nice addition to T5, but it has not been done yet. > > The point is: you are asking for a new feature (and a large one, I 'd > say), so you cannot expect a simple answer on the mailing list. Look at > JIRA improvement issues, to find out whether this has already been > requested by someone else. If not, submit a new Issue, describing with > the greatest detail how the new feature should work. Then you can ask > the mailing list to vote for your issue, and ask the developers to > consider it. Or if you feel brave enough, write it yourself and submit > it for inclusion. > > That's how things are done in OS projects... > > Angelo. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
