Since LynxKite workspaces are now normal files, the directory browser is just a file browser. Surely there is prior art for that? I don't want to implement all file operations myself! (I couldn't even bring myself to implement renaming, to be honest.)
Some ideas discussed for this:
Find an open-source component that does it for us.
Make LynxKite a desktop app.
Make LynxKite a VS Code plugin.
Make LynxKite a Jupyter Lab plugin.
Make LynxKite a web application like https://photopea.com/ or https://excalidraw.com/. You can put a file in your browser, edit it there, and download/save it. It's never stored on the backend.
None of these are clear winners, especially if we split the editor (#1). In one use case we would prefer to work with local files. (E.g. maybe LynxKite graph analytics.) In another, the workspace is closely tied to a remote server. (E.g. if you are configuring a chatbot in production.)
Since LynxKite workspaces are now normal files, the directory browser is just a file browser. Surely there is prior art for that? I don't want to implement all file operations myself! (I couldn't even bring myself to implement renaming, to be honest.)
Some ideas discussed for this:
None of these are clear winners, especially if we split the editor (#1). In one use case we would prefer to work with local files. (E.g. maybe LynxKite graph analytics.) In another, the workspace is closely tied to a remote server. (E.g. if you are configuring a chatbot in production.)