Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #40784 All Revisions ] Back to Issue ]
Summary 0040784: provide a consistent mechanism to load messages in client
Revision 2019-05-06 09:45 by alostale
Description Currently, messages defined in AD_Message are loaded in the client side according to one of these two mechanisms:

1. Back-office
  * Messages in core module: only those flagged as "Force Availability in Client"
  * Messages in any other module: all of them are loaded

2. Mobile applications (such as WebPOS or AWO)
  The messages available in the client are [1]:
    * The ones defined in Mobile Core Infrastructure module
    * The ones defined in current mobile application module
    * The ones defined in any module depending (at any level) on current mobile application module


This has some inconveniences:

1. Inefficiencies: messages intended to be used only by backend processes are also loaded in the client
2. Some cases are not covered: for example, having a module A that depends on mobile.core, and a module B that depends on A and WebPOS, messages defined in A cannot be made available in WebPOS client


---
[1] http://wiki.openbravo.com/wiki/Mobile_Internationalization#Available_Labels [^]
Revision 2019-05-06 09:40 by alostale
Description Currently, messages defined in AD_Message are loaded in the client side according to one of these two mechanisms:

1. Back-office
  * Messages in core module: only those flagged as "Force Availability in Client"
  * Messages in any other module: all of them are loaded

2. Mobile applications (such as WebPOS or AWO)
  The messages available in the client are [1]:
    * The ones defined in Mobile Core Infrastructure module
    * The ones defined in current mobile application module
    * The ones defined in any module depending (at any level) on current mobile application module


This has some inconveniences:

1. Inefficiencies: messages intended to be used only by backend processes are also loaded in the client
2. Some cases are not covered: for example, having a module A that depends on mobile.core, and a module B that depends on A and WebPOS, messages defined in B cannot be made available in WebPOS client


---
[1] http://wiki.openbravo.com/wiki/Mobile_Internationalization#Available_Labels [^]


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker