I agree with Igor. if you are looking to generate your ui purely in javascript you will not be able to take advantage of a lot of wicket components.
And i think you should generate your ui purely in javascript only when the ui dose not include in the standard Html components. 2008/10/3 Igor Vaynberg <[EMAIL PROTECTED]> > there shouldnt be any problems using prototype with wicket. > > however, if you are looking to generate your ui purely in javascript > you will not be able to take advantage of a lot of wicket components > > -igor > > On Thu, Oct 2, 2008 at 8:18 AM, ilanfox <[EMAIL PROTECTED]> wrote: > > > > Hello, > > > > I am considering starting a new project (web app) with Wicket. > > This project will be based heavily on JavaScript with Prototype and > > Scriptaculous. > > Most of the UI will be generated via JavaScript and the also the new > CANVAS > > tag will be used. > > I really need to know if I'm going the right direction. is it safe to > > combine the Prototype lib with Wicket? > > Do I need to fully understand how Wicket works before trying to combine > it? > > my prior expropriate is mostly with struts1. > > > > Thanks in advance. > > Ilan F > > > > > > -- > > View this message in context: > http://www.nabble.com/using-Prototype.js-and-Scriptaculous-with-latest-version-of-wicket-tp19781402p19781402.html > > Sent from the Wicket - User mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > 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] > >
