Leonardo Quijano Vincenzi wrote:
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)
-1 on this integration.
Are there any benefits beside enabling some ajax or effects magic ?
I am also opposing integrating Tacos into Tapestry, but thats another
thema...
Instead of centralizing Tapestry - so good components come only from the
main distribution, keep the libraries of components out there, like
tacos is, make their life simple by joining development to make the
support better, just like the case with Jesse is, but tapestry should
stay a framework and not a solution, to the maximum extent abstract.
e.g. : it should evolve to allow partial page rendering, making tacos
life much easier, but keep the implementation of components to others,
just like in the case of JSF...
Cheers
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
