I see. Also the two DateTextField have no functional difference. This is
in short what I would do:
Remove:
/wicket-datetime/src/main/java/org/apache/wicket/datetime/DateConverter.java
Move to wicket-utils:
/wicket-datetime/src/main/java/org/apache/wicket/datetime/PatternDateConverter.java
/wicket-datetime/src/main/java/org/apache/wicket/datetime/StyleDateConverter.java
Move to wicket-extensions:
/wicket-datetime/src/main/java/org/apache/wicket/datetime/markup/html/basic/DateLabel.java
Merge wicket-datetime DateTextField into the existing wicket-extensions
DateTextField. The first one has a DateConverter as constructor
parameter which is used internally instead of a more generic
IConverter<Date>. it would be nice to have single component with the
same constructors of the existing two.
What do you think?
On 06/02/15 14:24, Sebastien wrote:
Hi devs,
Actually Wicket jQuery UI's DatePicker extends org.apache.wicket.
*extensions*.markup.html.form.DateTextField
By the way, Wicket Utils already have
org.apache.wicket.*util*.convert.converter.DateConverter.
I did not check the differences..
DateLabel & PatternDateConverter are probably convenient. I didn't know
they exists so I write them for my work purpose, I suppose many users did
the same... So why not moving them to *wicket-extensions* as well...
Best regards,
Sebastien.
On Fri, Feb 6, 2015 at 2:02 PM, Sven Meier <s...@meiers.net> wrote:
