DevTools/Features/GCLI: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "= 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. Th...")
 
No edit summary
Line 11: Line 11:
# select elements via CSS selectors and then pass that to object inspector or DOM inspector etc.
# 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?
# output area with full UIs for things like inspection?
= Next Steps =
# Expand unit tests
# breaking changes:
  # rename text to string
  # rename bool to boolean
  # rename Type to Converter
# Embed in Ace again with find and replace and goto line, and prototype git
# Begin embedding in WebConsole
# Complete ArrayArgument
Features
--------
- add grouped parameters
- add JS parser
- allow use without input element
- add menu hierarchy
- add typing to return values
- add history retention
- add URIs for reference to everything
- define environment
- define prefs with:
  - scoping for projects, filetypes, etc
  - hiding for internal things, page owner things
- embed help as commands
- incorporate buggerall
- allow publishing of commands in pages (microdata?)
Bugs
----
- 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

Revision as of 13:15, 14 March 2011

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

  1. can we build command metadata for functions like alert from IDL?
  2. select elements via CSS selectors and then pass that to object inspector or DOM inspector etc.
  3. output area with full UIs for things like inspection?


Next Steps

  1. Expand unit tests
  2. breaking changes:
 # rename text to string
 # rename bool to boolean
 # rename Type to Converter
  1. Embed in Ace again with find and replace and goto line, and prototype git
  2. Begin embedding in WebConsole
  3. Complete ArrayArgument


Features


- add grouped parameters - add JS parser - allow use without input element - add menu hierarchy - add typing to return values - add history retention - add URIs for reference to everything - define environment - define prefs with:

 - scoping for projects, filetypes, etc
 - hiding for internal things, page owner things

- embed help as commands

- incorporate buggerall - allow publishing of commands in pages (microdata?)


Bugs


- 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