Michael Sparer wrote:
the components we're using in our projects have been ported to dojo 1.1 now,
including:
- FXOnClickFader
- FXOnClickSlider
- FXOnCliskWiper
- FXOnMouseOverFader
- DojoToaster
- Drag and Drop panels
all other components have been dropped and should be added one by one after
you diligent, highly motivated people porting the components you're using
;-)
Some API changes were unavoidable due to the new dojo version, and the
documentation of the classes is sometimes a bit spare and/or obsolete.
one major point:
the cometd-part of the wicketstuff-push project has been integrated. as the
push projects consists of about 20 classes and depends on dojo, it's, from
my point of view, best located in the same project (Rodolfo's gonna kill me
for that :-)).
so it's basically ready to be shared with the community. in the current
structure the way to go is creating a new wicketstuff project, isn't it?
so we'd have in trunk:
- wicketstuff-dojo (for dojo 0.4)
- wicketstuff-dojo-1.1 (for dojo 1.1 - including push)
- wicketstuff-push (for dojo 1.1. with its own dojo distribution contained)
and in branches
- wicketstuff-push (for dojo 0.4 before Rodolfo's major refactoring)
that makes the already confusing wicketstuff even more confusing doesn't it?
shouldn't we consider merging some projects?
YES it's a good idea.. I've also though of it.. At some point we'll
probably need to put some of the stuff in a legacy folder or something,
or maybe people should write which version their stuff project supports...
another problem might be to find the above mentioned motivated people ...
so if it's ok to share it as new wicketstuff project we'll go about starting
a (short) wiki page explaining the differences and API changes and then
posting message to the user list for motivated people.
what do you think?
Nino.Martinez wrote:
+1, and i'll even try to help when I have time:) I think I could make my
ajax loading tooltip in there:)
Michael Sparer wrote:
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)
Could you try if it's possible? I think it should be on svn, but not
sure on team-city and jira
regards,
Michael
-----
Michael Sparer
http://talk-on-tech.blogspot.com
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
-----
Michael Sparer
http://talk-on-tech.blogspot.com
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
