[ADD] pos_pywebdriver: support pywebdriver printing, even in Enterprise installs#1571
[ADD] pos_pywebdriver: support pywebdriver printing, even in Enterprise installs#1571dreispt wants to merge 1 commit into
Conversation
78bbda5 to
a14118c
Compare
There was a problem hiding this comment.
Thanks for providing this module !
I faced similar issue some monthes ago on v18, and loose time before understanding pywebdriver and pos_iot was incompatible... A lot of ugly code in Odoo on that topic !
FYI, a new project exists that provide similar features as pywebdriver. it is used in GRAP & Coop It easy for the time being. Maybe a more generic name could be great. (pos_without_iot / pos_community_driver ... not a blocking point, though).
You can take a look here :
https://gitlab.com/grap-rhone-alpes/odoo-driver
(In a few word : it replace pywebdriver in a more modern way, with plugin, etc. BUT, there is no installer for windows).
|
Thank you @legalsylvain . The point for I don't know if your In the end of the day, I wish we had a project like |
a14118c to
3f80ac6
Compare
|
Thanks for your answer.
Interesting. Could you elaborate ? What are the features that are missing for you ?
I thought the same thing at first, when I created pywebdriver. |
| help="Connect receipt printer via a PyWebDriver proxy instead of IoT Box.", | ||
| default=False, | ||
| ) | ||
| pywebdriver_ip = fields.Char( |
There was a problem hiding this comment.
Sorry. I dont understand why not use native field. Proxy_ip
https://github.com/odoo/odoo/blob/19.0/addons/point_of_sale/models/pos_config.py#L125
|
@legalsylvain We do have the maintainer role under the OCA, that can own a roadmap. I think this ends up being OK as long as there are multiple maintainers, that make the project move forward in bursts, at different point in time. So moving it into the OCA could allow for different people in different moment make it move forward. |
|
@dreispt : I propose to move this discussion here pywebdriver/pywebdriver#57 thanks ! |
No description provided.