Hi, It is not very clear to me what exactly is clumsy. Can you explain in more details how it got worse. Show some code maybe.
On Fri, May 11, 2012 at 2:20 PM, Girts Ziemelis <girts.zieme...@gmail.com> wrote: > I was using border in 1.4 to dynamically add different borders to the page > (like - for printing, popup, plain, with header/ footer etc based on page > parameters and some other criteria) and really liked this method in 1.4. > Seems that 1.5 makes this approach clumsy :( Now I must override the > page.add method and do some magic to decide where I am adding the component, > etc. I got it to work (pretty sure I am not covering all cases ) , then > realized, that in WicketTester also now all the component paths must be > prefixed with the "border:border_body" string which is rather ugly :( > > Is there a better way to implement this (instead of borders)? It just does > not feel right - most of the changes in 1.5 made my code cleaner, but this > one feels like a hack ... :( > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
