Single inheritance should not be a problem if your design is good, which
means that your components' taxonomy must be consistent.
On the other hand having more component classes brings developers a
stronger abstraction and a more readable code.
I'm -1 on adding more subclasses to Wicket's type h
I'm -1 on adding more subclasses to Wicket's type hierarchy.
We have single inheritance in Java, why waste it for something which could
equally well be implemented with behaviors?
Sven
Am 30.11.2010 um 13:18 schrieb Andrea Del Bene:
> Same for me. I prefer having new component classes with a
Same for me. I prefer having new component classes with a meaningful
name rather then some more "checking type code" under the hood
Just my 0.2 cents...
personally i would prefer to have NumberField, UrlField, etc. based on
some html5 detection (doctype or a setting) it can fallback to pre-5
On Sun, Nov 28, 2010 at 1:26 PM, Martijn Dashorst
wrote:
> The upcoming standard for HTML 5 defines new input types. These are
> currently only relevant for mobile applications, but new versions of
> firefox, Opera and webkit enabled browsers will provide support for
> these types as well.
>
> Unt
The upcoming standard for HTML 5 defines new input types. These are
currently only relevant for mobile applications, but new versions of
firefox, Opera and webkit enabled browsers will provide support for
these types as well.
Until now HTML provided the following input types:
- checkbox
- radio
