[jira] Commented: (TAPESTRY-2198) Date formating global support

["Geoff Callender (JIRA)" <de...@tapestry.apache.org>]

    [ https://issues.apache.org/jira/browse/TAPESTRY-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572454#action_12572454 ] 

Geoff Callender commented on TAPESTRY-2198:
-------------------------------------------

I wouldn't restrict the formatting info to message catalogs - I'd like it to be a parameter on the component.  I've worked on data-entry systems pre-Java where the display format is a user-level option, eg. ddMMMyy (26FEB08) vs dd/MM/yy (26/02/08) vs dd/MM/yyyy (26/02/2008).  This is something users appreciate.

It's worth noting too that the format that suits users in DateField is often different to the format they like to see in list output, eg. yyyy-MM-dd is popular when the user needs to be able to quickly compare dates in a list.

As for inputting into a DateField, it would be nice to be able to plug in your own parsing (ie. easily able to extend DateField and override the input parsing) to allow whatever rules you like - in data-entry entry it's nice to be able to enter ddMMyy or even ddMM and have it displayed back in one of the above formats.  In trading rooms they even like stuff like 1m, meaning today plus 1 month.

The difficult I've had with extending Tapestry's date pickers to date is that they've used private fields without public getters and setters, and often the methods are final.

> Date formating global support
> -----------------------------
>
>                 Key: TAPESTRY-2198
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2198
>             Project: Tapestry
>          Issue Type: Improvement
>    Affects Versions: 5.0.11
>            Reporter: Davor Hrg
>
> there is a javascript implementation of
> SimpleDateFormat and is apache 2.0 licensed
> http://www.timdown.co.uk/code/simpledateformat.php
> it implements most of:
> http://java.sun.com/j2se/1.5.0/docs/api/java/text/SimpleDateFormat.html
> It is 8.7 Kb with stripped comments.
> I'm looking at making a trimmed down version that can parse/format only numeric date parts : day, month, year, dour, min sec.
> This covers most likely usages on the client side (forms and datefield) and would make shorter code. 
> (I feel that prototype is bloated already so another 10K does not look apealing)
> Not to complicate things and optimize too soon, full lib can be used now,
> and later along with "multiple js lib support" the short version should be made available and pushed as default.
> while talking about dates... date format should be in message catalog so it is locale specific.
> for example in my language date format is: dd.MM.yyyy
> there should be different keys for server side format and client side format
> (the formats should be compatible of course)
> tapestry-date-format-server=MM/dd/yyyy
> tapestry-date-format-js=MM/dd/yyyy
> (which are sam in case we use forementioned lib)
> or, if one would choose to use the former date picker i would be:
> tapestry-date-format-server=MM/dd/yyyy
> tapestry-date-format-js=%m.%d.%Y
> I feel strongly about this being global  key instead parameter for
> datefield, but even if it is only for date-field there should be two formats (server and js)
> in the end... the formater should be used to test validity for the field on the client side
> or regexp added to message catalog
> tapestry-date-format-js-regex=...complex or simple regex......

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org