[
https://issues.apache.org/jira/browse/TAPESTRY-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625999#action_12625999
]
Ernest Monklitch commented on TAPESTRY-2617:
--------------------------------------------
So if I understand correctly the first datefield to get localized date names
would trigger AJAX call to the server and then the result would be cached to
client side if there are more datefields in the page?
Either that approach or then supply the names as parameters in DateField.java
setup.put("field", clientId);
setup.put("parseURL",
resources.createEventLink("parse").toAbsoluteURI());
setup.put("formatURL",
resources.createEventLink("format").toAbsoluteURI());
support.addInit("dateField", setup);
This would add the size of the original response, but would save one round trip
to server. (Which approach is more efficient depends on the number of
datefields in the page)
I would like to see the no-server-round-trip approach, as usually there are max
2 datefields in one page.
> Localize datefield
> ------------------
>
> Key: TAPESTRY-2617
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2617
> Project: Tapestry
> Issue Type: Bug
> Affects Versions: 5.0.14
> Environment: All
> Reporter: Ernest Monklitch
> Fix For: 5.0.15
>
>
> Datefield is almost localized as TAPESTRY-1856 is closed, but still the UI of
> the date selector is hard coded to use english day and month names. Please
> fix this too.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
