After the update of wicketstuff-push (see
http://www.nabble.com/wicketstuff-push-update-to18765345.html) the question
came up if the push project shouldn't depend on the dojo project any longer
as ws-dojo uses dojo 0.4 and the new cometd implementation requires dojo
1.x.
Rodolfo Hansen, who volunteered to do the upgrade to the latest cometd
version, suggested to let wicketstuff-push cease to depend on ws-dojo. In
our current project, we're using both ws-dojo and ws-push. We really would
like to use the latest cometd release; we can't bear, however, the idea of
having two different dojo versions in the classpath - so we thought about
lifting ws-dojo to 1.1.
As Rodolfo mentioned, lifting ws-dojo to 1.1 isn't trivial due to
incompatibilities (i.e. API changes) between 0.4 and 0.9. However, we think
that lifting the ws-dojo project as a whole (with its dozens of components)
isn't necessary. We'd propose to start with ws-dojo's core functionality -
which is providing dojo resources and build facilites - and lift components
as needed.
We already managed to get the latest dojo release in and port some
components, but there's still a lot of work to be done. Therefore we suggest
to make a new project for wicketstuff-dojo with dojo 1.1 and rely on some
helping hands who port the components they use to dojo 1.1.
As for wicketstuff-push we still hope we can convince Rodolfo to keep the
dependency to (the then new) wicketstuff-dojo-1.1
So what do you, wicketeers, think about that?
If it's alright, our sf.net accounts are the following:
msparer (i already got some permissions, dunno if creating projects is among
them)
sfussenegger (no permissions so far)
regards,
Michael
-
Michael Sparer
http://talk-on-tech.blogspot.com
--
View this message in context:
http://www.nabble.com/New-wicketstuff-dojo-project-tp19070145p19070145.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
