in reality wicket _does not_ ship with a javascript framework, all the javascript that ships with wicket is meant for internal use only.
we did in fact start out with prototype, or ricoh, or one of those big players as the back end, but we immediately ran into several issues: these libs do not namespace themselves, so if we use prototype our users can never use mootools or jquery because they are incompatible. wicket ajax is very different, these libs are centered around making an ajax request and sending back data, then applying that data to the dom through client-written js. wicket requests send back markup that is then plugged in - a totally different and completely transparent concept. and as matej mentioned we have built, out of necessity, some pretty advanced features that other libs do not provide. we have namespaced all of our javascript so it does not interfere with anything, which leaves you with unlimited choice of mixing and matching other js libs in your code. what this allows us to do is to mix and match components. yes, it would be nice if we could all agree on a single js lib and build out a complete suite of components based on it, but we have not yet. our users have started building out these suites in projects like wicketstuff-yui, wicketstuff-dojo, etc. -igor On 9/5/07, bmarvell <[EMAIL PROTECTED]> wrote: > > > Hello all, > > This is my first post so please be gentle ;) > > I'm a user interface developer (no Java) working on what will inevitably > be > a fairly heavy Ajax wicket project. After looking at a number of Ajax > examples and pre built widgets I have to say I'm a little puzzled! Why > does > wickets core JS framework not use one of the main JS frameworks that are > available such as jQuery, Dojo or Prototype? I believe you have a hand > rolled version of mootools (although I may be wrong). Do the Wicket core > team plan on supporting and enriching this hand rolled framework alone? > Surely it would make more sense to choose one of the main JS frameworks > that > have dedicated teams of devs supporting it? > > Also I've found that Ajax widgets in wicket seem quite "here and there" in > their implementation. Some demos use prototype, some use YUI (a datepicker > for example). Doesnt this go against what JS frameworks are trying to > provide? Choosing a decent framework such as jQuery or Prototype will give > the developer a solid toolkit on which they can build, so extra components > such as datepickers or custom widgets can be applied as "Plugins". > Sticking > to one framework reduces hits to the server, bandwidth, load and > processing > times all of which imho are good things. > > My worry at the moment is that the demos in wicket are very "lets get it > working on the frontend" and not "lets think about a framework and its > rich > functionality". > > SO to summarize :) are there any thoughts about using a single, supported > framework in wicket and moving forward from there? > > Cheers, > > Ben > -- > View this message in context: > http://www.nabble.com/JavaScript-Frameworks-tf4383060.html#a12494810 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
