Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Browser support (Chrome App) #1653

Closed
brandonkal opened this issue Nov 8, 2019 · 3 comments
Closed

Browser support (Chrome App) #1653

brandonkal opened this issue Nov 8, 2019 · 3 comments
Labels
🦊 resolved/wontfix This will not be worked on

Comments

@brandonkal
Copy link

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

@fxha
Copy link
Contributor

fxha commented Nov 8, 2019

@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.

@fxha fxha closed this as completed Nov 8, 2019
@fxha fxha added the 🦊 resolved/wontfix This will not be worked on label Nov 8, 2019
@brandonkal
Copy link
Author

Thank you for the context on muya.

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?

@Jocs
Copy link
Member

Jocs commented Nov 8, 2019

but there is no plan to build or support a web client. Is that correct?

Currently we don't have a plan to develop a web version, and we hope that other contributors/developers can use muya to develop a web version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🦊 resolved/wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants