On Thu, Aug 28, 2008 at 4:07 AM, Michael Sparer <[EMAIL PROTECTED]>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 :-)). YES!! Arhhg... > > > 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? What about the people who don't want dojo? :p Ok, you push things... How about these options: A. Create a project for the actual DOJO base: wicketstuff-dojo-core (or wicket-dojo-core), factoring out the common elements, and then, both wicketstuff-push, and wicketstuff-dojo-components depend on that one? (This means, since dojo now has a maven build, we could get things from there... ...maybe) B. Rename wicketstuff-push wicketstuff-dojo-core and thats it... Make sure its known that Comet technology is there. (Seems harder to know dojo-core has comet and push but its dooable, and has less projects...) And your suggestion: C. Stopping support of wicketstuff-push and just having that inside wicketstuff-dojo.... (Obviously my least favorite option, I wouldn't have even considered it, if you hadn't forced my hand...) > > 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? > > >
