[ALOY-967] Support i18n directory in widgets
| GitHub Issue | n/a |
|---|---|
| Type | New Feature |
| Priority | High |
| Status | Resolved |
| Resolution | Fixed |
| Resolution Date | 2015-02-13T18:26:25.000+0000 |
| Affected Version/s | Alloy 1.3.1 |
| Fix Version/s | Alloy 1.7.0 |
| Components | I18N, Widgets |
| Labels | n/a |
| Reporter | Alan Leard |
| Assignee | Feon Sua Xin Miao |
| Created | 2014-03-06T14:53:32.000+0000 |
| Updated | 2015-02-13T20:32:27.000+0000 |
Description
Customers have requested support for widget specific i18n localization files. This would be useful for fully independent UI widgets.
Attachments
| File | Date | Size |
|---|---|---|
| Screen Shot 2014-06-13 at 1.24.14 pm.png | 2014-06-13T05:29:43.000+0000 | 45025 |
| Test.zip | 2014-06-09T15:41:24.000+0000 | 5926862 |
[~aleard] I think I know what you're asking for here. But some clarification would help me and QE. Could you post a sample app showing how you'd like this to work, plus any considerations or details describing how a developer would implement this feature?
I have attached a sample app. Notice that the included widget has its own i18n directory and its own set of language strings. The widget developer should be able to independently manage the language included in any of their UI elements without having to ask the application owner to modify their strings.xml files at an application level.
PR: https://github.com/appcelerator/alloy/pull/446 Test app: https://github.com/feons/alloy/tree/ALOY-967/test/apps/testing/ALOY-967 Functional Test: 1. Run the test app on ios 2. The localized strings from each widgets are displayed as illustrated by the attached screenshot.
Updated functional test steps: You can use Feon's test app (included in the PR). However, you can't run it using the jake test harness. Instead: 1. Create a new Alloy project. 2. Copy the contents of the 967 test app's folder, minus the i18n folder, to your new project's app folder. 3. Copy the test app's i18n folder to your project's root folder 4. Now run the app. Change the language of your simulator/device from English to Spanish. The app name on the springboard should change. Open the app. You get new language strings from both the app and widget labels. 5. Change your sim/device back to English. App name and labels change back to English strings.
PR tested and merged
Reopening for consideration of alternate ways to implement the functionality.
Please work on the blocking ticket, and then take this one.
We will need input & guidance from [~cbarber] on the blocking ticket before we can work on it.
This is resolved by ALOY-858 However, TIMOB-18570 will prevent you from testing/confirming this with the iOS simulator. Use an iOS device or Android emulator to test until that ticket is resolved.