Hi Martin,
On Sun, Nov 23, 2008 at 2:36 PM, martin-g (via Nabble)
<[hidden email]> wrote:
Hi,
First I want to congratulate you about this project!
I find it really interesting. The JavaScript generation, the plugin architecture, the testing mini framework ... pretty cool.
Thank you, did you look at the documentation on our official website
www.wickext.org ?
I don't understand the full usage of the widgets.
You know that Wicket saves the state at the server-side. Looking at the widgets' code I don't see how they will update their (server) state after user's interaction. There aren't any callbacks (ajax behaviors) which will let me know that the tab selection has changed for example.
Yes, that's one of the questions we will resolve in the 1.0 version. In facts, the only way to synchronise a widget (like a tab widget for example) would be to send an Ajax request to set the active tab. I don't think that we can make this behavior a default behavior. My idea is to give a configuration option per component (like setServerSync(true)) in order to choose to synchronise it or not.
For the callback part, this will be done in the 1.0 version.
I suppose you are aware of https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-jquery. Here all widgets provide such callbacks.
Yes I am, in facts WickeXt first goal was to give JavaScript generation tools and then to build UI components on it (if you took a look at our source code, you can see that our UI components are generated via WickeXt's JavaScript generation framework).
Anyway, thanks for your feedback and don't hesitate to contribute if you want to !
Cheers,
Lionel Armanet
Cheers
martin-g
--
__________________________________
"SJBCJM! (Si Java Bien, C'est Java Mine)"
Lionel armanet
MSN :
[hidden email]
