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
Thus far the schematic editor runs on two internally-defined Platforms:
The dedicated Electron app
The VsCode extension
Given everything in the project uses web-stack technologies, the natural third is the web. This will in principal be very easy to stand up. There are two interesting questions/ groups-thereof (to my eye):
How to handle "platform interactions", e.g. opening from file.
The existing platforms have access to the editor's local filesystem; a web app will not.
Popular such apps would often get this content from GitHub, Google Drive, or its own database.
"Save" is probably a bit easier, and would presumably be more like "export and download". Nonetheless that also needs to be piped through the browser APIs.
Where to host and run it.
That's in some sense tied to (1), particularly if there is a native datastore of schematics.
The text was updated successfully, but these errors were encountered:
To fit the PlatformInterface - which is basically message-passing - this will also need some kinda bidirectional server-client communication channel. Socket.io seems a popular and relatively straightforward option.
Thus far the schematic editor runs on two internally-defined
Platform
s:Given everything in the project uses web-stack technologies, the natural third is the web. This will in principal be very easy to stand up. There are two interesting questions/ groups-thereof (to my eye):
The text was updated successfully, but these errors were encountered: