* Bart Molenkamp:
I wanted to make better use of JavaScript inheritance using Dojo.
snip/
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
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
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.
snip/
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
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 -
