You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Thibault Kruse <ti...@googlemail.com> on 2015/02/02 14:21:11 UTC
Plans for further wicket classes with generics
Hi,
Already in Wicket there is GenericPanel, GenericWebPage,
GenericFragment, IGenericComponent, and IModel of course is already
generic.
But there is still IBehavior without Generics and several standard
components which do not implement IGenericComponent such a Label.
Are there plans to further promote APIs with generics, also maybe
deprecating the APIs which do not use generics (classes Panel, Page,
etc.)?
Or is there a good reason not to use Generics?
regards,
Thibault
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Plans for further wicket classes with generics
Posted by Thibault Kruse <ti...@googlemail.com>.
I see, I guess this was summarized here:
https://cwiki.apache.org/confluence/display/WICKET/generics
On Mon, Feb 2, 2015 at 2:27 PM, Martin Grigorov <mg...@apache.org> wrote:
> Hi,
>
> There is a discussion about this since Wicket 1.4 (the first version of
> Wicket built against JDK 1.5).
> The main stopper is that using generics makes the code even more verbose.
> And many people don't like this.
> So there are few Generic*** versions of the most used components.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Mon, Feb 2, 2015 at 3:21 PM, Thibault Kruse <ti...@googlemail.com>
> wrote:
>
>> Hi,
>>
>> Already in Wicket there is GenericPanel, GenericWebPage,
>> GenericFragment, IGenericComponent, and IModel of course is already
>> generic.
>>
>> But there is still IBehavior without Generics and several standard
>> components which do not implement IGenericComponent such a Label.
>>
>> Are there plans to further promote APIs with generics, also maybe
>> deprecating the APIs which do not use generics (classes Panel, Page,
>> etc.)?
>>
>> Or is there a good reason not to use Generics?
>>
>> regards,
>> Thibault
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Plans for further wicket classes with generics
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
There is a discussion about this since Wicket 1.4 (the first version of
Wicket built against JDK 1.5).
The main stopper is that using generics makes the code even more verbose.
And many people don't like this.
So there are few Generic*** versions of the most used components.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Mon, Feb 2, 2015 at 3:21 PM, Thibault Kruse <ti...@googlemail.com>
wrote:
> Hi,
>
> Already in Wicket there is GenericPanel, GenericWebPage,
> GenericFragment, IGenericComponent, and IModel of course is already
> generic.
>
> But there is still IBehavior without Generics and several standard
> components which do not implement IGenericComponent such a Label.
>
> Are there plans to further promote APIs with generics, also maybe
> deprecating the APIs which do not use generics (classes Panel, Page,
> etc.)?
>
> Or is there a good reason not to use Generics?
>
> regards,
> Thibault
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>