Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [sequoyah-dev] Suggestions for the LFE
Hi all, 

as part of the effort of improving Localization File Editor usability, we are proposing some changes in the UI and workflow of the component, documented in the attached document.

Any comments / suggestions / feedback are more than welcome.

Best,
 Marcel

On Mon, Oct 4, 2010 at 5:09 PM, Daniel Pastore <KPQB38@xxxxxxxxxxxx> wrote:
Hi guys,

Using the three areas approach, we could:
- create the structure for the correct implementation of the string array (model side);
- separate string and string array related implementation on the Android package (schema side);
- adjust the editor to work with this new model (editor side).

On Mon, Oct 4, 2010 at 10:40, Matheus Lima <WML044@xxxxxxxxxxxx> wrote:
Thanks for the answer,
 
I'd opened the following bug:
 
Regards,
Math.

On Fri, Oct 1, 2010 at 11:25 AM, Marcel Gorri <WMG040@xxxxxxxxxxxx> wrote:
Matheus, 

this is a great idea. In fact, we had already started a task to support other localizable resources (such as images, video and sound files) and this improvement can be considered part of the scope of this change.

For your proposed improvement, we identify 3 main areas that must be modified in the Localization framework: editor, model and schema.

Can you please open a bug in Bugzilla (project: Sequoyah, component: Localization) with your proposal so we can work on this improvement?

Since we are adopting SCRUM in Sequoyah, we are thinking about attacking those areas in an agile development way. We'll keep you updated about that. 

So let's evolve this discussion with the ideas and next steps for this task.

Best,
 Marcel


On Fri, Oct 1, 2010 at 10:19 AM, Matheus Lima <WML044@xxxxxxxxxxxx> wrote:

Hi all,

 

I’m Matheus and although I’m not a Sequoyah committer I’m working under the direction of a committer, Daniel Pastore, in the same company.

 

My project is using the Sequoyah Localization Files Editor and we have a suggestion: In order to improve the usability, my team is thinking of changing how the Localization Editor handles String Arrays. The first step would be to refactor the data model so the whole localization framework becomes aware of the existence of the array type (currently the Editor itself only knows Strings, not arrays). Once the model is changed this way a next step will be possible, that is: to improve the editor to handle arrays and strings differently and more efficiently.

 

What do you think? Suggestions?

 

Math.


_______________________________________________
sequoyah-dev mailing list
sequoyah-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/sequoyah-dev



_______________________________________________
sequoyah-dev mailing list
sequoyah-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/sequoyah-dev



_______________________________________________
sequoyah-dev mailing list
sequoyah-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/sequoyah-dev




--
Thanks,

Daniel Pastore
Sequoyah Team


_______________________________________________
sequoyah-dev mailing list
sequoyah-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/sequoyah-dev


Attachment: Localization Editor Workflow Improvements.pdf
Description: Adobe PDF document

Back to the top