5. resolving template/component class names:
This one seems interesting, certainly some variation in the allowed naming conventions seems nice if it's configurable (e.g. a naming strategy) > > > 1. User .tpl instead of .tml. This way there is also no problem with > > syntax highlighting in most editors. > This one seems quite arbitrary, .tml seems just as tood as .tpl, which "most editors" are you talking about ? > > 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 > > > Can you give an example of how a template might be "compatible" with an SSI template ? > > > 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. > A step further : it would be nice if a page could specify either in the template or in the java class which border component to use. Grails for example uses Sitemesh layouts, and each rendered page (gsp) can specify the layout to use . > > > > > 4. Allow the use of templates without having to have a corresponding > Java > > class for it. > This would certainly be nice, as on a small project that I do (that for now only has little functionality) I already have a whole bunch of dumb java classes. I'll file feature requests for these in a couple of days if there are no objections from the list members. Cheers, Alex Kotchnev
