opera dragonfly doesn't work etc on the current file if you switch tabs

[jmichae3]

start opera.
open several web pages.
start dragonfly with ctrl-shift-i.
click on a different tab.

actual result:

• the file(s) you were looking at with the previous page in the debugger is still open in the debugger.
• the debugger does not close and make a new closed instance for a tab that didn't have it open

expected:

• the debugger should create a new instance the first time you make a tab and open dragonfly on /that tab/.
• when you switch tabs, the context for that tab should be different than for another tab. in other words, each tab should have its own debugging context.
• each debugger context should have its own state of debugger open/closed.
• each debugger context is what you think a context should be, page js variables, html, css, errors, and such like things you would expect from that tab.

[chriskr]

Dragonfly is not actively developed anymore, sorry.

[deepak1556]

@chriskr i just started using opera and got a great liking towards dragonfly's organised architecture but after using devtools for so long i find a lot of scope for improvement and features in dragonfly. Are PR's still welcome ?

[chriskr]

Hi @deepak1556, we have in mind to work on Dragonfly 2, so it would be interesting to know which features you miss from devtools.

[deepak1556]

That's great!
Features :

• Profile tab - Need a css profiler and a heap snapshot profiler
• timeline tab - i use this a lot to debug memory leaks
• Able to write and save JS snippets
• Settings tab - fps meter, paint rectangles, source maps and disable a specific framework
• Networks tab - able to export the waterfall for later use
• Console tab - autocomplete and suggestions
• debugging workers

Also i use backbone debugger, angular-batarang devtools extensions for debuggind my projects. But one annoying thing about devtools extensions is that they always get loaded on every new instance even when i dont need them, this has slowed my devtools a lot lately. But we could have an option in drangonfly to enable dragonfly extensions.

these are the ones i use a lot while debugging. Is there any tracker for dragonfly 2.0, i would love to help in its development ?

[chriskr]

Thanks! No, we haven't really started yet with Dragonfly 2.

[jmichae3]

I think someone just tried to cancel my bug report?
I have lots of RAM, have lots of tabs, and need the context. the debugger currently throws 1000-1200 error messages on average for 1 web page that is cross-browser because 99% of them are css errors that opera doesn't like because they are not o-specific.

I don't want to be a human filter. I think there was probably 1 or two error messages in that stuff I wanted, and I could not find them. so I used the built-in debugger on ff after giving up.

all the error messages are jammed together and you get a search box. I have no clue what the error message would be that I am searching for from js!
there's nothing that says javascript: or anything like that I can categorize on.
I even get browser internal js/css/whatever error messages. a checkbox for those would be nice. and some sort of error message categorization (html, css, js, etc) would help immensely.
(of course, that could be handy for debugging the browser)

as far as debugger contexts goes (the reason for this bug report), I still think that would be the best thing. for example:
if I am on web mail, I don't want its mounds of error messages throwing at me and making unnecessary noise, which it does with a single-context-only debugger (what we have now). those same error messages get thrown into my debugging of my project web pages. I don't have any choice. I can't turn those noisy ones off, except to zap the tab. what have I got? I have all the error messages from all the tabs in one listbox. not good. I would prefer to keep them SEPARATE. it also helps me to know where they are coming from too! I am not just running blind with a bunch of noise. with 60 tabs, this becomes necessary. and now with 4K monitors & video cards on the scene (asus), we will probably have even more tabs... and more memory usage. (this is why I am pushing for 64-bit browsers too). I already have problems loading the w3c html5 single-page spec in 32-bit browsers due to memory limitations (the OS and video card uses a fair chunk of that 4GiB so essentially you get 1.6GB-1.8GB max).

this is some of my reasoning for this bug report. I would definitely like some enhancements in this direction from the new debugger (multiple contexts) for the above reasons.

[jmichae3]

I do like the new feature list... :-))

[deepak1556]

Oops sorry @jmichae3, just wanted to clear my doubt with christian on dragonfly's devlopment. One thing tat keeps dragonfly unique from devtools is the error log, which is a built-into the console of devtools but that is annoying.

• a filter for error log
• new context for each tab
  are must add features for dragonfly 2.0