Return-Path: X-Original-To: apmail-tapestry-dev-archive@www.apache.org Delivered-To: apmail-tapestry-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 81FD61076E for ; Tue, 29 Oct 2013 22:23:26 +0000 (UTC) Received: (qmail 88307 invoked by uid 500); 29 Oct 2013 22:23:26 -0000 Delivered-To: apmail-tapestry-dev-archive@tapestry.apache.org Received: (qmail 88256 invoked by uid 500); 29 Oct 2013 22:23:26 -0000 Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tapestry.apache.org Delivered-To: mailing list commits@tapestry.apache.org Received: (qmail 88206 invoked by uid 99); 29 Oct 2013 22:23:26 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Oct 2013 22:23:26 +0000 Date: Tue, 29 Oct 2013 22:23:26 +0000 (UTC) From: "Lenny Primak (JIRA)" To: commits@tapestry.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (TAP5-2211) Replace DatePicker with JQueryUI DatePicker MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13808531#comment-13808531 ] Lenny Primak edited comment on TAP5-2211 at 10/29/13 10:21 PM: --------------------------------------------------------------- Barry, I don't think that the problem that you mentioned here is unsolvable at all. There can be a mapping between Java and JavaScript DateFormat, and there can be a subclass of DateFormat that returns the format. The whole reason to replace Datepicker in Tapestry is so there is a modern, supported datepicker that's maintained by someone else (JQuery team) and it won't get stale or obsolete soon Also, your textfield solution won't work for BeanEditor. was (Author: lprimak): Barry, I don't think that the problem that you mentioned here is unsolvable at all. There can be a mapping between Java and JavaScript DateFormat, and there can be a subclass of DateFormat that returns the format. The whole reason to replace Datepicker in Tapestry is so there is a modern, supported datepicker that's maintained by someone else (JQuery team) and it won't get stale or obsolete soon > 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)