Thats why we also have IcomponentBorder, because thats like a swing border, you add that border to a component instead the other way around
2007/11/16, Stefan Simik <[EMAIL PROTECTED]>: > > thanks for your response igor, > yes, you are right, i understand, that in the output html border wraps > its content -> so it's looks like border for nested components. > > What we both mean, is the same, difference is only from point of view. > My point of view is, that generally (in desktop GUI like Swing - that was my > swing context) > borders are used for decorating some component (that's the same for wicket) > but hierarchy > is reversed towards wicket - for example: > component.add( new LineBorder() ); //like in > desktop GUI > Here: border knows nothing about component, that decorates > > > In Wicket, it's reversed: > border.add(component); //in > Wicket > So it's my point of view, that this border is container component, because > other > components are added to it. I know, that it results in decorating added > component, but in the sense > of hierarchy, other components are added to the border, so the border is > container for added components. > > In this context I see Border quite like "Panel, that can use markup > inheritance through <wicket:body/>" > > I hope, you understand what I mean.. > thx > > > -- > View this message in context: > http://www.nabble.com/Border-component---naming-tf4822088.html#a13802790 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
