Hello, my answers to the questions:
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. 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. The reason for my decision is that if a concept will be applied to a framework, then it should be applied thoroughly; in this case generics to all container-like types. But what are the advantages? In my understanding the following: - compile-time type safety - improved readability - improved robustness - eliminiation of casts. But are these the features, which are the most important to the users and deliver the most benefits? I think not the ways, but the objectives should be defined by the Wicket users. For me as a Wicket user the most important is to be more productive by writing less code. Eliminating casts doesn't mean this. Andras -- View this message in context: http://www.nabble.com/users%2C-please-give-us-your-opinion%3A-what-is-your-take-on-generics-with-Wicket-tp17589984p18553155.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
