Numa Schmeder <numa <at> euroconsumers.com> writes:
> I am also voting for an abstraction layer, dojo slows thing down and
> is not always fully compatible with all browsers and version.s Keep
> in mind that tapestry is used for public website and not only
> intranets where you can control the client's browser.
I think we should have an abstraction only when we need two or
more implementations. But the current case is not like that. So
I don't see a compelling reason to do that.
If you're concerned with dojo code bloat, T5 may by default use
a bare minimal dojo.js. For each component that uses extra
dojo functionality, it can output a dojo.require('dojo.foo')
to bring in the extra Javascript. I believe such code is
still cached by modern browsers
(http://dojotoolkit.org/pipermail/dojo-contributors/2005-December/001259.html).
This way, if you don't use such components, you won't pay
the price.
--
Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
