[
https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13808624#comment-13808624
]
Thiago H. de Paula Figueiredo commented on TAP5-2211:
-----------------------------------------------------
Barry brings some good points, specially the component vs mixin approach one.
Implementing a mapping between the SimpleDateFormat and JS date formats (which
I think it would actually be the jQuery UI DatePicker one) would be another
support nightmare, with probable many filed JIRA in the future. It would be
solving a problem by creating another.
Anyway, you're not obligated to use Tapestry's DatePicker and it's easy to
override the edition block for Date fields to use whatever way of editing dates
you want, as the tapestry-datepicker project source linked above proves. Maybe
the better solution is to fix the Tapestry's current DatePicker instead of
replacing it, but I really don't know what's the best solution for sure.
Barry, actually, DateFormat is an abstract class and I guess almost all
instances of it are SimpleDateFormat ones, which do have a field for getting
the format (pattern). </pedantic>
> 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
> 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)
