http://weblogs.java.net/blog/timboudreau/archive/2009/07/api_design_vs_a_1.html
I guess he doesn't get why we did the rename. This reminds me that we
*really* should improve our release docs before we finalize 1.4!!!
Martijn
--
Become a Wicket expert, learn from the best:
A good overall read, but he also seemed to miss the reason we have
getModel**Object**. He doesn't think that's necessary, but misses
that there is also getModel (without object) and the word does clarify
the difference.
Anyway, a good read on overall API design, though. I'd recommend it
to
Am 06.07.2009 um 16:18 schrieb Jeremy Thomerson:
A good overall read, but he also seemed to miss the reason we have
getModel**Object**. He doesn't think that's necessary, but misses
that there is also getModel (without object) and the word does clarify
the difference.
Anyway, a good read on
I've just read the explanation in a Tim's blog post comment. Oh, well,
generics definitely isn't easy to grasp...
I myself have observed that my (wicket) code is so much readable without
most generics declarations. Even when using components that do have models
(Textfield, for example) I didn't
What if Component was not generified, and had an 'Object getModel()' method
instead of 'Object getDefaultModel()', and the components that do benefit
from generics, simply override the method to return 'T' (then the component
class would have a T type parameter)? The compiler accepts this just
'IModel? getModel()' instead of 'Object getModel()', and 'IModelT
getModel()' instead of 'T getModel()', sorry.
And sorry for flooding the mailing list, this is the last one, I promise :)
On Mon, Jul 6, 2009 at 3:54 PM, tetsuo ronald.tet...@gmail.com wrote:
What if Component was not
Problem is setDefaultModelObject().
If you have setModelObject(Object o) you can not override it in
subclass and restrict the parameter.
-Matej
On Mon, Jul 6, 2009 at 8:58 PM, tetsuoronald.tet...@gmail.com wrote:
'IModel? getModel()' instead of 'Object getModel()', and 'IModelT
getModel()'
Now I get it, thanks.
Indeed, it's hard to think in a better solution (without ditching generics
altogether).
Tetsuo
On Mon, Jul 6, 2009 at 4:19 PM, Matej Knopp matej.kn...@gmail.com wrote:
Problem is setDefaultModelObject().
If you have setModelObject(Object o) you can not override it in
