Orion/Chrome Tools Integration
- Student: Zachariah Moreno
- Mentors: John Arthorne, Ken Walker, & John Barton
My goal for this year’s GSoC is to write a Chrome extension that implements Orion as part of the current DevTools, with the extended goal of landing this functionality within Chrome. A Chrome implementation would give Orion a platform for exposing its functionality to developers everywhere. Allowing for designers and developers to view their changes in real-time, a cornerstone that I believe is missing from the current development process. Applications like Adobe Dreamweaver try to augment this issue by implementing a WebKit view into their native environment. But, I believe this to be the wrong way to go about solving this issue. We design and develop for the browser so we should complete that process by designing and developing in the browser.
This section contains tasks which are under development now and in the nearest future.
|Status||Milestone||Description||Due Date||Bugs / Reviews|
|M1||Community Bounding, technical discussion||May 21st|
|M2||Chrome DevTools extension - empty||May 21st|
|Students begin coding||official GSoC milestone, see ||May 21st|
|M3||Embed Orion Client in extension||June 1st|
|M4||Use chrome.devtools.inspectedWindow.getResources API to pull in client side code||June 29th|
|M5||Integrate Save functionality||July 11th|
|Midterm evaluations||official GSoC milestone, see ||July 13th|
|pencils down date||official GSoC milestone, see ||August 13th|