You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Apache Wiki <wi...@apache.org> on 2007/06/30 06:17:15 UTC

[Tapestry Wiki] Update of "WishList" by ErikVullings

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

------------------------------------------------------------------------------
   * Listener methods that take actual typed parameters rather than having to pull them from service parameters
   * Cleaner URL's, to really help with ["J2EESecurity"]
   * Easier testability of Tapestry pages/components
+  * Fix for security hole in asset service
+  * Allow simpler validation - for example, bypass invoking listener method and return to same page if validation errors occur
+  * Better support for hot deploy, allowing new page and component templates/specifications to be picked up at runtime.  WebOGNL has a timestamp dependency check, which would be nice to borrow from.
+  * Let the component user be able to set the template for the component just as easily as set a paramemter.
+  * For component beans, add a set-static-property type of capability, instead of shoehorning in a string using an expression setter.
+  * Unified the way to process validation, make all form components support displayName property and be able to support validator. Let the FieldLabel highlight the label automatically when the field is required.
+  * 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.
  
+ Many of these wishes are already being acted upon, see ["Tapestry31"].
+ 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org