DevTools/Features/GCLI: Difference between revisions

Jump to navigation Jump to search

DevTools/Features/GCLI (view source)

Revision as of 14:25, 1 April 2011

413 bytes added ,  1 April 2011
no edit summary
No edit summary
Line 1: Line 1:
= Graphical Command Line Interface =  
{| class="fullwidth-table"
|-
| style="font-weight: bold; background: #DDD;" | Feature
| style="font-weight: bold; background: #DDD;" | Status
| style="font-weight: bold; background: #DDD;" | ETA
| style="font-weight: bold; background: #DDD;" | Owner
|-
<section begin="status" />
| [[DevTools/Features/GCLI]]
| {{StatusHealthy|status=Prototype implementation being integrated with Firefox.}}
| YYYY-MM-DD
| Kevin Dangoor
<section end="status" />
|-
|}


Cockpit was created as part of the merger between Mozilla Skywriter and
== Summary ==
Ajax.org's Ace. It provides a graphical command line interface. This
document describes our planned evolution of Cockpit as part of our
overall tools effort.


= Open Questions =
The Graphical Command Line Interface (GCLI), which you may see referred to as "Cockpit" at times, is intended as a way for users to quickly navigate and control the developer tools from the keyboard. The GCLI is designed to make the available commands easily discoverable and easy to correctly run with the right parameters. Unlike the JavaScript command lines provided by existing tools like the Web Console, the GCLI provides commands that are faster to type.


# can we build command metadata for functions like alert from IDL?
Ultimately, the GCLI is an attempt to provide easy keyboard control to a diverse and feature-rich set of tools. If you try to figure out how to control one of the traditional web developer tools with the keyboard, you'll see what the current approach lacks.
# select elements via CSS selectors and then pass that to object inspector or DOM inspector etc.
# output area with full UIs for things like inspection?


= Week of 21 March =
== Release Requirements ==


* {{bug|642505}} Continue embedding in WebConsole
* Firefox features and add-ons can register new commands to be available in the GCLI
* {{bug|642231}} Prepare GCLI for review
* Integrates with the Web Console for output
* {{bug|642226}} allow use without input element
* Electrolysis-ready


These bugs can be defined, and documented without being completed:
== Next Steps ==


* {{bug|642189}} support grouped parameters
* Contain scope for initial release
* {{bug|642238}} add typing to return values


= Distant Future (beyond next week) =
== Related Bugs & Dependencies ==


Major features that we are looking to work on, these are roughly sorted in order of importance.
See the [http://mozilla.github.com/devtools/2011/status.html#gcli status page] for bugs.


* {{bug|641903}} create a global command registry
== Team ==
* {{bug|642196}} allow JS to be entered using {}
* {{bug|642241}} experiment with better UI presentation methods
* {{bug|642239}} add history retention
* {{bug|642237}} add menu hierarchy
* {{bug|642240}} add URIs for reference to everything
* {{bug|642242}} embed help as commands


There is a meta bug ({{bug|642229}}) to bring these and other bugs together.
The GCLI is an experiment and it will take a little time to get the UX right. We want your help and feedback! Send email to dev-apps-firefox


= Bugs =
* Joe Walker: lead developer and feature designer
* Kevin Dangoor: PM


Other bugs for us to work on. These should really be discovered using some sort of search, keeping this list up to date could be a drag. Maybe we should raise a bug for that.
== Designs ==


* {{bug|642400}} define 'environment'
TBD
* {{bug|642401}} allow preferences to have custom scopes
* ensure canon.addCommands does as the docs say it should
* Requisition._onAssignmentChange:~559 shouldn't fire events when bumping posn
* give all arguments some position and a fill-with-default system


= Old Tasks =
== Goals/Use Cases ==


Week of 14 March
A Web Console user should be able to change filters or clear the console entirely with the keyboard.


* Array arguments
Someone who wants to compare the styles of a set of page elements should be able to run a command to select some elements and then another command to open the Style Inspector, all without reaching for the mouse.
* Embed in Ace again with find and replace and goto line
 
* Update type names in Pilot
== Non-Goals ==
 
For this project, we're not looking to replace the Web Console's JavaScript command line with the GCLI. After we are comfortable with the UX, we will revisit that.
 
__NOTOC__
 
[[Category:Feature]]
[[Category:Firefox]]
[[Category:DevTools]]
[[Category:Priority 1]]
Kdangoor
canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,093

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/295950"

Navigation menu