[magnolia-dev] [JIRA] (MGNLUI-3721) Improve i18n key generators to work with extends

2016-03-29 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3721 
 
 
 
  Improve i18n key generators to work with extends  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Kromeriz 23 , Kromeriz 37 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3721) Improve i18n key generators to work with extends

2016-03-29 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3721 
 
 
 
  Improve i18n key generators to work with extends  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Kromeriz 23 , Kromeriz 37 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3721) Improve i18n key generators to work with extends

2016-01-13 Thread on behalf of Roman Kovařík 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3721 
 
 
 
  Improve i18n key generators to work with extends  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3721) Improve i18n key generators to work with extends

2015-12-23 Thread on behalf of Roman Kovařík 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3721 
 
 
 
  Improve i18n key generators to work with extends  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 
 
 
 
 
 
 
 The new I18N system does not play nice with the JCR extends mechanism because an extended definition has a new name and will therefore generate translation keys with this new name. So if I extend an App - all of the items with keys that depended on that apps name - will now be untranslated. This is a dealbreaker for Templating because the extends mechanism is so important to effective work. With the new i18n system if I extend a dialog, I would have to copy all of the existing translations for the tabs and fields and change there keys to match the name of the new dialog.Lets say we have a dialog named {{basicLink}}, and we extend it with {{superLink}}, which is extended by {{superDuperLink}}.A key might be{{joesModule.dialogs.basicLink.tabLink.title.label}}There is a POC for dialog key generator in linked PR. We'd need the similar change in most of the generators. It's kind of effort to do this everywhere. The question is if it's worth the effort or we can solve most of the problems by using of less specific keys. (e.g. {{tabMain.fieldNam,label}} instead of { { dialogWhichOtherDialogsExtendsFrom.tabMain.fieldNam , . label}}) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, 

[magnolia-dev] [JIRA] (MGNLUI-3721) Improve i18n key generators to work with extends

2015-12-23 Thread on behalf of Roman Kovařík 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3721 
 
 
 
  Improve i18n key generators to work with extends  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 The new I18N system does not play nice with the JCR extends mechanism because an extended definition has a new name and will therefore generate translation keys with this new name. So if I extend an App - all of the items with keys that depended on that apps name - will now be untranslated. This is a dealbreaker for Templating because the extends mechanism is so important to effective work. With the new i18n system if I extend a dialog, I would have to copy all of the existing translations for the tabs and fields and change there keys to match the name of the new dialog.Lets say we have a dialog named {{basicLink}}, and we extend it with {{superLink}}, which is extended by {{superDuperLink}}.A key might be{{joesModule.dialogs.basicLink.tabLink.title.label}}There is a POC for dialog key generator in linked PR. We'd need the similar change in most of the generators. It's kind of effort to do this everywhere. The question is if it's worth the effort or we can solve most of the problems by using of less specific keys. (e.g. {{tabMain.fieldNam,label}} instead of {dialogWhichOtherDialogsExtendsFrom.tabMain.fieldNam,label}}) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

[magnolia-dev] [JIRA] (MGNLUI-3721) Improve i18n key generators to work with extends

2015-12-17 Thread on behalf of Roman Kovařík 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3721 
 
 
 
  Improve i18n key generators to work with extends  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Project:
 
 Magnolia  UI 
 
 
 

Key:
 
 MAGNOLIA MGNLUI - 6308 3721 
 
 
 

Component/s:
 
 dialogs 
 
 
 

Component/s:
 
 i18n 
 
 
 

Fix Version/s:
 
 5.4.x 
 
 
 

Fix Version/s:
 
 5.4.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)