Graphical Command Line Interface
Cockpit was created as part of the merger between Mozilla Skywriter and 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
- can we build command metadata for functions like alert from IDL?
- 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 14 March
- Begin embedding in WebConsole
- Make breaking changes to Pilot: s/text/string/g, s/bool/boolean/g, s/Type/Converter/g
- Embed in Ace again with find and replace and goto line, and prototype git
Week of 21 March
- Continue embedding in WebConsole
- bug 642231 Prepare GCLI for review
- bug 642226 allow use without input element
These bugs can be defined, and documented without being completed:
- bug 642189 support grouped parameters
- bug 642238 add typing to return values
Distant Future (beyond next week)
Major features that we are looking to work on, these are roughly sorted in order of importance.
- 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.
Bugs
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.
- bug 642400 define 'environment'
- 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