Hello, The only one of these that I'm interested in is the ability to have class-less components (just markup, no logic). I filed an issue for this many months ago, and am no longer certain where in the mix it is. I'll add one:
Configurable URL-mapping service. I loathe - /loathe/ the fact that I have no control over the URL structure, and that it directly reflects the page class structure of the applications. There are simply cases where I want to have some kind of routing/rewriting feature, not to mention that management will at times demand control over such a thing. Tobias Marx wrote: > Hi there! > > Here is my list of Tapestry5 suggestions: > > > Tapestry5 Suggestions: > > 1. User .tpl instead of .tml. This way there is also no problem with syntax > highlighting in most editors. > > > 2. Make those templates compatible with SSI templates. > > This is because most HTMLers will slice PSD files to SSI templates. > This way, they could directly be used in a Tapestry project > > 3. Make the Layout component the default component that is always used if not > otherwise specified. > This saves 2 lines of code in all page templates. > > 4. Allow the use of templates without having to have a corresponding Java > class for it. > > Otherwise you to generate tons of "stupid" empty Java classes. > > > > What do you think? > > Thanks! > > Toby > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- http://thegodcode.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
