My Opera
What's New in Opera Dragonfly with Opera Next
By Divya Maniannimbupani. Sunday, December 4, 2011 8:00:58 PM
New Release Model
You might have seen the flurry of updates in Opera Dragonfly – we now have CSS shorthands and also a style profiler! To make all this possible, we have also altered our release model.
Previously, we used to support older versions of Opera even with new releases, but it typically resulted in broken performance. Since Friday, we freeze a given Dragonfly version to an Opera version. This means, if you use a newer version of Opera, you get the latest, fastest version of Dragonfly that is stable and is confirmed to work on that version of Opera.
If you use remote debugging, be aware that this change may require your browser to load a previous version of Opera Dragonfly if connecting to an older browser version.
Local Zip Files
We have also vastly improved our build tools. You can now use a local version of Opera Dragonfly. What you might not know is you could also use them direct from the zipped file – less work for you! After downloading the zip file, you should set the Developer Tools URL in opera:config to:
file://localhost/<path to>/client-en.zip/client-en.xmlIf you are a user of another locale, just download the appropriate locale zip, e.g.
file://localhost/<path to>/client-es.zip/client-es.xmlZipped files are available for: latest build, cutting-edge, experimental.
JS Runtime Errors
Previously run-time errors were dropped in the console, but now you can actually see the line number and the script resource where an error occurred. Note that you currently need Opera Next to use this feature. Here is a screencast of this new feature in action:
Do note that, at the end, I show some features that are not yet part of this experimental build, but will be soon. 
To use the experimental build of Opera Dragonfly, set the URL for opera:config#DeveloperTools to:
https://dragonfly.opera.com/app/experimental/Please try it out and let us know what you think of it!
BLOBO # Monday, December 5, 2011 4:34:28 PM
Егорtermi1uc1 # Monday, December 5, 2011 4:52:41 PM
d4rkn1ght # Monday, December 5, 2011 4:54:29 PM
svdb0 # Monday, December 5, 2011 5:06:39 PM
Will it be possible to see the selected expression in the state inspector as well?
Btw, the link back from YouTube is broken.
MyOpera team, please fix this!fearphage # Monday, December 5, 2011 6:46:35 PM
It would be nice if this was worked out internally so that nothing was exposed to the world outside of these branches (aside from pulling the code down yourself obviously).
My goal/hope/dream is to have the latest and greatest dragonfly code with the least amount of work. To me, that would mean I could point to one URL and every time a new blog post about a new feature landed here, I'd already have it. I wouldn't have to update configs or download some file.
Also out of latest, experimental, and cutting edge, which one is the most up-to-date? This use of synonyms and similarly meaning words should be documented in a wiki or somewhere if it isn't already.
Thanks team.
gwarser # Monday, December 5, 2011 7:01:26 PM
Divya Maniannimbupani # Monday, December 5, 2011 7:29:23 PM
Divya Maniannimbupani # Monday, December 5, 2011 7:31:39 PM
Originally posted by svdb0:
Fixed!
Christian Krebsaleto # Monday, December 5, 2011 7:36:33 PM
* https://dragonfly.opera.com/app/experimental/
This path is to try out new features. There is no guarantee that a feature which appears on this branch will land on the other branches. We have no internal requirement for this branch. If someone likes to try out something, he can basically make a build from his work branch and put it on "experimantal".
* https://dragonfly.opera.com/app/cutting-edge/
Buildss on this branch are release candidates. An according build can only be created from our mainline. That means any code was at least reviewed by two other developers. The build must have an according tag in our repo. Each candidate build must be tested and approved by a QA depending on a diff to the last release.
* https://dragonfly.opera.com/app/
Buils on this path are meant to be stable. An according build must have passed the testing on the "cutting-edge" path.
* https://dragonfly.opera.com/profiler/
This is a special path to make the new profiler available to our users, but also to ourself, so that we can improve the Dragonfly performance. There is still some work to do to integrate it on mainline, mainly we need to adjust our design of handling scope services.
Each of the above paths has a zip directory, that is
* https://dragonfly.opera.com/app/stp-1/zips/
* https://dragonfly.opera.com/app/stp-1/cutting-edge/zips/
* https://dragonfly.opera.com/app/stp-1/experimental/zips/
with a zip for each build ever created for that path. To make it easier to find the latest zip, we have now shortcuts:
* https://dragonfly.opera.com/app/stp-1/zips/latest/
* https://dragonfly.opera.com/app/stp-1/cutting-edge/zips/latest/
* https://dragonfly.opera.com/app/stp-1/experimental/zips/latest/
Patrick H. Laukepatrickhlauke # Wednesday, December 7, 2011 10:39:37 AM
"My goal/hope/dream is to have the latest and greatest dragonfly code with the least amount of work"
then stick to the experimental branch https://dragonfly.opera.com/app/experimental/
JanGen # Thursday, December 8, 2011 10:03:38 AM
Originally posted by aleto:
I guess that's a typo: should be NO guarantee?
Can't we have a selection field for choosing the DF version in opera:config.
Always looking up the url's to try out a new version is a waste of time,
Daniel Herzogdanfoooo # Thursday, December 8, 2011 12:28:43 PM
Originally posted by gwarser:
Thanks, this is known and filed internally as DFL-2444
Christian Krebsaleto # Thursday, December 8, 2011 2:00:51 PM
Originally posted by JanGen:
Yes, of course, thanks, fixed it.
MyOpera team, please fix this!fearphage # Monday, December 12, 2011 9:16:38 PM
Any chance that there will be a bleeding edge/this may not function at all/nightly/hourly branch that the brave ones can use? I want to be seeing Chris's changes (live) without jumping to every branch he (and the team) are developing on. I'm thinking commit hooks to push to some branch. Thoughts?
Side note: Chris and Divya, you aren't a member of the Opera Employees group - http://my.opera.com/Opera/ I have a scripts that highlights employees and I wondered why it missed you... and that's why.