Yep, Wicket kicks ass. The book will help even more.
Am I the only one having so many issues trying to update to 1.3, though? Was there such a big jump because of the move to Apache? Or is this kind of growing pain to be expected for each new version, do you think? On Tue, 2007-09-04 at 20:14 -0700, Jonathan Locke wrote: > > yeah, i saw that last week. it's quite a statement. but i'm hearing this > kind of thing more and more. at my current workplace, i'm constantly > staggered when i mentally compare our development speed with past non-wicket > projects. even when i guess a little on the low side, i find i'm mostly > making or exceeding schedule targets. and the feature branches we're > developing in parallel often come together so quickly that it's a challenge > just to stay on top of the back end of the process with all the merging and > testing and deploying. our components already are paying off enormously in > terms of both cost of development and cost of maintenance. just being able > to fully refactor wicket components in eclipse is almost a reason to adopt > wicket in itself. > > > jweekend wrote: > > > > This http://www.eweek.com/article2/0,1895,2176557,00.asp eweek article > > has a small section on how LeapFrog are finding development with Wicket > > and why they chose to use it. > > Regards - Cemal > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
