Hi Emanuele,
I don't plan to support additional components myself - especially not problems that seem to be caused by Dojo only. wicketstuff-dojo-1.1 is mainly meant to ease the integration of Dojo into Wicket (i.e. to provide the infrastructure like custom builds, packaging as jar files, configuration of Dojo as part of a Wicket application, mounting resources and the like). In the future, there might be more and more components available out of the box. However, at the moment I don't have plans - or time - to add more components than those already included (animations, toaster widget, drag and drop and cometd support)
If you've built a Wicket component based on wicketstuff-dojo-1.1, you're welcome to contribute your code. If you want to contribute but don't know how, I'd be happy to get you started.
Merry Christmas, Stefan
Emanuele Gesuato-2 wrote:
Stefan Fußenegger wrote:
> There's now a little bit of documentation online:
>
http://wicketstuff.org/confluence/display/STUFFWIKI/wicketstuff-dojo-1.1>
> Cheers, Stefan
>
Hi,
First of all, good job.
Is there any plan to support the dojo context menu ? :-)
We are using it but we've got several warnings with some deprecation
calls on the html document in development that are quite annoying.
Also if i have different context menu in the same page and if these
context menu has submenus, the submenus are sharing the same instance of
the content component.
Example:
If i have menuA and menuB in two tables, tableA and tableB. If i right
click on menuA or menuB in the java code i see that the referenced
component is always on tableB. This only happens in the voices of the
menu that are in a submenu.
Thanks for any help,
Emanuele
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
