What can be extracted from all this information, is that all Openbravo modules should be rendered properly in a 9/16 aspect ratio, because this is the aspect ratio where the components will have the smaller size, and they should display properly even with this size. From this point, the UI starts to be "taller", but components width remain the same. In portrait mode, the content is compressed horizontally until the UI reaches the 9/16 aspect ratio. From this point, it switch to portrait mode. In landscape, the content is compressed horizontally until the UI reaches the mentioned 9/8 aspect ratio. The switch is made when the aspect ratio of the screen is larger (or smaller) than 9/8. In landscape mode it displays two columns, and in portait mode just one, with an enhaced toolbar to be able to reach all views from just one single column.
Openbravo layout is automatically adapted depending on if it is being displayed in landscape or portrait mode. Openbravo UI Landscape vs Portrait display 3.3.2 Receipt Total and Taxes Breakdown.3.2.3 Modal Dialog Button - Auxiliar Action.3.2.2 Modal Dialog Button - Default Action.2.6 Screen Backgrounds and Surfaces - Popup.2.5 Screen Backgrounds and Surfaces - MainScreen.1 Openbravo UI Landscape vs Portrait display.
#OPENBRAVO WEB POS HOW TO#
The development document How to create a new device driver explains the details how to develop a new module that implements this integration.įrom the Web POS side there exist the Payment Gateway connector for Retail Module that implements the integration of Web POS with any payment device connected to the Hardware Manager. The Payment Gateway must offer libraries that can be used from Java that is the language used in the Hardware Manager. In this option, the device will be connected to the machine where the Hardware Manager is running and it requires a Hardware Manager device driver that implements the communication with the payment device. Also moves all the security concerns outside the Web POS application because all the communication of the sensitive data will be just between the payment device and the Payment Gateway and Web POS will not be part of this communication. In this case it is only needed to have configured a payment method to be used with the payment device and the cashier will be responsible of performing the payment entering the amount to pay using the payment device when the configured payment method in Web POS is selected.ĭirect communication of the payment device with the Payment Gateway removes the communication management responsibility outside the Web POS application. Web POS and the payment device are not connected and do not share information. In this document you can find the different payments integration models offered in Web POS you can use for the different payment solutions in the market. All the sensitive data manipulation should be left to the payment solution integrated with Web POS. Web POS payments integration models are also focused to security, enforcing to follow the international security standards by not storing or managing any sensitive data in the payment transaction.
To offer the best purchasing experience to customers, Web POS has different integration models for payment devices and payment gateways that allows stores to use all the electronic payment methods needed. It is optimized to run on mobile devices like tablets or smartphones, and desktop computers with touch screen support. Openbravo Web POS is a light, fast and very user friendly solution. It is used in stores to assist shop floor staff in client-side selling and enables the checkout process. The Openbravo Web POS is the POS component included in the Openbravo Commerce Suite. 2.2.3 Proxy the communication by the Hardware Manager.2.2.1 The user interface for the payment.