Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [orion-dev] Implementing a runtime debugger for Orion as a GSoC Project
It's been a few days, so I want to follow up though I cannot show anything solid yet.

>In particular improving our integration with Chrome's debugger would be really useful for both browser and node.

An improved integration with Chrome sounds to me like a good contribution in general but not like a GSoC project, am I wrong?

My implementation builds upon the debug bundle. The communication with Chrome's API happens via a modified [debug.js] contentscript and an extended [debugMessaging.js]. I had to make some changes to make it work more stable and with multiple orion endpoints from the same tab, but apart from that, the basic ideas were the same as in the original debug bundle.
I only implemented the _javascript_ part of the Chrome debugger protocol [1], since that was my focus.
I also implemented a connector for the Rhino debugger, which was based on a WebSocket connection.

It seems to me, that currently there just is not much interest in a debugger plugin and I should try to contribute in my spare time.

-Leo

[1] https://developers.google.com/chrome-developer-tools/docs/protocol/1.0/debugger
[debug.js] https://github.com/eclipse/orion.client/blob/b40de370c816554c8da6376176a91e5a4ea6abfd/bundles/org.eclipse.orion.client.debug/chromeExtension/debug.js
[debugMessaging.js] https://github.com/eclipse/orion.client/blob/b40de370c816554c8da6376176a91e5a4ea6abfd/bundles/org.eclipse.orion.client.debug/web/debugMessaging.js


2013/2/25 Leo R <leor.email@xxxxxxxxx>
Hi Simon,

I'll probably need a few days to get the permissions. I did my thesis at a company so it's bound by an (obligatory) non disclosure agreement, that's why I wanted to know whether there is any interest first. 

Until I have the permissions I can, as Marcel suggested on soc-dev [1], at least link to some sources to show some identification and that I have been working on that project. I have uploaded the changes to RingoJS that I made to make it remote debuggable to github [2]. [3] shows the related RingoJS Google group discussion. 
I also asked some questions in the forum [4,5].
I started a blog where I describe my bigger vision and which I would use to document my progress of the project [6].

Regards,
Leo



2013/2/25 Simon Kaegi <Simon_Kaegi@xxxxxxxxxx>

Sounds interesting.
In particular improving our integration with Chrome's debugger would be really useful for both browser and node.
 Do you have any pointers to your work or maybe a paper etc?
-Simon

Inactive hide details for Leo R ---02/24/2013 07:12:39 PM---Hi. I am Leo Roos. I would like to contribute to Eclipse Orion for Leo R ---02/24/2013 07:12:39 PM---Hi. I am Leo Roos. I would like to contribute to Eclipse Orion for GSoC 2013.


    From:

Leo R <leor.email@xxxxxxxxx>

    To:

orion-dev@xxxxxxxxxxx,

    Date:

02/24/2013 07:12 PM

    Subject:

[orion-dev] Implementing a runtime debugger for Orion as a GSoC Project

    Sent by:

orion-dev-bounces@xxxxxxxxxxx



Hi.

I am Leo Roos. I would like to contribute to Eclipse Orion for GSoC 2013. My "idea" is to implement (/start working again on) a debugger-plugin for Orion.

Partially based on org.eclipse.orion.client.debug [1] I implemented a browser-based debugger that supports breakpoint setting/removal, stepping through code and state inspection. The debugger can connect to the chromeDevTools _javascript_ debugger and a Rhino debugger (more specifically RingoJS [2]). To visualize the code the debugger uses the embeddable Orion Editor.

The implementation was part of my my master's thesis and is not much more than a proof of concept (I am still a student because I have some exams left). It crashes frequently and the setup is complex. But I liked working on it, I gained experience with the different remote debugging protocols, the chrome extension mechanism and Orion. I would hate to see that wasted.

My Goal would be to at least support above mentioned functionalities plus a call stack visualization  The debugger should be able to connect to at least one client-side (Google Chrome) and one server-side technology (e.g. Rhino or Node.js).

Please let me know if this is of interest to you as a GSoC project.

Best Regards,
Leo

[1] which has been removed in 21b24b1022458184e1e710585f731d177e49915f Bug 386961 - remove dead/stale pages
[2] http://ringojs.org/_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev



_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev



GIF image

GIF image

Back to the top