[
https://issues.apache.org/jira/browse/WOOKIE-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791983#action_12791983
]
Scott Wilson commented on WOOKIE-67:
------------------------------------
I've now completed localization of Name, Description, License, Icon and
StartFile, and added a localized access method (see the LocalizationUtils class)
I've added a locale parameter to the controllers, and implemented this for the
Widgets and WidgetServices APIs.
Still to-do:
- implement locale parameters for requesting Widget Instances
- implement charset selection for StartFiles
> Implement localization of widgets on per-instance basis
> -------------------------------------------------------
>
> Key: WOOKIE-67
> URL: https://issues.apache.org/jira/browse/WOOKIE-67
> Project: Wookie
> Issue Type: Task
> Components: Configuration, Server, Wookie REST API
> Reporter: Scott Wilson
> Priority: Critical
> Fix For: 0.8.1
>
> Original Estimate: 4h
> Time Spent: 3h
> Remaining Estimate: 6h
>
> While the W3C Widgets specification supports localization we haven't
> implemented the hooks for this within Wookie. In particular, we need to
> consider whether to support locales on a per instance basis - e.g. to allow
> the container to set preferred locale when requesting a widget instance by
> adding a "locale" optional parameter in the REST API.
> This would require a rethink of the Widget object model; currently the
> WidgetManifestModel supports multiple localized values and has
> getLocal<Property>(locale) methods, but these are compressed into singular
> properties when a Widget object is created from it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
