I think that I'd have to say that the main cons are:- (a) It does demand a certain level of OO coding, in terms of being happy to override classes & typically to be able to create anonymous classes - not a huge amount, but coders grounded in procedural code will feel lost.
(b) The documention is scattered - partly because there are so many ways that it can go beyond the basic web-page (i.e. page inheritance, panels/fragments, embeded forms, built-in AJAX, security, etc,) that not much short of an encylopedia could do it justice! /Gwyn On 15/11/2007, mraible <[EMAIL PROTECTED]> wrote: > > I didn't say my cons were valid - but I do believe there *are* cons to > Wicket. What are they - in your opinion? > > matt > > > igor.vaynberg wrote: > > > >> * HTML templates live next to Java code > > this is easily changed - just a default > > > >> * Need to have a good grasp of OO > > why is this a con? you are saying not knowing oo is a good thing? you > > can say this is a pro - learning wicket will make you a better > > developer :) > > > >> * The Wicket Way - everything done in Java > > as opposed to embedding logic in views which has been something > > plaguing other frameworks for ages? > > > > -igor > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: > http://www.nabble.com/Matt-Raible%27s-ApacheCon-presentation-tf4815955.html#a13780519 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Download Wicket 1.3.0-rc1 now! - http://wicketframework.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
