There has been a discussion about whether or not to generify
component. currently component is generified.
Maurice
On Wed, Apr 9, 2008 at 9:25 AM, John Patterson <[EMAIL PROTECTED]> wrote:
> I like the type-safe getModelObject() and of course it is optional to
> specify a type.
>
>
>
> On 9 Apr 2008, at 14:18, Timo Rantalaiho wrote:
>
>
> > On Wed, 09 Apr 2008, Martijn Dashorst wrote:
> >
> > > If you are depending on trunk and build your own Wicket versions,
> > > please note that trunk is now Wicket 1.4 and will be used for the next
> > > Wicket version.
> > >
> >
> > Is there already a specific plan (or even local changes on
> > Johan's machine :)) on what exactly will be generified?
> >
> > DropDownChoice fooSelection = new DropDownChoice("fooSelection",
> > new Model<Foo>(foo), fooList);
> >
> > or
> >
> > DropDownChoice<Foo> fooSelection = new DropDownChoice<Foo>("fooSelection",
> > new Model<Foo>(foo), fooList);
> >
> > ? Old 2.0 had the latter way of generifying also Component,
> > which removes the need to cast when doing getModelObject(),
> > but adds a lot of clutter in all Component declarations.
> >
> > Have you thought of whether it would make sense to only
> > generify IModel and retain Object in get/setModelObject? Or
> > was this already tried with 2.0?
> >
> > Best wishes,
> > Timo
> >
> > --
> > Timo Rantalaiho
> > Reaktor Innovations Oy <URL: http://www.ri.fi/ >
> >
>
>
