On Wednesday, Oct 9, 2002, at 01:41 Europe/Zurich, marc fleury wrote:
> 1- I don't want to declare the 200 pages that make up my "website" > application. This is cute for 1/2/3 pages and really makes my nerves > go > "whoooom" when I think about the 200 pages I have > > 2- I don't want to write a .page for all my html and include my > "template" component for every fucking page I have in my system. Right... Then Tapestry is perhaps not what you are looking for. Try JSP. Or static HTML. Everything is nicely dumped in one html page. The point of something like Tapestry is to build an handful of components that you can reuse all over the place instead of having to deal with "200 pages that make up my 'website' application". If there is no reuse and your "200 pages" are utterly different, without anything in common whatsoever, then forget about a component base system like Tapestry. Using systems like Tapestry or WebObject is to avoid to have to deal with html altogether: you don't write any html, you let the system generate it for you. This implies that you can turn your application into a discreet set of components that can be combine and reuse programatically. Maybe this is not your case. PA. ------------------------------------------------------- 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
