I'm job hunting right now which means I sometimes have to explain why I chose
Tapestry for a web application platform. ( http://www.linkedin.com/in/pwetter
if your company needs a new Director of Web Development ).
I had an insight yesterday that I thought I would share. Tapestry is a
I think the biggest insight I attempt to inject into people is the
component template: It's easy to think about it the way a JSP
operates: working character-by-character. But for Tapestry, the
template is actually a blueprint for building a structure in memory,
and that structure is a program
I think we're saying the same thing in different ways.
Tapestry compiles the template into a program to generate the content is a
shorter way of saying what you just said. As opposed to JSP which interprets
the template character by character.
Other systems (WebObjects is one) convert
of course JSP templates are not interpreted character by character
but *just* converted to servlets, javac'ed and finally executed
On Fri, Apr 29, 2011 at 00:03, Pierce T. Wetter III
pie...@twinforces.com wrote:
I think we're saying the same thing in different ways.
Tapestry compiles the
On Thu, 28 Apr 2011 18:03:09 -0300, Pierce T. Wetter III
pie...@twinforces.com wrote:
I think we're saying the same thing in different ways.
Tapestry compiles the template into a program to generate the content
is a shorter way of saying what you just said. As opposed to JSP which
On Thu, 28 Apr 2011 18:16:51 -0300, Andreas Andreou andre...@gmail.com
wrote:
of course JSP templates are not interpreted character by character
but *just* converted to servlets, javac'ed and finally executed
This is compilation in my dictionary, as JSP (a language) is compiled into
a
