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
Given that this this is already a browser app bundled with chromium, I would like to the possibility to use the editor directly in the browser. This would also be useful for ChomeOS.
What problem does this feature solve? [optional]
This could be entirely client side with filesystem operations performed by calling an http endpoint that can easily be hosted on localhost or on a remote system.
@brandonkal Thanks for your request but this is currently out of scope of the project. Please see #772 for more information. If you need a standalone version you could try Muya, the core of Mark Text. Muya is currently developed in this repository and not in the linked one.
This could be entirely client side with filesystem operations performed by calling an http endpoint that can easily be hosted on localhost or on a remote system.
Yep, your are right but we also use Electron and Node.js functions in renderer process because it's not planned to support web. There are no benefits from spending much time refactoring Mark Text to support it.
What I gather is that the intent is to make some core functions (rendering excluded) accessible to other projects but there is no plan to build or support a web client. Is that correct?
Describe your feature request
Given that this this is already a browser app bundled with chromium, I would like to the possibility to use the editor directly in the browser. This would also be useful for ChomeOS.
What problem does this feature solve? [optional]
This could be entirely client side with filesystem operations performed by calling an http endpoint that can easily be hosted on localhost or on a remote system.
Additional context [optional]
code-server
The text was updated successfully, but these errors were encountered: