You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Juergen Donnerstag (JIRA)" <ji...@apache.org> on 2010/11/27 21:39:37 UTC
[jira] Resolved: (WICKET-3158) DateField, DateTimeField classes
available, but no TimeField
[ https://issues.apache.org/jira/browse/WICKET-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juergen Donnerstag resolved WICKET-3158.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.5-M4
Assignee: Juergen Donnerstag
thanks
> DateField, DateTimeField classes available, but no TimeField
> ------------------------------------------------------------
>
> Key: WICKET-3158
> URL: https://issues.apache.org/jira/browse/WICKET-3158
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-datetime
> Affects Versions: 1.4.13
> Reporter: Adrian Sud
> Assignee: Juergen Donnerstag
> Fix For: 1.5-M4
>
> Attachments: TimeField.java
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> There are many instances in which one will want to collect a Time from a user when it is unnecessary to also collect a date.
> In wicket-datetime there is a class for DateField and DateTimeField, so that you can collect a date with a time, or a date separately, but no method for collecting a time alone.
> Creating the TimeField class from Eelco's DateTimeField class is almost trivially easy, by removing the date portions of the class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.