Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 270603 - Riena extension points must respect translatable attributes.
Summary: Riena extension points must respect translatable attributes.
Status: CLOSED FIXED
Alias: None
Product: Riena
Classification: RT
Component: navigation (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.1.0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-31 10:02 EDT by Stefan Flick CLA
Modified: 2009-11-18 11:02 EST (History)
1 user (show)

See Also:


Attachments
translateable attribute for assembly extension point (4.41 KB, patch)
2009-03-31 10:10 EDT, Stefan Flick CLA
christian.campo: iplog+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Flick CLA 2009-03-31 10:02:21 EDT
There is a need to translate extension point scheme attributes for NLS support. The eclipse extension points are almost fine. For Riena extension points is no translatable attriube defiend. 
Please check all Riena extensionpoint for sinfull translatable attributes. 
In the attached patch is the extended org.eclipse.riena.navigation.navigationNode assembly extension point schema.
Comment 1 Stefan Flick CLA 2009-03-31 10:10:55 EDT
Created attachment 130388 [details]
translateable attribute for assembly extension point
Comment 2 Christian Campo CLA 2009-04-05 15:58:19 EDT
I think having translatable extension points make sense. I am however not sure why typeId, parentTypeId, view (id) or autostartsequence should be translatable.

I understand name, label or icon. Maybe you can elaborate on this. Otherwise we would restrict translatable to places where it makes sense.
Comment 3 Christian Campo CLA 2009-04-06 08:18:21 EDT
I have made the attributes name, label and icon translatable in the assembly schema.
Comment 4 Christian Campo CLA 2009-04-06 08:19:49 EDT
closed