Re: Wicket vs. ZK

2007-08-19 Thread Matthijs Wensveen
1. Design concern (Wicket vs. ZK) Both frameworks are thin-client and generate AJAX, the biggest difference is Wicket uses Java and HTML while ZK uses XUL or other scripting language. What's the advantage and disadvantage in both cases? Advantage of HTML is that you can work with web

Re: 1:1-translation from html [was: Wicket vs. ZK]

2007-08-17 Thread Jan Kriesten
hi eelco, I agree: especially if you break your application up in many panels, it can be hard to keep an overview. So sometimes, there is something to say for following a more page based approach in favor of reusability. However, part of the argument still holds as even broken up in panels,

Re: 1:1-translation from html [was: Wicket vs. ZK]

2007-08-17 Thread Eelco Hillenius
in fact, select, choices (and radio) are still a weak part in wicket (imho). there are many classes to deal with them, but most aren't customizable enough and/or require different markup (span instead of select) as the designer would put in. It's certainly not a perfect framework, and we need

Re: Wicket vs. ZK

2007-08-16 Thread Gabor Szokoli
Hi, Slightly off topic, but this is the summer vacation season on this hemisphere, so I'm sure no one will mind: On 8/16/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Wicket assumes that UI designers are *designers* (and not half-programmers like ZK assumes) only dealing with laying out, and

Re: Wicket vs. ZK

2007-08-16 Thread Eelco Hillenius
We've been using wicket for a couple of months now, our first application is about to be deployed, so I looked back at the templates and started wondering how much this separation of concerns applies to us. We have a base page with some panels supplied by subclasses, then those panels are

Re: Wicket vs. ZK

2007-08-16 Thread juliez
for MEAP (nope, it's not free) you can help use make that chapter perfect by giving us feedback when it is available :) Thanks, Julie -- View this message in context: http://www.nabble.com/Wicket-vs.-ZK-tf4276516.html#a12188293 Sent from the Wicket - User mailing list archive at Nabble.com

Re: Wicket vs. ZK

2007-08-15 Thread Eelco Hillenius
. Design concern (Wicket vs. ZK) Both frameworks are thin-client and generate AJAX, the biggest difference is Wicket uses Java and HTML while ZK uses XUL or other scripting language. What's the advantage and disadvantage in both cases? Advantage of HTML is that you can work with web designers standard

Re: Wicket vs. ZK

2007-08-15 Thread Igor Vaynberg
On 8/15/07, juliez [EMAIL PROTECTED] wrote: 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