> I give up. Looks like this enhancement is really receiving positive votes. > :)
:) :) :) :) :) :) :) :) Just some of the many happy faces! > In my second reason, I point to something that is... the _core_ of wicket: > binding Java objects (Components) to HTML tags. So, not having this > binding, we could lose great features. Seeing from this point of view, my > suggestion is to allow these new > call-whatever-you-want-here-from-abstract-to-implement-to-default-to-etc > tags only when they have been declared in Java: It's great that you're now at the level of suggesting improvements! And I'm already hating myself for my following comments but in the interest of keeping this enhancement simple: My first thoughts about your suggestion are: I wonder if components associated with default/overridden markup should be treated any differently. I have always found Wicket's error detection on missing tags or unbound components to be excellent. It would still continue to work in the exact same way without needing to define, as you suggest, at the Java level, special components that will bind to abstract (default/override) markup sections. I think the elegance of the new feature is that is purely an enablement (I think I just invented a new word!) of multiplicity on an existing feature and some new tags to more accurately define the feature (previous tags are aliased to the new ones for backwards compatibility). If we start having to define "overridden" or abstract components at the Java level then it turns into a whole 'nuther beast and I worry that we lose some of the genericity of component definition that we have now in wicket. On first glance I believe that your suggestion may create problems for backwards compatibility with existing pages using the current <child><extend> feature. It would mean people would have to add addAbstractMarkup to their existing pages to allow them to work in the new system which would be a bad thing I think. Ok, I can stop hating myself now ;) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
