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 > -- View this message in context: http://www.nabble.com/More-real-world-Wicket-tf4379690.html#a12490893 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
