[
https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13808727#comment-13808727
]
Lenny Primak commented on TAP5-2211:
------------------------------------
As far as fixing "old" DateField, (which I could accept as an option)
isn't that difficult either.
Perhaps we could start with that as well
There are "showstopper" datefield issues:
https://issues.apache.org/jira/browse/TAP5-1845
https://issues.apache.org/jira/browse/TAP5-2203
https://issues.apache.org/jira/browse/TAP5-2003
https://issues.apache.org/jira/browse/TAP5-805
https://issues.apache.org/jira/browse/TAP5-1998
https://issues.apache.org/jira/browse/TAP5-2173
https://issues.apache.org/jira/browse/TAP5-2144
Plus one more (localization)
to show "September 2013" as opposed to "2013 September" in the title:
http://code.google.com/p/flowlogix/wiki/TLCalendarPopupPatch
> Replace DatePicker with JQueryUI DatePicker
> -------------------------------------------
>
> Key: TAP5-2211
> URL: https://issues.apache.org/jira/browse/TAP5-2211
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Lenny Primak
> Assignee: Thiago H. de Paula Figueiredo
> Labels: datefield, datepicker
>
> The current 3rd party datepicker used by Tapestry is very old,
> and isn't very good. It's time to update it to one of
> the better currently-available datepickers.
> There are about 15 unresolved issues opened against Datepicker that can all
> be solved by just replacing it.
> I suggest JQueryUI datepicker (if JQuery is included as the default stack)
> The current datepicker can be left alone is prototype is chosen.
> By default, JQueryUI datepicker should be used with the button-to-activate
> option so that it looks similar to the current datepicker.
> It should also work properly in BeanEditor and friends and even look good
> with form-horizontal version of BeanEditor
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
