First, thanks for the reply! >> 2. AJAX components (Wicket vs. ZK) >you do not implement features like drag and drop or datepicker in wicket, >instead you wrap javascript libraries that implement those features with >wicket components.
I am actually confused at how many ways Wicket supports AJAX. The classes in wicket.ajax packages are used for AJAX behaviors. I supposed these classes are for common AJAX behaviors. It seems they are different from wrapping JavaScript - correct me if I am wrong. Then my questions are 1) what is the standard way to add AJAX with Wicket: first looking for existing components (including the components in WicketStuff), then if not found, wrap JavaScript? 2) I read the attached file and googled more for the instruction on how to wrap JavaScript. Found one here (http://cwiki.apache.org/WICKET/adding-dynamic-field-prompts-or-hints.html). I am wondering if there are instructions on how to do it in a general way. >>3. Target application (Wicket) > like you say, wicket is component oriented. it doesnt really care how you > build your app: many pages or a single page. at my day time job we have an > app that is mostly a single page with a lot of component replacement. > works > just fine. Still not sure, if a page includes many replacement, how to keep the method/class short yet support those changes? >>4. Integration (Wicket) > how about it? i dont see why you would want to integrate a ui framework > with > another ui framework. >in the end what you should do is write a small app using both frameworks to >get a feel for them. Absolutely! I started with a simple Wicket page already and will try to add some AJAX stuff tomorrow as well as a page with some replacement. Need to try ZK too. Sounds a lot of fun. -- View this message in context: http://www.nabble.com/Wicket-vs.-ZK-tf4276516.html#a12175176 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
