mirror of
https://github.com/kusti8/proton-native.git
synced 2026-05-15 14:15:50 -06:00
[GH-ISSUE #170] [Question]: USB or Bluetooth #110
Labels
No labels
bug
documentation
enhancement
libui issue
pull-request
question
wait for libui implementation
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/proton-native#110
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @internetstyle on GitHub (Aug 8, 2018).
Original GitHub issue: https://github.com/kusti8/proton-native/issues/170
Is Proton native able to work with USB or Bluetooth? I work with web development, but now I need to make an app that communicates with a device via USB or Bluetooth and I would like to know if Proton Native is recommended for this. Thank you.
@kusti8 commented on GitHub (Aug 8, 2018):
What are you trying to do? Proton native is only the GUI library, meaning that it only displays what you want it to. Anything that happens on the back end with communicating with something else is separate. You need to search for node packages to communicate.
Personally, I would use something like mqtt for communication and skip USB.
@internetstyle commented on GitHub (Aug 8, 2018):
Got it. Thank you. I believe that with node packages I can then do it. I had not understood that Proton Native was just UI. Better yet, because I'm used to React.
MQTT currently I believe that it would not be possible as it is a third party equipment, which I need to monitor via the web. Would using MQTT require hardware changes?
@kusti8 commented on GitHub (Aug 8, 2018):
It entirely depends on how the equipment and your idea of the stack is setup.
What I'm thinking is you have some sort of computer like a raspberry pi interface with the equipment. That can run a web server that has a rest API that you make. Then write the web/desktop clients to interface with that. But it entirely depends on your situation and I recommend researching more generally the ideal workflow.
@internetstyle commented on GitHub (Aug 8, 2018):
Thank you very much.