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
I might have a bunch of data loaded in my own web page, and I want to be able to "open in Foxglove", without having to upload that content to a file server.
Open a new window, use that reference to send data to foxglove with post. Could be quite efficient and quick to prototype, though might hit problems with ad blockers.
Open foxglove to connect a peer-to-peer datchannel to the source window, then the content could be streamed across (maybe reusing the ws-protocol).
This would require a signalling server etc, though it could open up a bunch of other use cases (being able to share your data to other people, or connecting to robots without having to expose http ports).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I might have a bunch of data loaded in my own web page, and I want to be able to "open in Foxglove", without having to upload that content to a file server.
Two ways I could imagine this working
1.
postMessage
to window / iframeOpen a new window, use that reference to send data to foxglove with post. Could be quite efficient and quick to prototype, though might hit problems with ad blockers.
2. WebRTC
Open foxglove to connect a peer-to-peer datchannel to the source window, then the content could be streamed across (maybe reusing the ws-protocol).
This would require a signalling server etc, though it could open up a bunch of other use cases (being able to share your data to other people, or connecting to robots without having to expose http ports).
Beta Was this translation helpful? Give feedback.
All reactions