Re: Last BIG refactor: onAttach/onBeforeRender behavior change in 1.3

yep. one question: i assume that some internal magic will attach any components i add dynamically in onBeforeRender() in a second attachment phase. this could be efficiently implemented by having MarkupContainer add/replace/etc call an internal requestcycle method to add to a list if onBefo

Re: [wicketstuff dojo] JS inheritance and the wicketstuff namespace

Bart Molenkamp a écrit : Vincent Demay wrote: If I well understand it is a class named wicketstuff giving access to each function of each package as a subclass of wicketstuff? I like that, so +1 I don't understand exactly what you mean. I now have classes coded in JavaScript (similair like

Re: [wicketstuff dojo] JS inheritance and the wicketstuff namespace

* Bart Molenkamp: > > I wanted to make better use of JavaScript inheritance using Dojo. > > > > Therefore, I created a dojo module named "wicketstuff", which can access > anything under org.wicketstuff.dojo. For example, > I now have a javascript class wicketstuff.dojodnd.DojoDropContainer >

Re: [wicketstuff dojo] JS inheritance and the wicketstuff namespace

Vincent Demay wrote: If I well understand it is a class named wicketstuff giving access to each function of each package as a subclass of wicketstuff? I like that, so +1 I don't understand exactly what you mean. I now have classes coded in JavaScript (similair like most - if not all - class

Re: [wicketstuff dojo] JS inheritance and the wicketstuff namespace

If I well understand it is a class named wicketstuff giving access to each function of each package as a subclass of wicketstuff? I like that, so +1 -- Vincent Jean-Baptiste Quenot a écrit : * Bart Molenkamp: I wanted to make better use of JavaScript inheritance using Dojo. Therefore,

[wicketstuff dojo] JS inheritance and the wicketstuff namespace

Hi, I wanted to make better use of JavaScript inheritance using Dojo. For example, using Java I can extend DojoDropContainer to implement (server-side) specific drop behavior. But I also wanted some specific behavior on the JavaScript side without having to copy/paste all the existing js code

Re: [Wicket-autocvs] SF.net SVN: wicket-stuff: [1935] branches/wicket-1.3/wicket-contrib-dojo/ src/main/java/org/wicketstuff/dojo

Bart Molenkamp a écrit : Done. Vincent, could you please check if this is the way to go? Hope everything is ok for you (about refresh). It seems ok for me thx. -- Vincent Thanks, Bart. -Oorspronkelijk bericht- Van: Bart Molenkamp Verzonden: dinsdag 17 april 2007 12:15 Aan: wick

RE: [Wicket-autocvs] SF.net SVN: wicket-stuff: [1935] branches/wicket-1.3/wicket-contrib-dojo/ src/main/java/org/wicketstuff/dojo

Done. Vincent, could you please check if this is the way to go? Thanks, Bart. > -Oorspronkelijk bericht- > Van: Bart Molenkamp > Verzonden: dinsdag 17 april 2007 12:15 > Aan: wicket-dev@incubator.apache.org > Onderwerp: RE: [Wicket-autocvs] SF.net SVN: wicket-stuff: [1935] > branches/wic

RE: [Wicket-autocvs] SF.net SVN: wicket-stuff: [1935] branches/wicket-1.3/wicket-contrib-dojo/ src/main/java/org/wicketstuff/dojo

Ok, I can just simply add my configuration parameters using ComponentTag.put(). Also reloading works (probably didn't work in the first case due to the bug in RichText.js). I will remove the AbstractDojoWidgetBehavior class. Thanks, Bart. > -Oorspronkelijk bericht- > Van: Vincent Demay

Re: [Wicket-autocvs] SF.net SVN: wicket-stuff: [1935] branches/wicket-1.3/wicket-contrib-dojo/ src/main/java/org/wicketstuff/dojo

Bart Molenkamp a écrit : Hi Vincent, I wasn't aware of the TargetRefreshManager class. I found out that the DojoRichTextBehavior didn't work when the component was added to the page after an Ajax update (in my case I replaced some panel with another panel that contained the rich text editor).

RE: [Wicket-autocvs] SF.net SVN: wicket-stuff: [1935] branches/wicket-1.3/wicket-contrib-dojo/ src/main/java/org/wicketstuff/dojo

Hi Vincent, I wasn't aware of the TargetRefreshManager class. I found out that the DojoRichTextBehavior didn't work when the component was added to the page after an Ajax update (in my case I replaced some panel with another panel that contained the rich text editor). The solution would be call

Re: [Wicket-autocvs] SF.net SVN: wicket-stuff: [1935] branches/wicket-1.3/wicket-contrib-dojo/ src/main/java/org/wicketstuff/dojo

Hi Bart I see you added a behavior to deal with Dojo widget creating it using dojo.widget.createWidget. I don't understand what is the aim of this abstract behavior because AbstractRequireDojoBehavior can already create a dojo widget via an AjaxRequestTarget (see TargetRefresherManager which