You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by ta...@jakarta.apache.org on 2004/04/06 01:38:48 UTC

[Jakarta Tapestry Wiki] Updated: WishList

   Date: 2004-04-05T16:38:46
   Editor: ErikHatcher <eh...@apache.org>
   Wiki: Jakarta Tapestry Wiki
   Page: WishList
   URL: http://wiki.apache.org/jakarta-tapestry/WishList

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -8,5 +8,6 @@
  * 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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org