Things like partial render/form submissions/links you will have to use our ajax support for, dojo simply doesnt know how to interact with wicket.
-Igor
On 6/7/06,
Eelco Hillenius <[EMAIL PROTECTED]> wrote:
The core ajax support is very nice because it allows you to re-render
any component you want without having to code a single line of
_javascript_. Dojo and friends are richer on the _javascript_ side. But I
don't think you have to choose one or another; just mix 'n match
according to what you need. That's what we do all the time.
Eelco
On 6/5/06, Wouter de Vaal <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm trying to decide whether to use the dojo-toolkit from wicket-stuff
> or the native wicket-ajax support. Dojo looks very cool and has a lot
> of nice features and widgets, which may be easily incorporated using
> the wicket dojo-toolkit (right?) and the ajax features/widgets from
> wicket don't look very extensive to me (or am I missing something).
> So I'm leaning towards picking up the dojo solution and take the
> already build features and put them in my wicket app.
>
> So what are your thoughts? Pro's/con's, etc?
>
> I also read that Jeff Lin was busy porting the wicket dojo toolkit to
> support wicket 1.2, any new on this (hope he's reading this).
>
> Regards
> Wouter de Vaal
>
>
> _______________________________________________
> Wicket-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
_______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
