yeah, strong coding is about making strong choices. when you /know/ a design decision (such as this one -- separating markup from code) is the right decision, you need to stick to your guns and not lose the whole war because you want to win some little battle. the fact that it takes a little more effort to do a label in wicket than to use some special syntax to substitute a run-time expression is only a lost battle to someone who does not look very deeply at the problem domain. by not trying to please everyone, wicket is able to make a strong design choice here (and in other places). these strong choices are, for many people, winning the war of web app development (if i do say so myself).
Eelco Hillenius wrote: > > On Nov 15, 2007 8:47 PM, Joshua Jackson <[EMAIL PROTECTED]> wrote: >> It's better to have too much Java than too much XML :) >> I think that's one of the consequences in using Wicket > > The end of the day, it comes down to making choices. The Wicket choice > is to not allow template scripting at all. We think we have good > reasons for that, based on our experience (certainly mine!) of what > happens to medium to large sized projects when you do. There are > plenty of threads and discussions about the why. Also, you can avoid a > lot of Java code by just being smarter about things a bit. > > Eelco > > --------------------------------------------------------------------- > 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#a13788321 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
