On Sun, Jun 1, 2008 at 9:44 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > 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. > [half-X] 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?)
I see the stronger-typing made possible with Generics as a step forward for Java and for Wicket. I believe that Generics will improve my code, and make my life easier. I understand that actually implementing the Generified objects is harder than using them, and that this task rests mostly on the devs' shoulders! > 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. Whatever the devs decide, I'm not going to stop using Wicket (or refuse to upgrade forever more) just because they've not implemented something exactly the way I personally prefer! I have faith that, with discussion, the "right" decision will be made for the framework as a whole. After all, if I weren't happy to go along with the majority view, I'd have to write everything myself... Charlie. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
