I don't like making the HTML templates visible in the web context; a clever end-user may be able to get the template directly, though what they would do with that is anyone's guess (one of the advantages of not having any code in the HTML template).
-- [EMAIL PROTECTED] http://tapestry.sf.net > [EMAIL PROTECTED] wrote: > > > There's an advantage to moving the HTML files out in the > > the web context space ... so that relative references to > > assets work during development (in a WYSIWYG editor). > > Point well taken on .jwc. I also get why you might want all files in the > same location, though my impression is that having the html in a place that > permits relative references would be enough to convince me to use that > approach. We shall see. As with any framework I will figure out my > efficiency preferences as I become more familiar. > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
