As a wicket-stuff developer, I for one would hate to see restrictions placed on what can or can not be a wicket-stuff project. The beauty of the wicket-stuff idea is that it is a playground for people try out potentially cool ideas. It's a place for people to learn how to use wicket and build "possibly" cool widgets and tools.
I know that *my* project (wicketstuff-scriptaculous) has occasionally been left "in the dark" for several months before a whole slew of changes and features get built in. Sure, there may be a "better" wicket/hibernate project out there (aka: databinder), but I really don't see any issues with that. Especially now that there's a wicket-stuff wiki, it can be clearly spelled out there what each project's strengths/weaknesses are. On 5/6/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Well, then someone would complain wouldn't they? You know what, I'm sick of this and deleted the projects, including the wicket-stuff-examples, which was another one of these projects only maintained by me. As you brought this up Martijn, please do a review of the other wicket-stuff projects that are *possibly* not actively 'maintained' (wicket-database, datepicker, gmap?). Let's do the cleanup properly then. Eelco On 5/6/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > well, yes it does matter. there is a difference between a project and a > bunch of compiling code. for example that project will break if anyone tries > to use it with hibernate 3.2 because it hasnt been updated to their switch > of aggregate return types form int to long. who knows what else is broken. > this project needs to be maintained from both ends: wicket and hibernate. > and you are only doing it form one end. > > -igor > > > On 5/6/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > > > you _maintain_ them as far as keeping api with wicket in sync. but do > > you > > > actively develop them? do they provide any value in their current state? > > are > > > they up to the latest hibernate version? > > > > Huh? Does it matter for this project more than other wicket-stuff > > projects? Does it matter what release of Hibernate it's on? Don't you > > have more important things to do than to bith about wicket-stuff > > projects that I say I take responsibility for? > > > > > imho those projects never got finished, not even close. > > > > The great motivator speaks again. > > > > Eelco > > >
