Jump to: navigation, search

Difference between revisions of "Orion/Chrome Tools Integration"

(New page: <ul> <li>Student: Zachariah Moreno</li> <li>Mentors: John Arthourne, Ken Walker, & John Barton</li> </ul>)
 
Line 1: Line 1:
<ul>
+
*Student: Zachariah Moreno
<li>Student: Zachariah Moreno</li>
+
 
<li>Mentors: John Arthourne, Ken Walker, & John Barton</li>
+
*Mentors: John Arthorne, Ken Walker, & John Barton
</ul>
+
 
 +
This project is part of the [http://wiki.eclipse.org/Google_Summer_of_Code_2012 Google Summer of Code 2012]
 +
 
 +
<br>  
 +
 
 +
== Goal  ==
 +
 
 +
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.
 +
 
 +
<br>  
 +
 
 +
== General plan  ==
 +
 
 +
<br>
 +
 
 +
== Progress  ==
 +
 
 +
This section contains tasks which are under development now and in the nearest future.
 +
 
 +
 
 +
<br>
 +
 
 +
== Completed tasks  ==
 +
 
 +
Section contains all the task which are completed, tested and positively reviewed.

Revision as of 18:28, 29 May 2012

  • Student: Zachariah Moreno
  • Mentors: John Arthorne, Ken Walker, & John Barton

This project is part of the Google Summer of Code 2012


Goal

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.


General plan


Progress

This section contains tasks which are under development now and in the nearest future.



Completed tasks

Section contains all the task which are completed, tested and positively reviewed.