If the component hierarchy can be changed without changing behavior or semantics, then why are the components in a hierarchy to begin with? Why aren't all the components being moved around already siblings at the same level? Does Wicket require that the order of sibling Wicket components match the order at which simply HTML elements appear?
-----Original Message----- From: jcar...@carmanconsulting.com [mailto:jcar...@carmanconsulting.com] On Behalf Of James Carman Sent: Tuesday, November 09, 2010 9:39 AM To: users@wicket.apache.org Subject: Re: Free wicket from component hierarchy hell I get what you're saying about having to stick to the hierarchy when designing markup files. I just don't know whether this approach is the best or not. Again, I really haven't had a chance to sit down and think it through. > > Sounds completely fair to me. > Why don't you put this work into wicketstuff (or flesh it out more with Igor in his git repo first and then move it), so we can see what it's all about and perhaps try it out for ourselves? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
