On Tue, Nov 22, 2011 at 1:15 PM, Emond Papegaaij <[email protected]> wrote: > On Tuesday 22 November 2011 13:09:08 Martin Grigorov wrote: >> Hi, >> >> On Tue, Nov 22, 2011 at 1:02 PM, Hielke Hoeve <[email protected]> > wrote: >> > Emond Papegaaij and I have also attempted to see if it is possible to >> > integrate a small part of WiQuery's functionality into Wicket. We are >> > still working on cleaning the code but here is a preview: >> > https://github.com/papegaaij/wicket/compare/trunk...wicket+wiquery#file >> > s_bucket >> > >> > Basically we have implemented >> > AbstractDependencyRespectingResourceAggregatingHeaderResponse ( :-) ) >> > and have it build jQuery statements for window load and dom ready. All >> > resources are automatically an >> > AbstractResourceDependentResourceReference, this will not break current >> > resources it will only allow them to specify their dependencies. >> I like the change as a whole. >> We had recently some complains that Wicket itself doesn't use its >> dependency management for resource references. >> >> What I think we should do is to remove all uses of jQuery() in .java >> and replace them with Wicket.Event.add(). > > And wicket-event-jquery.js will convert this to $(document).ready or > $(window).load right?
Right. Almost. Only 'domready' is a special event name, because browsers have different impl for that. Passing 'domready' as event name will do: jQuery(fn). Passing any other event name will do: jQuery(target).on(eventName, fn) > >> > Hielke Hoeve >> > >> > -----Original Message----- >> > From: Martin Grigorov [mailto:[email protected]] >> > Sent: woensdag 16 november 2011 11:05 >> > To: [email protected] >> > Subject: Re: Wicket 6 development >> > >> > On Wed, Nov 16, 2011 at 11:54 AM, Sven Meier <[email protected]> wrote: >> >> +1 >> >> >> >> (I'd love to take a look at the new jquery stuff.) >> > >> > https://github.com/martin-g/wicket/tree/ajax-jquery >> > Basically the internals of wicket-ajax.js (partially), wicket-event.js >> > (fully) and wicket-ajax-debug.js (fully) are redone with JQuery. >> > Also there are ~ 90 QUnit tests at >> > https://github.com/martin-g/wicket/tree/ajax-jquery/wicket-core/src/test >> > /js> >> >> Sven >> >> >> >> -----Ursprüngliche Nachricht----- >> >> Von: Martin Grigorov [mailto:[email protected]] >> >> Gesendet: Mittwoch, 16. November 2011 10:01 >> >> An: [email protected] >> >> Betreff: Re: Wicket 6 development >> >> >> >> +1 >> >> >> >> I have quite some progress with JQuery-fying Wicket's javascripts and >> >> I'd like to move it in trunk and involve more people in >> >> designing/coding/discussing/... it. >> >> >> >> On Wed, Nov 16, 2011 at 10:51 AM, Martijn Dashorst >> >> >> >> <[email protected]> wrote: >> >>> We have released 3 bug fixes to 1.5.x and it seems like it is more >> >>> stable now. Stuff for wicket.next is piling up, so I propose we >> >>> start >> >>> our wicket-6.x.y work, using semantic versioning. Since Wicket 6 >> >>> will >> >>> be a breaker API wise, we can just stick with trunk for new >> >>> development, and move maintenance for 1.5.x to a branch. >> >>> >> >>> WDYT? >> >>> >> >>> Martijn >> >> >> >> -- >> >> Martin Grigorov >> >> jWeekend >> >> Training, Consulting, Development >> >> http://jWeekend.com >> > >> > -- >> > Martin Grigorov >> > jWeekend >> > Training, Consulting, Development >> > http://jWeekend.com > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
