But why not for tabs, accordion, slider, and other jquery components? That gives you much more flexibility in separating what a component logically does (e.g. render various sections of data, widgets, etc.), from how it is shown and interacted with in the browser (view as tabs, steps in a widget, accordion, just plain sections, ...). In jquery-ui itself you also add it as a behavior to a DOM element. So why not offer that flexibility in the Wicket integration? Idem ditto for things like draggable, droppable, etc. Why not offer the possibility to make any existing wicket panel/component a draggable by having a DraggableBehavior? In wicket-jquery-ui you need to subclass a Draggable panel, which is obviously not possible with already existing components/panels.
Just to clarify: this is my very personal opinion on how a jquery integration should be designed (and actually how I've done it for many projects so far). That's obviously very subjective. It looks like an impressive library nonetheless! On Tue, Oct 2, 2012, at 15:30, Sébastien Gautrin wrote: > Hi Pointbreak, > > At least for wicket-jquery-ui, it offers also pure behaviours > integration for jquery extensions that are pure behaviours (such as > Droppable). I think wiQuery does as well. For ease of defining such > things for you own component, it is the main goal of wicket-jquery-ui; > take a look at the three tutorials Sebastien made (sebfz1) for > wicket-jquery-ui: > http://code.google.com/p/wicket-jquery-ui/w/list?q=label:How-To (note: > Sebastien is the author of wicket-jquery-ui). > > More on the topic, I as well would welcome experience returns from > people who used both (though personally I'm inclined to use > wicket-jquery-ui at the moment, but that's also because I'm biaised > after having been really impressed at how fast Sebastien integrated run > fox software Datepicker component to wicket-jquery-ui while doing his > tutorial#3). > > Pointbreak wrote: > > It's a very long time ago that I looked at the API's, so it's likely > > things have changed since that time. But the problem I had with both > > products is that they are mostly component based API's (meaning they > > offer an Accordion component, Autocomplete component, etc.). Imho, a > > much more flexible approach for JQuery integration is to offer all > > jquery-ui functionality as behaviors. That way existing components (both > > from core, other libraries, or your own code) can more easily be > > augmented with jqeury-ui functionality. And since it's easy enough to do > > it yourself with a few lines of code, I opted to don't use these > > libraries at all. > > There are a few things that require more thought (e.g. jQuery Tab-UI > > combined integrated with Wicket-Ajax functionality, but at least back > > then these frameworks didn't offer that in a flexible way either). > > > > So I would say, check the libraries for how you are supposed to add the > > jquery functionality (behavior vs component hierarchy), and don't be > > afraid to just roll your own if necessary. It's not that much extra > > functionality that the library offers over just using raw Wicket and > > jQuery. > > > > My 2cnts. > > > > On Tue, Oct 2, 2012, at 13:02, ronny.v...@consult.nordea.com wrote: > >> Hi > >> > >> I was not thinking about the base, ie AbstractDefaultAjaxBehavior. > >> > >> I was thinking about using one off the API - several components - could > >> be accordion? could be some effects etc. > >> > >> So I was thinking about who has tried out both API's - has some > >> experiences and suggest this API because bla bla. > >> > >> Hope I explain myself fully here. > >> > >> - Ronny > >> > >> -----Original Message----- > >> From: Martin Grigorov [mailto:mgrigo...@apache.org] > >> Sent: 02 October 2012 08:52 > >> To: users@wicket.apache.org > >> Subject: Re: Wicket and jQuery UI > >> > >> Hi, > >> > >> On Tue, Oct 2, 2012 at 9:28 AM, <ronny.v...@consult.nordea.com> wrote: > >>> Hi Wicket > >>> > >>> I have been looking at a) wiQuery and b) wicket-jquery-ui > >>> > >>> What API to use when doing a bridge between Wicket and jQuery UI? > >> What exactly do you need ? > >> > >> The "bridge" is AbstractDefaultAjaxBehavior - the base Ajax behavior. > >> > >>> Recommendations and experience would be very much welcomed. > >>> > >>> Thanks in advance! > >>> > >>> Best regards/Med venlig hilsen > >>> Ronny Voss > >>> > >>> Nordea Bank Danmark A/S > >>> Online & Securities Processing Solutions Strandgade 3 > >>> DK-1401 København K > >>> Mobile: +45 26711952 > >>> E-mail: > >>> ronny.v...@consult.nordea.com<mailto:ronny.v...@consult.nordea.com> > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
