You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any thoughts or opinions about adding a debugging GUI? I'd be willing to write and demonstrate a PyQt5 gui. Would probably end up looking like a tree-view for each device with a toolbar that has buttons for adding new device, deleting an existing device, repair network, etc.. Each node on the tree would give the latest information and allow its features to be directly controlled. I could see it turning into a pretty useful tool for debugging and even general z-wave development (adding new devices that have very little available information, e.g. the Ring security front panel and door/window sensors which are using some of the proprietary codes but are still accessible from a z-wave USB device).
Qt5 and the PyQt5 bindings are both GPLv3 so there shouldn't really be any licensing issues. It might be better to throw it in a separate library (pyzwaver_gui for example) so that this library doesn't have a hard dependency to the GUI, which would be better for those that don't need it).
Thoughts?
The text was updated successfully, but these errors were encountered:
example_webserver.py implements a web based GUI.
It is quite rough but it would better to improve it than to add a completely
new GUI. Also, more people are familiar with web technologies than Qt.
Any thoughts or opinions about adding a debugging GUI? I'd be willing to write and demonstrate a PyQt5 gui. Would probably end up looking like a tree-view for each device with a toolbar that has buttons for adding new device, deleting an existing device, repair network, etc.. Each node on the tree would give the latest information and allow its features to be directly controlled. I could see it turning into a pretty useful tool for debugging and even general z-wave development (adding new devices that have very little available information, e.g. the Ring security front panel and door/window sensors which are using some of the proprietary codes but are still accessible from a z-wave USB device).
Qt5 and the PyQt5 bindings are both GPLv3 so there shouldn't really be any licensing issues. It might be better to throw it in a separate library (
pyzwaver_gui
for example) so that this library doesn't have a hard dependency to the GUI, which would be better for those that don't need it).Thoughts?
The text was updated successfully, but these errors were encountered: