A quick brain-dump of the commands I'd find particularly useful:
* resize width, height, viewport?
- Resize the browser window or viewport.
* cache on/off (for current page)
* reload (css)
- Purge all CSS resources, and reload them.
* screenshot (window|viewport)
- Grab a screenshot of the browser window (perhaps viewport as default)
* cookie foo/blah = blah
- Set cookie at foo/blah to blah
* cookie blah
- Retrieve value of cookie blah
* cookie blah !
- Erase cookie blah
* inject
http://foo.com/bar.js (element)
- Inject resource into the page -- handle JS and CSS appropriately. If
element specified, use that, otherwise put scripts at bottom of <body>,
and CSS at bottom of <head>.
* plugins on/off
- Enable or disable plugins (Flash, silverlight, etc.) for current page
* break foo.js#324
- Add a breakpoint in foo.js at line 324.
I'll probably think of more during the day. I've not expressed them as
commands per se -- the list is meant to indicate desired functionality
more than desired syntax.
- Barry
On 13/12/11 04:18, Kevin Dangoor wrote:
> Joe Walker has been building a great "modern command line" for developer
> tools. You can see it right now in Nightly by setting devtools.gcli.enable
> to true in about:config.
>
> When you do so, you'll see the Web Console's JavaScript command line change
> to a tool-oriented command line (which means: designed to be very quick to
> type). You can still run JavaScript by hitting { (curly brace)
>
> This has the potential to be an amazing feature... but it needs commands. I
> started a wiki page:
>
>
https://wiki.mozilla.org/DevTools/ThinkingInCommands
>
> I'm interested in hearing people's thoughts about the command line feature
> and the kinds of commands they'd like to see. Bugs with patches for
> commands would be cool, too :)
>
> Kevin
>
--
Barry van Oudtshoorn
www.barryvan.com.au
Not sent from my Apple πPhone.