Re: Borders and inheritance in wicket 1.5

2011-11-02 Thread bjolletz
Oh, that would probably solve my scenario! I think add() actually was final in 1.4, but as you say that seems to have changed in 1.5. I wasn't aware of that change so did not think that was an option... Thanks you very much for your help and quick replies, much appreciated! -- View this message i

Re: Borders and inheritance in wicket 1.5

2011-11-02 Thread Igor Vaynberg
afair add() method is not final, so you can overwrite it on panel A and forward all calls to the border's body container. -igor On Wed, Nov 2, 2011 at 12:22 PM, bjolletz wrote: > If panel A was the only place where the border was used, that would surely be > true. But I also use the border in ot

Re: Borders and inheritance in wicket 1.5

2011-11-02 Thread bjolletz
If panel A was the only place where the border was used, that would surely be true. But I also use the border in other components where I want the same appearance but dont want to extend from panel A. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Borders-and-inherita

Re: Borders and inheritance in wicket 1.5

2011-11-02 Thread Igor Vaynberg
if you are using inheritance why are you using a border? same effect can be achieved with markup inheritance... -igor On Wed, Nov 2, 2011 at 11:55 AM, bjolletz wrote: > > Igor Vaynberg-2 wrote: >> >> extending panel A means that your components go into panel A not into >> one of its children. >>

Re: Borders and inheritance in wicket 1.5

2011-11-02 Thread bjolletz
Igor Vaynberg-2 wrote: > > extending panel A means that your components go into panel A not into > one of its children. > Yep. That's why I used setTransparentResolver on the sectionBorder in 1.4 to make things work. Igor Vaynberg-2 wrote: > > you can provide a special addChild() method, or

Re: Borders and inheritance in wicket 1.5

2011-11-01 Thread Igor Vaynberg
extending panel A means that your components go into panel A not into one of its children. you can provide a special addChild() method, or provide addChildren(WebMarkupContainer) callback that you call from A's onInitialize() or let your panel A implement IComponentResolver and try to locate child

Borders and inheritance in wicket 1.5

2011-11-01 Thread bjolletz
Hi, I have the following setup: *A border:* *Panel A* (sectionBorder refers to my border component above) *Panel B* (extends Panel A) When I add the "someLabel" component to Panel B, the component hierarchy will be wrong since the someLabel component will be added to the base panel (Panel A