Skip navigation.

Log in | Sign up

Opera Dragonfly

Bug control, accelerated

Opera Dragonfly alpha 2 out now

By dstorey. Tuesday, 1. July 2008, 14:21:22

, ,

Following the Release Candidate last week, Opera Dragonfly alpha 2 has now gone live. People using the default URL for Opera Dragonfly will automatically upgraded to this new version. As always, you can access Opera Dragonfly alpha 2 by clicking on Tools -> Advanced -> Developer Tools in Opera 9.5’s menu bar.

Along with the new features, such as CSS editing, that were introduced in the last post on this blog, we've also released schemas and JSDocs for the code structure and source code. This should make it easier for developers to pick up the source code and start playing with it. I'd be interested to see what people can come up with to improve Opera Dragonfly. If you have any questions about the code, want to post some adaptions or give feature requests then head over to our forums.

The next step is to work on the bugs and planned features for alpha 3 in a few months time.

Opera Dragonfly alpha 2 RCThe latest weekly, now with more lingo

Comments

shadowk 1. July 2008, 14:59

great :d how can i post from JS directly to the console?

you know something like opera.postError, but instead of showing up in the error console i would like it to show up in the command line so if it's an object i can click on it and so on...

hallvors 1. July 2008, 15:27

aleto: he meant from the script itself, not from the console :smile:
shadowk: we plan to support console.log and friends :wink: Not sure when we get them though.

aleto 1. July 2008, 15:30

aleto: he meant from the script itself, not from the console


I have understood immediately after i have posted my response :smile: and then deleted it.

It is actually a very valid feature request.

dstorey 1. July 2008, 15:43

Firebug Console API requires Scope support, so will be with the next Core version at the earliest. Would we need errors to go to the command line if we get the Firebug Console API and objects are clickable in the Error Console, instead of just the Command Line?

aleto 1. July 2008, 15:55

Yes, i actually don't think only the console api would give us the feature which shadowk is asking for, we would need a bit more.

shadowk, one thing which we haven't publish so far ( if i'm not mistaken ) is the "debugger" keyword, that's like a hard coded breakpoint in the source file. That does at least stop the code at that point and would let you inspect with the tab completion quite quickly your target object.

Khadgar 2. July 2008, 04:01

I am unable to use Dragonfly on any My Opera page. Is this known or should I file a bug report?

d.i.z. 3. July 2008, 18:59

I am unable to use Dragonfly on any My Opera page. Is this known or should I file a bug report?


What is wrong? I can use it on this page for example.

Khadgar 3. July 2008, 20:07

I'm unsure at the moment to be honest. It doesn't work is what's going on, but it seems to be isolated to my particular computer. I've tested it on several and neither has the same problem. Dumping preferences doesn't solve the problem either.

Edit: Dragonfly gives an error in the error console upon loading a My Opera page on my computer:

Unexpected end of file

Line 12:
  .sidelinx a:hover {background:#eee;}


Which is from My Opera, but then it shows nothing else. I get the error on other computers, but it allows me to select them.

Edit #2: Looks as if I've found the culprit. When I dumped my preferences looked like I missed my site preferences file. Something in it was keeping Dragonfly from working on my opera pages. Sorry to bug you guys about it.

fearphage 24. July 2008, 20:02

I recently had the need to dive into DF. I have been doing lots of backend work lately so hadn't needed it for this brief stint. I'm debugging our product in Opera and there are roadblocks that I simply and unable to cross. I have some javascript widgets that work fine in ff and safari but only partial in Opera. They are silently dying without errors some I'm having a really hard time debugging them in opera. Is there a way to make breakpoints remain through a refresh? This is the first time I've needed to use DF and sadly it is not helping as much as I had anticipated. :worried:

aleto 25. July 2008, 14:35

fearphage: breakpoints should still break after a reload, if not that would be a bug.

But you could also set them manually in the source code with the "debugger;" statement, if that is of any help.

fearphage 25. July 2008, 18:38

Thanks aleto. I was not aware of the debugger; statement. Also, another feature i'd like to see is that i can send live elements/data to the console in firebug. For instance:
console.log(document.getElementById('catpants'))
In the console, i will see a "live" representation of this element and i can click it, to navigate to it in the dom and see its childNodes and all that good stuff. Also, i would like the capability to have the debugger always on or to enable/disable on a per-site basis. Would be nice...

fearphage 13. August 2008, 19:17

Maybe it is situational to what I am debugging but I've set breakpoints many times and Opera/dragonfly just powers through them.

My latest annoyance is that opening dragonfly automatically reloads a (seemingly) random window. I know this is because dragonfly doesn't have an on/off switch... which I think is a very soar point right now (feature request). I want it on always and poised in the ready (maybe in time?). Until then, does anyone know how dragonfly selects that window that it will choose as active (...and then reloads)?

aleto 14. August 2008, 15:21

fearphage, do you have a tc which you can share with the non-working breakpoints? We are very much interested in such stuff.

There is a cookie with the last selected window ( the internal uid ) for the automatic selection. That should be most likely the last one which you have work with.

fearphage 15. August 2008, 12:58

Originally posted by aleto:

do you have a tc which you can share with the non-working breakpoints?

Well one I ran into issues with was debugging bug #
354901 (Regression: No comments on USA Today). There are two example links listed. I was trying to break in various functions in these files:
pork.iframe.js
requestbatch.js

Write a comment

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