Re: users, please give us your opinion: what is your take on generics with Wicket

Hi *,

My point of view, static type checking is more important as API cleareness. In any case using modern IDE make more help in this area.
Some exercises in also useful for programmers (but not coders though :). Wicket was born as a framework for the qualified programmers. I think no reason why wicket should demote self for anybody, who can not understand generics.

1) Generifying* Wicket
   [x] Can best be done like currently in the 1.4 branch, where models
and components are both generified. I care most about the improved
static type checking generified models and components give Wicket.
   [ ] Can best be done in a limited fashion, where we only generify
IModel but not components. I care more about what generifying can do
for API clarity (declaring a component to only accept certain models
for instance) than static type checking.
   [ ] Should be avoided, I prefer the way 1.3 works. Because... (fill
in your opinion here).
   [ ] .... (anything other than these choices?)

2) How strongly do you feel about your choice above?
   [x] Whatever choice ultimately made, I'll happily convert/ start
using 1.4 and up.
   [ ] I might rethink upgrading if my choice doesn't win.
   [ ] I definitively won't be using 1.4. if Wicket doesn't go for my
preference.

Thanks