Dojo should be optional, IMO, but with a global switch (on/off). I don't
know if that's too naive, but it should be possible to enable /
disabling it by just changing the configuration (What I mean is, that
there should be no need of changing the components)
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Ron Piterman wrote:
While dojo seems a very good library, there are some serious
considerations about making tapestry really dependeant on it -
I would like to know if that is going to be the case for 4.1...
Well, as unpopular as it may sound, I find that very unacceptable -
dojo, as hip as it is, has also many disadvantages - like getting
really hard on the browser for very basic tasks - so page load time is
very long, getting high latency also when using top hardware - I don't
want to know what happens when and if using old browsers and hardware -
I think if tapestry is heading the way of being a web framework for
ajax applications, not giving the basic sleek functionality for good
old web 1.0 - well - this requires some discussion from the community.
currently, all JS is clean and functions well, I hope it stays that
way, *enabling* one to use JS libraries such as Dojo, but not
*imposing* one to use a certain one...
Cheers,
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
