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
Second browser window for customer display #422
Comments
i have done something similar to it. but using Raspberry pi 5inch display and python script to fetch discounted product from DB and show to people in queue in my supermarket. |
Probably just a matter of adding a new view to the app and showing this in a separate window (which can then be dragged onto another monitor?) |
if you know how the schema works, you can create a button that opens anew page for the items list. how you display the list can be up to you. you may need to also create permissions/access rights for it. |
As @sgr1875 suggested, having a rasperry pi with a small screen offering websocket server functionality could be an option. From cash register or receipt the websocket client would need to write the total. You could use the screen during other phases too for ads or showing the logo. |
I have done this only for discounted products but i am looking showing the current bill value and change show. |
You probably need to use a websocket to push it to your raspberry pi. If you search on github you can find examples for rapsberry pi and on the Sales register page you need to add a javascript to read what you need and push it to a websocket. |
It would be probably nice to have the feature supported in Sales register to push data on a websocket to a websocket server. |
I think a really cool feature would be showing a (themable?) item list in a separate window.
That way, a second monitor could be facing the customer with a fullscreen browser window. It could show the items in the current sale, and a static image or background when no sale is in progress.
If it were in the same browser instance as the "regular" interface, it probably wouldn't be hard to implement.
The text was updated successfully, but these errors were encountered: