Project:
| View Revisions: Issue #45785 | [ Back to Issue ] | ||
| Summary | 0045785: Move hardware manager communication API to mobile.core | ||
| Revision | 2022-08-30 09:35 by caristu | ||
| Description | Currently all the logic to communicate with the hardware manager is centralized in the posterminal module. It should be moved to the mobile.core module so other applications (awo) can also perform hw manager operations like printing. This includes the following tasks: 1- move code. Note that those parts of the code referencing to ticket/orders must be kept in posterminal. (Example: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/blob/master/web/org.openbravo.retail.posterminal/app/external-device/ExternalDeviceController.js#L262 [^]) 2- create/move template backend and HWM definitions |
||
| Revision | 2022-08-29 12:49 by caristu | ||
| Description | Currently all the logic to communicate with the hardware manager is centralized in the posterminal module. It should be moved to the mobile.core module so other applications (awo) can also perform hw manager operations like printing. This includes the following tasks: 1- move code. Note that those parts of the code referencing to ticket/orders must be kept in posterminal. (Example: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/blob/master/web/org.openbravo.retail.posterminal/app/external-device/ExternalDeviceController.js#L262 [^]) 2- create/move template backend and HWM definitions 3- [NEW POS] Register hwmanager endpoint in core2 to keep consistency mobile.core<->core2 and posterminal<->pos2 |
||
| Revision | 2022-08-29 12:49 by caristu | ||
| Description | Currently all the logic to communicate with the hardware manager is centralized in the posterminal module. It should be moved to the mobile.core module so other applications (awo) can also perform hw manager operations like printing. This includes the following tasks: 1- move code. Note that those parts of the code referencing to ticket/orders must be kept in posterminal. (Example: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/blob/master/web/org.openbravo.retail.posterminal/app/external-device/ExternalDeviceController.js#L262 [^]) 2- create/move template backend definitions 3- [NEW POS] Register hwmanager endpoint in core2 to keep consistency mobile.core<->core2 and posterminal<->pos2 |
||
| Revision | 2021-02-02 12:33 by caristu | ||
| Description | Currently all the logic to communicate with the hardware manager is centralized in the posterminal module. It should be moved to the mobile.core module so other applications (awo) can also perform hw manager operations like printing. This includes the following tasks: 1- move code. Note that those parts of the code referencing to ticket/orders must be kept in posterminal. (Example: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/blob/master/web/org.openbravo.retail.posterminal/app/external-device/ExternalDeviceController.js#L262 [^]) 2- create/move backend definition 3- Some utilities for creating messages for printing are in core2. (See here: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/blob/master/web/org.openbravo.mobile.core/app/model/business-object/messages/MessagesUtils.js#L87 [^]) They should be moved to posterminal. 4- [NEW POS] Register hwmanager endpoint in core2 to keep consistency mobile.core<->core2 and posterminal<->pos2 |
||
| Revision | 2021-01-29 14:30 by caristu | ||
| Description | Currently all the logic to communicate with the hardware manager is centralized in the posterminal module. It should be moved to the mobile.core module so other applications (awo) can also perform hw manager operations like printing. This includes the following tasks: 1- move code 2- create/move backend definition 3- Some utilities for creating messages for printing are in core2. (See here: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/blob/master/web/org.openbravo.mobile.core/app/model/business-object/messages/MessagesUtils.js#L87 [^]) They should be moved to posterminal. 4- [NEW POS] Register hwmanager endpoint in core2 to keep consistency mobile.core<->core2 and posterminal<->pos2 |
||
| Revision | 2021-01-26 11:23 by caristu | ||
| Description | Currently all the logic to communicate with the hardware manager is centralized in the posterminal module. It should be moved to the mobile.core module so other applications (awo) can also perform hw manager operations like printing. This includes the following tasks: 1- move code 2- create/move backend definition 3- [NEW POS] Register hwmanager endpoint in core2 to keep consistency mobile.core<->core2 and posterminal<->pos2 |
||
| Revision | 2021-01-26 11:22 by caristu | ||
| Description | Currently all the logic to communicate with the hardware manager is centralized in the posterminal module. It should be moved to the mobile.core module so other applications (awo) can also perform hw manager operations like printing. This includes the following tasks: 1- move code 2- create/move backend definition 3- [NEW POS] Register hwmanager endpoint in core2 to keep consistency mobile.core-core2 and posterminal-pos2" |
||
| Revision | 2021-01-26 11:22 by caristu | ||
| Description | Currently all the logic to communicate with the hardware manager is centralized in the posterminal module. It should be moved to the mobile.core module so other applications (awo) can also perform hw manager operations like printing. This includes the following tasks: 1- move code 2- create/move backend definition 3- (NEW POS)Register hwmanager endpoint in core2 to keep consistency mobile.core-core2 and posterminal-pos2" |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |