Dave,
I don't think anyone does have a good handle on how much work it would be to
integrate Dojo 1.0 into the S2.1 tag framework. It's one of those things
that the time taken to properly evaluate and estimate the work necessary may
be longer than the time to do the work, and even when the work is under way
there may be some unforeseen issues even if an estimate was made. The Dojo
guys have tried to make it easier by providing an api change list from 0.4
to 0.9 then from 0.9 to 1.0, but how that applies to the S2.1 code is
something that will only make sense to someone who has the code fresh in
their mind.
This is why I started to work on the changes and kept the code as a separate
entity, that way if it does prove to be a mountain rather than a molehill
there's nothing being held up, and if it turns out to be a molehill then we
get all the benefits of supporting, matured code with a smaller footprint in
a short period of time.
Al.
----- Original Message -----
From: "Dave Newton" <[EMAIL PROTECTED]>
To: "Struts Developers List" <dev@struts.apache.org>
Sent: Sunday, April 06, 2008 3:18 PM
Subject: Re: Dojo plugin update using 1.1.0 framework
--- Al Sutton <[EMAIL PROTECTED]> wrote:
My main driver for doing the updates was to update the S2.1 code to bring
it inline with the latest version, but perhaps we should put our hands up
and
admit that S2's focus is not on Ajax UI widgets
Nobody has yet provided any information as to the potential cost of making
Dojo 1.0 work and nobody answered my question regarding what level of
functionality currently exists in the Dojo 1.0 plugin, so I'm pretty much
unable to come to any cogent conclusion.
If it came to a vote I'd probably say (a) leave the current Dojo plugin
where
it is, and (b) put any new tag plugins on Google Code (like my
semi-dormant
jQuery plugin and others people are working on).
I don't know what the ASF policy is on "endorsing" particular code, but it
seems like if a new plugin got to the point of being usable it would be
simple enough to add a "we currently recommend using..." or "among the
better
tag libraries are..." or whatever.
Dave
---------------------------------------------------------------------
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]
