Hi,
I've not been able to follow the discussion on generics (simply too
much) but now that I've switched to 1.4-M3 I have a comment/question.
Generally I think wicket is going in the right direction regarding
generics...
Another (great) web application framework that I've used doesn't have
"component" at the root of the inheritance tree, but "element" -
"component" extends "element". The elements are the UI atoms, and
components are complete or partial pages.
I think elements should be generified, but not components.
As it is now Component is not generified, but further down you introduce
generics to some components that you feel benefit from it. I think you
should do it the other way around. Have a root - Element - that is
generified, and then have a Component class where you fix the type
parameter to something suitable.
To me the elements - the basic building blocks - are closely related to
their models and converters, but complete or partial pages are not.
1) I think Label should be generified the way TextField is. (It would be
if they both inherited from Element.)
2) I think think the Model and Converter of TextField should be
generified with the same type parameter as TextField itself - the way it
was in M2. (This could be defined in Element.)
/Anders
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
