Opera Dragonfly vs Firebug

Question

I am an Opera user for browsing and a Firefox user for development. I just can't work without Firebug, and any other tools are not suitable for me. Geeks from Opera often suggest using Dragonfly , whose purpose is almost the same as Firebug (JS debugger, DOM / CSS inspector, JS console, page load analysis, etc.). I tried Dragonfly but returned to Firebug for the following reasons:

• Firebug loads faster than Dragonfly (for example, when checking an item);
• Dragonfly does not (or I did not find) how to quickly disable some css property. On FB, you just need to click the icon next to the prop. He already has it.

I wonder if anyone uses Dragonfly instead of ob FB or any other tool? Why not)? What are the main differences between the two tools?

Answer 1

you may or may not know that Opera Dragonfly is a kind of web application, downloading from the Opera server on first use and whenever it is updated. If you reopen it and the server version is not updated, it should load quickly from the cache. I'm not sure it's always the case, YMMV, and I can fully understand that its unpredictable download times can be annoying. However, this way you always use the latest version of Dragonfly without updating any extension.

Which brings me to the second point: disabling CSS properties. This is currently supported in a fairly obvious way in the latest version. I suggest you just try opening Dragonfly again: -D

As for comparisons, I'm inherently too biased to comment on this question ... But anyway: My general feeling is that Firebug was a giant leap in the design of the web debugger interface (if you're old enough to use Venkman you know what I mean), however under the hood it does not seem to be stable in use. My use case is basically a JS debugger (the DOM inspector has always been more reliable), and I saw how the debugger felt bad over the years. I’ll quickly add that Dragonfly isn’t much better, it found problems that could completely throw you away from the track when you step. The current version of Firebug may be more stable than all previous versions, but I'm still a little reluctant to use it for complex JS debugging tasks and prefer Dragonfly or Chrome inspector. Ymmv again.

.. The main reason I prefer Dragonfly is probably because this JS user allows me to use Dragonfly to go through ANY random script, regardless of whether it was sent over the wire as text without spaces: http: // my .opera.com / hallvors / blog / 2008/05/13 / script-formatter-user-js

But then my precedent debugs ANY random page, while most people use the case - debug their own well-formatted scripts :)

Answer 2

I use the development tools of all browsers! Even for Internet Explorer there are additional downloads for developers!

The problem is that this is not so, because one thing works in firefox, it works in IE6,7,8, Opera and Chrome.

What I like about internet exlporer is that you can choose which version you are debugging. Therefore, you do not need to download the collection (because 6 and 7 are almost the same)

All tools have almost the same functions.

Answer 3

Well, I would say that dragonfly is much better than firebug. It provides all the tools that are present in Firebug, but you just need to understand this. There is CSS autocomplete. But for this you need to press down key for and adding css is very simple. Just scroll down to the bottom of the css panel and write new style . And the dragonfly also provides Line no for styles. In the upper right corner of the style ad.

Answer 4

Agree with this, I spend 90% of my time for something to work, i.e. and being able to render in ie7 or 8 using developer tools is a big bonus.

When it comes to ie6, I try to run it through spoon.net, and then use the firebug lite shortcut shortcut for hacking, however these days you will already have a general idea of ​​what will and will not work before you start.

... Unfortunately, while working in the field of finance, many of your users will be obsessed with ie6 for a considerable time, so you just need to go with it.

I personally try to debug other debuggers if they are better than firebug, but so far they are fine, but with the transition to the Google Chrome web kit browser I already got my vote.

Answer 5

 CSS editing capabilities Firebug | Dragonfly _______________________ CSS autocomplete Yes | No Ease in adding new css Very easy | Very difficult Line no of styles Yes | No Page rendering while inspect Normal | Inspected element get locked Ruler Useless | Very handy (on the screenshot) Color pallete No | Yes Tabbed resource browsing No | Yes Extendability via plugins Yes | No