> Chris Colman schrieb: > > The beauty of the multiple extend/child idea is that it's not a > > completely new concept we're talking about here - it's merely an issue > > of supporting n>1 instead of arbitrarily fixing n=1 like it is now. > > 1 Question: Who dominates Who and Why? > > If you extend 1 class by class you create specialisations that dominate > each other, but here you just mess together some classes - so why should > which class dominate? If we manipulate a headertag? If we have same > namespace? If we have different securitylevels? Wich class is > responsible for all this? Why?
Dunno what you mean by "dominate" or "mess together some classes". No one is talking about mess - the whole point of this feature is avoidance of mess - in the same way OO brings about reduced complexity in code the same thing can happen with markup. We're not proposing multiple inheritance - which indeed causes mess. We're talking single inheritance which means single lineage. Each page only has a single base page. It's easy for Wicket to perform the resolutions and merge markup from base and derived pages. I know this because it already does it and it works fine. We're just proposing to remove the restriction that it can only do it for just one section of your base page - that's all, nothing revolutionary - just evolutionary. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
