Howard Lewis Ship <hlship <at> gmail.com> writes: > So I've been thinking that the template files should get away from a > ".html" extension and settle on something Tapestry specific (rather > than content specific), such as ".t", ".tt", ".tsp" (Tapestry Server > Page ), ".tap", etc.
Using some unknown extension will prevent some HTML editors from listing the files in the Open File dialog and thus creates inconvenience in editing or previewing. I'd suggest a service configuration listing those extensions that are to be tried when looking for the template. By default the list should include: .html, .htm, .wml, .svg. > http://...//folder/page > http://..//folder/page/context0/context1/context2 > > Which I kind of like. In other words, the point where the page name > ends and the context begins will be determined based on the available > set of pages (in folders). Then we have to make sure if we have a page P1, then we are prohibited from having a folder named P1, otherwise we won't be able to tell http://...//folder/P1/P2 is referring to P2 inside folder P1 or just page P1 with context=P2. -- Kent Tong Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
