My Opera
New fast release cycle and a fresh experimental build
By David Håsätherhzr. Wednesday, September 21, 2011 2:31:03 PM
With the big launch of Opera Dragonfly 1.1 out of the way, we’ve decided it’s time to make some changes to our release cycle. From now on releases will be more focused on improvements to individual components, e.g. the DOM inspector or the UI framework. As soon as a feature for a certain component has been implemented, it will be put on the experimental path for some initial testing.
https://dragonfly.opera.com/app/experimental/It will then be released on the cutting-edge path as a release candidate, where it can be tested by more users.
https://dragonfly.opera.com/app/cutting-edge/If no issues are found, this will then be released as a new version on the default path.
In short, this will result in a faster release cycle, where new and improved features will be available to users much quicker than before.
To switch to the experimental or cutting-edge builds, paste the URL into opera:config#DeveloperTools|DeveloperToolsURL, click the Save button, and (re-)open Opera Dragonfly.
As part of this new release strategy, we’re also switching over Opera Dragonfly to a new version scheme:
<major-version>.<year>.<month>.<date>.<today’s-build>For example, a version number of 1.2011.11.21.2 will indicate major version 1, released 2011-11-21. It’s also the second build released on that day.
To kick things off, we also have a new experimental release today. The focus has been on improving the UI framework. The dimension of panels will now be stored, and will be better preserved when resizing the application. Resizing performance in the scripts view has also been improved. And we’ve made some tweaks to overall text selection – for example, it’s not possible to accidentally select the text of tabs and various other UI elements anymore.
We’ve also fixed an issue where Opera Dragonfly wouldn’t start in Opera 12 pre-alpha (Opera Next to its friends), as well as some other minor bugs. Lastly, we’ve added Ctrl-R and ⌘-R as a handy shortcut for reloading the debug context.
See the full changelog for further details.
Big thanks to Rafał Chłodnicki (Opera employee, but not on the Opera Dragonfly team) for fixing some of his pet bugs in this release. 
timmi # Wednesday, September 21, 2011 5:34:19 PM
There is one thing that bothers me a lot when debugging an extension. When I'm at the "Scripts" view and change the debugging context between injected script and background script, I must everytime reload the scripts for showing it to me.
Also it seams console.log is not "saved". When the background script does a console.log and i switch the debugging context to the injected script and trigger the method with the console.log (theres a message between them) and switch back to the background context and show the console, no output from the console.log is there
Eli Mitchellcyberstream # Wednesday, September 21, 2011 5:46:04 PM
sirnh1 # Wednesday, September 21, 2011 5:56:20 PM
David Håsätherhzr # Wednesday, September 21, 2011 6:11:53 PM
Originally posted by cyberstream:
This is planned, but we need the clipboard API to be implemented first.Originally posted by sirnh1:
Yes, this is planned.timmi # Wednesday, September 21, 2011 6:49:18 PM
David Håsätherhzr # Wednesday, September 21, 2011 8:16:22 PM
Unregistered user # Friday, September 23, 2011 12:41:46 AM
David Håsätherhzr # Friday, September 23, 2011 9:02:44 AM
Originally posted by anonymous:
I don't think it's possible to see if the crash had something to do with Dragonfly being open or not. Does this happen on specific pages, or is it random?metude # Sunday, September 25, 2011 7:07:16 PM
David Håsätherhzr # Tuesday, September 27, 2011 11:50:03 AM
Originally posted by metude:
No, this is not possible.metude # Tuesday, September 27, 2011 1:54:24 PM
David Håsätherhzr # Tuesday, September 27, 2011 8:58:05 PM
Originally posted by metude:
No, this is a big task and would first require large changes to Core before it could even be considered for Dragonfly.metude # Wednesday, September 28, 2011 5:22:39 AM
Originally posted by hzr:
Temp1AR # Thursday, September 29, 2011 11:04:13 AM
Rafald.i.z. # Friday, August 17, 2012 1:34:52 PM
Originally posted by anonymous:
There is one known crash related to pretty-printing scripts. You can try disabling that for the time being and seeing if it helps. It's the rightmost toolbar button on the Scripts tab.