First off, whatever solution comes up, I won't be throwing away anything in Tapestry. The prefered and most powerful way to develop is what's currently in 2.2.
Second, I like the idea, in this "RAD" approach, that the HTML files be in the web application context, so that relative URLs to stylesheets and images be natural. Easier for the new adopter. -- [EMAIL PROTECTED] http://tapestry.sf.net > In regards to Tapestry RAD being able to load *.html and wrap it with a > generic specification. What about adding a : > > <SEARCH PATH="/net/sf/tapestry/mypages"> > > Which would search the indicated package for raw HTML without a > corresponding jwc or page and wrap it. This way You don't need to throw out > the existing Tapestry just to get simplicity. This would work fairly easily > (I think, then again, I'm not the one who has to program it... It always > looks so easy when someone else has to do it :-) > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
