Re: [Ginp-developers] Char Encodings.

[Justin <ju...@sq...>]

Doug,

	Here's a pretty good article on The Server Side (a popular java news 
forum) about switching to Tapestry... Pretty much positive.  Basically, 
it's a paradigm shift but it's worth it.  A lot of people seem to be 
wondering about their switch to JDO and how it lacks vs. Hibernate though.

http://www.theserverside.com/news/thread.tss?thread_id=31313

I know you were interested in letting people customize the look and feel 
so I thought you might find the following interesting:

<i>

The big effect of using Tapestry (and also XMLC btw) for us has been 
that it allows our web designers to be integral in the whole UI design 
process. Real separation of concerns.

Tapestry and XMLC pages are *plain* HTML. With a jsp page, it becomes 
much more difficult to maintain the page visually. The jsp stuff gets in 
the way of the HTML designer, whereas for the developer the HTML is just 
something to be tolerated. And you *really* dont want a coder handling 
the visuals. It is definitely a different skill from coding.

It may be *possible* to do it all in JSP, but is it *easy*? That greatly 
affects maintainability, error counts, etc.

Kit

</i>

I think you can move the tapestry files out of the classpath in the 
latest version 3.1.

Regards,

	Justin