Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Using in an Electron app #122

Open
rgbkrk opened this issue Jan 2, 2016 · 6 comments
Open

Using in an Electron app #122

rgbkrk opened this issue Jan 2, 2016 · 6 comments
Labels

Comments

@rgbkrk
Copy link

rgbkrk commented Jan 2, 2016

Is there any good way of using Atom's raw Editor in an Electron app?

@lee-dohm
Copy link
Contributor

lee-dohm commented Jan 2, 2016

Atom's editor component isn't designed to be used outside of Atom, even in Electron. I'm pretty sure this has been asked before, but I can't find a link to it.

/cc @nathansobo @as-cii

@rgbkrk
Copy link
Author

rgbkrk commented Jan 2, 2016

You know it was probably even me asking.

@nathansobo
Copy link
Contributor

It's not broken out purely as an accident of not having access to Node when it was started. There's no explicit opposition to extracting it and it should be easier now than ever to do it, but it's not at the top of my list yet.

@50Wliu
Copy link
Contributor

50Wliu commented Jan 2, 2016

I don't know how relevant this is, but the slap editor uses text-buffer (here). That being said it isn't an Electron app. /cc @dbkaplun

@mnquintana
Copy link
Contributor

AFAIK text-buffer is distinct from Atom's editor component – Atom's editor component depends on text-buffer for all its text manipulation operations, but the editor component is what's responsible for rendering and interaction.

@rgbkrk
Copy link
Author

rgbkrk commented Jan 2, 2016

You've done phenomenal work in making Atom's Editor super performant with solid APIs, which is why I ask. I apologize for opening this in the wrong repo, it dawned on me right after that it belongs in atom/atom.

I'm currently working on a formal Electron app for the Jupyter/IPython notebook. Our current codebase for the web based notebook uses CodeMirror.

jupyter notebook

For an Electron app built primarily with React, CodeMirror is a bit strange. The Atom APIs on the other hand are wonderful and certainly work well with the ecosystem of Jupyter Atom plugins - Hydrogen, atom-notebook. A lot of people just want a full application for the notebook - primarily researchers, analysts, etc. that are comfortable in the notebook interface over an editor. Forking atom for the sole purpose of a different skin would be absolutely ridiculous on my part.

For comparison, here's the Atom notebook:

atom notebook

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants