Skip navigation.

exploreopera

| Help

Sign up | Help

Web Applications Blog

avatar

Web Developer Chat: Opera's Web Developer Toolbar

, , , ,

As you may know from the Desktop team blog, we're planning to include the developer console in future Opera editions. Over on dev.opera, we released the tools separately: a DOM Console, CSS Editor and DOM Snapshot.

But before these tools go live in the browser, we need your feedback. What works well, what doesn't, what tools do you need to make your jobs easier? What we have now represent the first step, and far from our last, but we want to make sure we're doing our best to give you what you need.

So joining us this week is Christian Krebs, with whom you spoke last year, and Helmers. These are the two masterminds behind the tools. Swing on by this Thursday at 5:00 PM CET (check the local time where you live) over on our usual channel: #webapps.

See you there!

Web Developer Chat: Fredrik AnderssonWeb Developer Chat: Jon von Tetzchner

Comments

avatar
Well, the obvious reference is Firebug for Firefox, definitely the best developer tool out there at the moment!
If you could mimic it, that would be the top! :smile:

I like and use the Opera DOM Console. It's nice and decent. Does its job. A disturbing thing is that it's impossible to "panelize" (at least I'm not able to). I don't like the floating window it appears in. Being able to get it on the Panel toolbar would be better, IMO.

The CSS Editor is a bit minimal, compared to what Firebug offers. But it can be useful to try fixes on the fly.

What Opera really lacks at the moment, especially for the trendy AJAX applications out there (and I'm an AJAX developer), is a serious Javascript debugging console. Even that awful and osbsolete Microsoft script debugger (for NT 4.0!!!) is much better then anything Opera has at the moment! You can get actual variables values, even if from a command line style console, assign values and try to understand why the hell something works on other browsers but not IE. Doing the same in Opera is basically impossibile.
A JS debugger with watches and step by step execution is the most needed Opera extension, for my needs, at the moment!

By upanisad, # 20. February 2007, 15:16:27

avatar
This seems like a waste of effort. Wouldn't it make more sense to collaborate with Firebug team, help expose some of the internal Opera engine hooks to Firebug so we could do the same thing in Opera with same codebase?

By ddrum, # 20. February 2007, 16:29:22

avatar
also note:
A combined DOM tree/DOM console, JS Viewer, CSS Editor, HTTP Header/Cookie viewer, and "XHR Logger:"(whatever that is) is available in the Latest Opera weekly build in Tools -> Advanced -> Devloper Console.

@upanisad: Allthough the JS viewer isnt as great as what you'd like, It does allow you to view what global variables(At least, i'd only glanced at it) are set to..

I've just taken a look at Firebug, I'd love to be able to do the JS part in Opera, Breakpoints and watch.. Hopefulyl opera can get that implemented..

@ddrum: Firebug looks nice, but honestly, I dont see it being able to be supported by Opera that easily, it uses many hooks into the core of Mozilla, allthough Opera could implement that the same way, i've got a feeling they've got other methods in the core, for the Firebug developers it'd take a bit to get their code to seemingly interact with 2 completely different API's, and then you'd have the problem of One set of developers claiming somethign should be done one way, and the other claiming differnetly etc..


What i'd like see done with JS though, Is some form of write up for this:
opera:config#Extensions|RemoteScriptDebugger
I cant find any applications that support it, and from memory, having something listening on the port and having Opera set to log it, nothing happened..

D

By DD32, # 20. February 2007, 23:19:13

avatar
I wanted to write a post about web developer tools and maybe I'll manage to do it some day. So let me just name some key points on this place (I'll not be available for the webchat):

I'd use Opera's already available power to have an easy possibility to test the pages. For final test there should be one button opening test scenarios with the page in question in multiple tabs in a seperate window:
  • different sized browser windows (from SSR mimicing PDA view up to very high resolution zoomed down to fit in the development environment), one
  • without JS, without images, without plugins, without CSS
  • in the different media-types (esp. print) or with available alternative style sheets
  • in several online validatiors and maybe in tidy
  • maybe in different color modes (using UserJS or UserCSS)
  • additionally open in IE + FF and / or any other available browser

The page title could tell what the single page is about. A summary page could link to the local test pages (although not necessary) and maybe give a automatic result for single tests (I'd think that's only reasonable with the validation pages).
Although the developer needs different tools for debugging, this would be very usefull, esp. for an easy final test just looking to (and maybe playing around with) the opened tabs and close one after another. The outstanding advantages: easy to use, guiding to standard design working on any device and any browser, unique and it ensures that it works in Opera. Further features (probably not possible yet) could be refresh/reload of all pages after editing HTML or CSS (similar as developer console does for one page) and saving screenshots of all pages for documentation (thinking of having an easy to define requirement for the page developers - the page has to pass the Opera check :smile: ).

Another thing which is not equally easy to implement: Provide homepage owners with a possibility to edit text of an online page. This should be possible by dynamically adding RTE-features into the DOM tree but it would need some authentification on the server, probably ftp (which I don't have on my roadmap prediction). Maybe it is possible to transfer the page to my.opera.com, edit it there and retransfer it afterwards. Editing could be limited by a seperate CSS definition like body content { Opera-edit: editable; Opera-addchilds: p h2 h3 quote div.special; } etc. - there could be a list box like the font-selection in an online WYSIWYG editor. This would make it possible for the designer to set up the design and framework and afterwards the user who is not capable of edition HTML or even use a mighty webdev-tool (or not willing to pay for it) to change the content without help just like adding content in a Wordpress blog.

I think that was the most important I thought of. I think it could be quite promising to have unique features.

By ResearchWizard, # 21. February 2007, 04:01:30

avatar

By remcolanting, # 22. February 2007, 17:24:29

avatar
Thanks remco (and grafio).

By hzr, # 23. February 2007, 00:32:53

avatar
The only reason I haven't uninstalled FF yet is because I sometimes need to use the Firebug extension. Besides, something like the Web Developer Toolbar add-on for Firefox would be fine.

By kaixi, # 1. November 2007, 17:50:03

avatar
Hi,
I am new to Mysql and PhP. I am having an error while adding,editing,delete or search the specif filed,error is:

Failed to connect to database at localhost:3306. Error: Access denied for user 'root'@'localhost' (using password: YES)

Please help me,
regards,

Tani.

By tani2008, # 11. January 2008, 12:22:01

Write a comment

You must be logged in to write a comment. if you're not a registered member, please sign up.