Also, checkout https://github.com/CrabDude/lookingglass/blob/master/GettingStarted.mdwhere I've copied Pavel's high-level overview of what's involved. Essentially, node will be a lot like debugging a remote webworker, so I guess that obviates the UI issues.
On Wed, Jul 10, 2013 at 8:33 AM, Adam Crabtree <[email protected]> wrote: > First, I'm definitely not interested in duplicating any work. As a > software engineer, my goal has always been to write as little code as > possible to achieve my goals. > > Second, with regards to node-inspector... > > It's my understanding that node-inspector, and it's step-brother > node-webkit-agent[1] both consume V8's D8 debugging protocol, and that > there are intrinsic limitations to using D8. I have a little experience > with this while at Palm / HP webOS when I got node-inspector working > against the Touchpad, and we suffered the same problems of D8's feature > subset. Either way, should definitely talk to the guys at Strongloop (who > are awesome for taking over node-inspector) and Camilo Aguilar (c4milo) > who's been working with the Chrome Devtools guys and maintains the only > active equivalent. > > That being said, if I understand the scope of the problem correctly, my > goal is fundamentally different (and from what I understand still > possible). Over time, both Danny Coates and Camilo Aguilar have admitted to > struggling to keep their projects up to date with the latest devtools code. > Ideally, I won't even need to touch the devtools code. > > Chrome already supports remote Chrome debugging[2], and my (hopefully > achievable) goal is to implement this protocol in a node.js addon so that > debugging a node process would be indistinguishable from debugging a remote > Chrome process. Obviously there's no DOM, no Blink, no UI, which may cause > complications, but I guess I'll find that out along the way. > > Any additional insight or input into any of this is appreciated. > > Cheers, > Adam Crabtree > > > [1] https://github.com/c4milo/node-webkit-agent > [2] > https://developers.google.com/chrome-developer-tools/docs/debugger-protocol > > > On Wed, Jul 10, 2013 at 2:52 AM, Ben Noordhuis <[email protected]> wrote: > >> On Wed, Jul 10, 2013 at 10:01 AM, Floby <[email protected]> wrote: >> > I was gonna answer that https://github.com/dannycoates/node-inspector >> > already existed, but it hasn't been updated in 2 years. >> >> See [1], we've taken over maintenance. We'll probably update Danny's >> repo soon. >> >> [1] https://github.com/strongloop/node-inspector >> >> -- >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> You received this message because you are subscribed to the Google >> Groups "nodejs" group. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "nodejs" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > -- > Better a little with righteousness > than much gain with injustice. > Proverbs 16:8 > -- Better a little with righteousness than much gain with injustice. Proverbs 16:8 -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
