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

Think it's possible to communicate between atom <--> chrome instance? #42

Open
coopermaruyama opened this issue Jul 12, 2015 · 1 comment

Comments

@coopermaruyama
Copy link
Contributor

@PEM-- I just had an idea but I'm not sure how it would work or if it's possible so I wanted to run it past you.

So usually I launch meteor, then I open up a chrome browser to localhost to develop my app. I figured since atom is pretty much an instance of chrome it shouldn't be too hard to get them to communicate. If I can just read chrome's Javascript console's output from Atom somehow, or to integrate in a way where we can get set breakpoints in another running chrome instance from Atom, I can probably add a feature which would allow setting breakpoints by clicking on the line numbers of the file you're working on within atom, as well as showing highlighting within Atom on lines that had errors.

What do you think? I really have no idea what this would take, but I think it would be really useful.

@coopermaruyama coopermaruyama changed the title Think it's possible to read the console output? Think it's possible to communicate between atom <--> chrome instance? Jul 12, 2015
@PEM--
Copy link
Owner

PEM-- commented Aug 31, 2015

Didn't see this one... I'm lagging behind.

That would be awesome. NodeJS uses node-inspector for debugging. Remote debugging is allowed with it. Atom could act as a remote debugger when Meteor is launched in debug mode.

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

No branches or pull requests

2 participants