Also do look once to the IComponentBorder (and the implementation: MarkupComponentBorder)
ofcourse that won't help you too much with your situation i guess because then still all subclasses shouldn't add to the page but to the panel that has the border.. johan On 6/18/07, Mark Derricutt <[EMAIL PROTECTED]> wrote:
On 6/18/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > Not so sure what to do with this. I think we should regard such use of > borders as outdated, and that for such templating markup inheritance > should be used. In the case I was wanting to work with markup inheritance didn't really work right as I wanted to change the used border on the fly, in the end I just used object inheritance having the subclassed pages to call "border.add()" rather than add() directory (with the border defined/added by the base class as required). It works, and its good that its explicit that you're adding objects into the border, but it would also be nice to override add() and disallow the subclasses from adding to the page itself. Mark
