if we reach a point where there are several contributed scriptaculous components, i think it would make sense to create a wicketstuff-scriptaculous-sandbox project that can house them all.
the sync and queue methods should be moved off of the core Effect interface and into the AbstractEffect class. that way, the Effect.multiple doesn't need to do a no-op. http://github.com/madrobby/scriptaculous/wikis/core-effects On Tue, Jun 10, 2008 at 2:05 AM, Nino Saturnino Martinez Vazquez Wael < [EMAIL PROTECTED]> wrote: > Ok. But I think that we should be a little carefull splitting up in too > many projects... But it's fine with me, so we should just move all the stuff > from the fx package away from your project right? Since the other stuff(only > the queue part though) I do need to be present or i'll have to build a new > project to depend on. > > > Ryan Sonnek wrote: > >> >>> >>>> It's a combination of effects(the example effects from scriptaculous), >>>> >>>> >>> something that fades in shakes and for example squishes.. Did you see the >>> example? >>> >>> >> >> >> I still think this would best be served in a separate project. >> >> >> > > -- > -Wicket for love > > Nino Martinez Wael > Java Specialist @ Jayway DK > http://www.jayway.dk > +45 2936 7684 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
