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/Tapestry41WishList ------------------------------------------------------------------------------ ----- - * '''Better Documentation''' This one is pretty obvious. The current documentation covers a lot, but there are a few places with either stale/missing information that need to be filled in. + * '''Better Documentation''' This one is pretty obvious. The current documentation covers a lot, but there are a few places with either stale/missing information that need to be filled in. It freely mixes deprecated 3.0 features in a way that's quite confusing -- these should be clearly separated, not littering the path. Furthermore, the material is organized more from the point of view of the app's architecture than from the point of view of the user: it is often necessary to skip around between several pages to gather the information for a single task. (For example: how do I build a validated field with annotations? How does one integrate Javascript?) Documentation should start by clearly describing the simplest, best way of accomplishing something, then fan out to the details. (The Hibernate docs do a better job of this; they're a good place to look for an example.) * '''Easier Testing''' There is a rather large and impressive set of very helpful testing classes that exist in Tapestry already, the only problem is that they aren't released as a library that anyone other than the Tapestry devs can use! (besides Creator) A new Tapestry testing library is already in the works [http://howardlewisship.com/tapestry-javaforge/tapestry-testng/ here]. A javascript test base has already been added to 4.1, but it is hoped that a completely seperate library can be created complete with documentation on how to do common tasks. - * '''Default Page/JWC Files and/or Page/JWC Inheritance''' Often there is a need to use the exact same services/beans/etc one multiple pages. The current solution is to add them to all the page/jwc files. There should be a way to inherit another page/jwc file and/or simply import another page/jwc file's settings. + * '''Default Page/JWC Files and/or Page/JWC Inheritance''' Often there is a need to use the exact same services/beans/etc one multiple pages. The current solution is to add them to all the page/jwc files. There should be a way to inherit another page/jwc file and/or simply import another page/jwc file's settings. (Note that this is already possible with annotations.) * '''Switch Default Binding for .html to ognl:''' Having ognl: as the default binding would be a welcome change (and improve portability from .page -> .html - this makes sense as .pages seem to be on the way out and consistency/convention is always a +). @@ -34, +34 @@ * '''Make custom Page Not Found easier''' Separate a NotFound.page from Exception.page, allowing a simple definition of a NotFound.page & NotFound.html in the webapp. Perhaps also make it configurable for the page to set a HTTP error code. + * '''Aggressively reduce verbosity and repetition''' Page templates are very verbose compared to most other templating languages. (The default 'ognl:' binding might be a good start, but won't solve the issue by itself.) Many component bindings involve unacceptable repetition: for example, the common case of a field with a translator and validator declared in an annotation involves redundant declaration of many things (such as the type of the component) which Tapestry should be able to infer. In general, Tapestry needs a lot more of the "don't repeat yourself" attitude. + + * '''Ad-hoc / undeclared properties''' One of the few features of JSP I miss is the ability to declare an ad-hoc property for use as the iteration value in a loop. Tapestry requires the page to declare a property for a For's value, even if that value has no meaning outside the template. + --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
