-
Notifications
You must be signed in to change notification settings - Fork 30.1k
[IMP] point_of_sale: remove customer display configuration #201637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[IMP] point_of_sale: remove customer display configuration #201637
Conversation
11b11e8
to
ef49de6
Compare
ef49de6
to
660869d
Compare
1062843
to
cd72e3b
Compare
cd72e3b
to
11faaa9
Compare
61d4590
to
9d40845
Compare
addons/point_of_sale/static/src/app/components/navbar/navbar.xml
Outdated
Show resolved
Hide resolved
addons/point_of_sale/static/src/customer_display/customer_display_adapter.js
Outdated
Show resolved
Hide resolved
fe79006
to
618130c
Compare
addons/point_of_sale/static/tests/generic_helpers/offline_util.js
Outdated
Show resolved
Hide resolved
6111503
to
c0f9f6f
Compare
as i understand, one of the goals of the task was to be able to use the customer display even if the same config is used on different devices, i.e.:
Is this not the case ? If it is indeed, then you can do this in a different commit |
b607875
to
65fd6d5
Compare
ba18c58
to
2beb82d
Compare
2beb82d
to
8f39f9a
Compare
addons/point_of_sale/static/src/app/customer_display/customer_display_qr_code_popup.js
Outdated
Show resolved
Hide resolved
addons/point_of_sale/static/src/app/components/navbar/navbar.js
Outdated
Show resolved
Hide resolved
addons/point_of_sale/static/src/app/components/navbar/navbar.js
Outdated
Show resolved
Hide resolved
addons/point_of_sale/static/src/app/customer_display/customer_display_qr_code_popup.xml
Outdated
Show resolved
Hide resolved
addons/point_of_sale/static/src/app/customer_display/customer_display_qr_code_popup.xml
Outdated
Show resolved
Hide resolved
Before this commit: ===================== Customer display configuration included three options: local, remote, and proxy, making the setup more complex. After this commit: ================ Customer display is now always enabled by default, removing the need for configuration in res config settings. This simplifies the setup and ensures the feature is always available. Task-4604770 Related Enterprise PR:odoo/enterprise#81395 Related Upgrade PR:odoo/upgrade#7386
In this commit: ================ Moved the customer_display_adapter file from the customer_display folder to pos/app/customer_display because it contains logic that is directly used by the POS app. The principle is to keep all code used by the POS app within the pos/app directory. This change helps maintain a consistent structure where all dependencies used in POS are centralized in its app directory.
…uuid In this commit: ================ - Implemented support for customer display on a per-device basis using `device_uuid`. - Customer display will now run per POS config session based on the device, ensuring each device maintains its own independent display. Ex: - Open POS Config 1 on Device A. - Open the same POS Config 1 on Device B. - Start the customer display on both devices. - Add a product line to the order on Device A. - `The line will appear only on the customer display linked to Device A not Device B.` - Added a popup for small devices to display a QR code and link for the customer display. - The QR/link can be scanned or copied to run the POS and customer display on separate devices easily. Task-4604770
…atus In this commit: ================== The use_proxy getter method was incorrectly referenced, while the actual method name was useProxy. This mismatch prevented the UI from displaying the correct status of the proxy customer display. Updated the reference to use the correct method name.
8f39f9a
to
f2d0e58
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
robodoo rebase-ff r+
Merge method set to rebase and fast-forward. |
Before this commit: ===================== Customer display configuration included three options: local, remote, and proxy, making the setup more complex. After this commit: ================ Customer display is now always enabled by default, removing the need for configuration in res config settings. This simplifies the setup and ensures the feature is always available. Task-4604770 Related Enterprise PR:odoo/enterprise#81395 Related Upgrade PR:odoo/upgrade#7386 Part-of: #201637 Signed-off-by: Vlad Stroia (vlst) <vlst@odoo.com>
In this commit: ================ Moved the customer_display_adapter file from the customer_display folder to pos/app/customer_display because it contains logic that is directly used by the POS app. The principle is to keep all code used by the POS app within the pos/app directory. This change helps maintain a consistent structure where all dependencies used in POS are centralized in its app directory. Part-of: #201637 Related: odoo/enterprise#81395 Related: odoo/upgrade#7386 Signed-off-by: Vlad Stroia (vlst) <vlst@odoo.com>
…uuid In this commit: ================ - Implemented support for customer display on a per-device basis using `device_uuid`. - Customer display will now run per POS config session based on the device, ensuring each device maintains its own independent display. Ex: - Open POS Config 1 on Device A. - Open the same POS Config 1 on Device B. - Start the customer display on both devices. - Add a product line to the order on Device A. - `The line will appear only on the customer display linked to Device A not Device B.` - Added a popup for small devices to display a QR code and link for the customer display. - The QR/link can be scanned or copied to run the POS and customer display on separate devices easily. Task-4604770 Part-of: #201637 Related: odoo/enterprise#81395 Related: odoo/upgrade#7386 Signed-off-by: Vlad Stroia (vlst) <vlst@odoo.com>
…atus In this commit: ================== The use_proxy getter method was incorrectly referenced, while the actual method name was useProxy. This mismatch prevented the UI from displaying the correct status of the proxy customer display. Updated the reference to use the correct method name. closes #201637 Related: odoo/enterprise#81395 Related: odoo/upgrade#7386 Signed-off-by: Vlad Stroia (vlst) <vlst@odoo.com>
Before this commit:
Customer display configuration included three options: local, remote, and proxy,
making the setup more complex.
After this commit:
Customer display is now always enabled by default, removing the need for
configuration in res config settings. This simplifies the setup and ensures
the feature is always available.
Task-4604770
Related Enterprise PR:https://github.com/odoo/enterprise/pull/81395
Related Upgrade PR:https://github.com/odoo/upgrade/pull/7386