On Thu, 01 Nov 2012 01:10:16 -0200, Paul Stanton <p...@mapshed.com.au>
wrote:
I've had to do some pretty in-depth debugging and patching of tapestry's
javascript in the past (particularly around zones) and at least I can
understand the source code because it is a familiar language...
Replacing the source-code with an entirely new language, which is
probably familiar for < 2% of tapestry sounds like a bit of a speedbump
to me.. especially if - in order to create a monkey-patch of sorts, it
will need to be written and integrated via Coffee?
I don't think so. Just look at the generated JavaScript files.
CoffeeScript is *not* understood by browsers, so it's compiled into
JavaScript before being served.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
