Unless WiQuery has matured a *lot* lately and the code has been cleaned up significantly, I can't recommend it, personally.
Writing what should be JavaScript in your wicket Java code is quite out-of-place, and generally all you need to do is place your code where it belongs, in a .js or your markup. There may be some odd cases here or there where tighter integration of jQuery and Wicket can be beneficial, but those can usually be resolved some other way. I don't have enough experience or knowledge of the framework to cast a final vote though, all I'm saying is: beware of the quality of this library's code and make sure you actually need it first (I want to do jQuery stuff in my Wicket application is generally not reason enough). On 06 Apr 2011, at 11:09, [email protected] wrote: > Hi, > > We are thinking of using wiquery for a project. We are interested in the > experiences of people using it. Does wiquery work in the major browsers (IE7, > IE8, IE9, FF3 and Chrome)? Are there any complications when different > versions of jquery are used on other places in the HTML? What is the version > of Wicket you used it? > > Please share your experiences. > > Thanks in advance, > > Haiko van der Schaaf > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
