SubscribeRSS Feed

Below are some quick notes from today’s chat with the Opera developers working on the developer tool.

On a side note, a new version of the developer tools was released today on the Opera developer site.

  • The Opera developer tools will eventually be placed in a panel.
  • The current developer console was created to get out the tools that Opera developers were using in-house to Opera users. Opera did not plan for the current version to compete with Firebug.
  • Plan is to include the error console with the dev tools.
  • Ability for a debugger to step through code, set breakpoints and see variable values.
If you enjoyed this post, then make sure you subscribe to my RSS Feed.




4 Comments

  1. 1 Ben Buchanan

    I wouldn’t have said it should compete with Firebug, so much as it has to catch up with the FF web developer’s toolbar. Whether the dev team like or not, that’s what they’re competing with. Anecdotally, I’ve had trouble convincing web developers to build with and for Opera since they felt it lacked the tools available in FF. Opera has tons of features built in but they’re not packaged up as neatly as the FF toolbar.

    eg. reload from cache – buried in a sub-sub-menu… if you use it, you use it LOTS. I created my own button to make it faster but most people aren’t that motivated yet :)

  2. 2 ResearchWizard

    I think following announcement after the end of the chat seems to be quite a bit interesting:

    And next week I have an extra special treat for you.
    To mark the 1001st Opera widget, we will be joined by none other than Jon von Tetzchner to talk about, well, whatever you want to ask him.

  3. 3 ResearchWizard

    It looks like cite=”thomfo” didn’t work. To make it clear: the previous cite was from thomfo aka (also known as) Thomas Ford

  4. 4 Daniel Goldman

    ResearchWizard, I saw that — but that has nothing to do with the developer tools. :)

    I’ll definitely blog about it next week, as we get closer to the chat date.