Opera Developer Console

Category: Opera , Utility

Shawn Lauriat has posted on the new Opera Developer Console.

The tool is written in JavaScript and is an interesting little read.

The tool covers:

DOM: The DOM tool lets the user inspect and alter various various aspects of the document.
JS: The JavaScript tool lets the user to inspect and search the JavaScript enviroment initialized on the web page.
CSS: The CSS tool lets the user inspect and alter any Cascading Style Sheets attached to the page. Further, the tools allow the altered stylesheets to be exported for later use.
HTTP: The HTTP tool allows user to inspect the HTTP headers sent from the server, inspect and edit cookies, and allows logging of XMLHttpRequests sent by the document.

Posted by Dion Almaer at 12:01 am
9 Comments

3.6 rating from 28 votes

9 Comments »

Comments feed TrackBack URI

great – can’t wait to try this out when theres a 64bit linux version of opera..since its damn near impossible to get firebug working on minefield without errors, not to mention firefox uses so much RAM that theres no room left for emacs when developing..

Comment by carmen — March 13, 2007

all they need is a syntax highlighting JS editor, and inline doc lookup, and we can ditch our SLIME for good

Comment by carmen — March 13, 2007

So, is this better than firebug? Different?

A ‘firebug’ knockoff for opera would be great; there’s plenty of times something works in firefox but crashes on other browsers. Now if only there was something like firebug for IE and safari as well, we’d be all set :-P

Comment by Reinier Zwitserloot — March 13, 2007

Actually in VS 2005 there is Script Explorer which can easily debug JavaScript under IE.

Here is more:
http://ajaxus.net/2007/03/debugging-javascript-using-vsnet-2005.html

Comment by ajaxus — March 13, 2007

There’s a firebug knockoff for IE:
http://www.ieinspector.com/dominspector/index.html

Ofcourse, it is not free.

Comment by Joeri — March 13, 2007

Microsoft provides a homegrown dev bar for IE, which is free.

Comment by Matthias — March 13, 2007

Reiner: different. They’ve made a point of saying that they have no intention to directly compete with Firebug, and it looks like the tool will work quite differently by the time it starts really taking shape.

Even if they made a Firebug clone, I’d have both installed. Not like I only keep one browser around for development and testing, anyway.

Comment by Shawn Lauriat — March 13, 2007

There’s also a firebug knock off in the Mootools library (found in the “Misc” folder in the trunk at dev.mootools.net; yeah, it could be better publicized). You can see it in action on my wikitorial for Mootools:

http://clientside.cnet.com/wiki/

Comment by Aaron Newton — March 13, 2007