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 ErikVullings: http://wiki.apache.org/tapestry/WishList ------------------------------------------------------------------------------ * It would be great if there was a way to carry through form parameters. Say I have pages A and B. B is a general purpose page used to lookup information. It should be possible to navigate from A to B back to A and keep the form parameters of that were set in A. At the moment you would need to make B record the values in hidden fields then submit them back to A or use persistent properties. It would be great to be able to automatically pass these parameters along without making B explicitly aware of A's parameters since B might be used in other contexts. Hope that makes sense. It's hard to explain. * Allow use of "id" attribute instead of "jwcid", so that templates are truly pure HTML. Perhaps even make the scheme for tagging the binding name flexible. * The biggest issue I have had (and have seen a lot others have) is with pleasing the rewind cycle. The rewind has to be completely transparent which means we should by default make all form elements serialize their state in hidden fields and allow the user to opt out. + * Get ride of page specifications - I've got 13 pages, all listed in App.application, all with Page.page files with just one line: <page-specification class="app.Page"/>. Perhaps I use anonymous components too much, and page-specifications would be needed for more complex pages, but it'd be great for trivial pages not to have to jump through these hoops and instead get auto-looked up by package (e.g. put app.pages.* in App.application as an auto-lookup package) Many of these wishes are already being acted upon, see ["Tapestry31"]. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
