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.
Numa
Le 8 janv. 07 à 13:33, Davor Hrg a écrit :
I'm for the abstraction too,
it will also force better separation from the framework
the AJAX and other client side features provide.
I suppose this would simplify using different versions of dojo also
easier.
Davor Hrg
On 1/8/07, RonPiterman <[EMAIL PROTECTED]> wrote:
Hi - I would like to share some thoughts about 4.1 dojo integration -
maybe it will help to improve T5...
I use Dojo in two projects - the first one, base on tapestry 4.0,
is a
heavy-ajax base project - everything is done via Async requests - we
have some custom widgets and so on... dojo is really a bless !
in another project, based on 4.1, we use normal (sync) navigation,
its a
classic web site, but for some small things we do use Async
requests- In
this second project dojo is mostly responsible for slowing down page
loading- bootstrapping on every navigation change makes a really
heavy
feeling of bad response time...
now howard mentioned the possibility of adding an abstraction
layer on
top of dojo, to loose the bundling of dojo with tapestry.
I would vote for that, and for making the dojo support a
subproject of
tapestry.
my 2 cents...
cheers,
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
