By David Storeydstorey. Thursday, June 26, 2008 2:37:48 PM
We've just released the Release Candidate for Opera Dragonfly alpha 2. New features added since the initial alpha include auto-complete for the Command Line (including object inspection), docked window mode, CSS editing including auto-complete, and a downloadable debug menu. There has also been many bug fixes and stability improvements.
Support for editing and a single window mode have been two of the three most requested features for Opera Dragonfly. The third was HTTP inspection, but this requires Core support to expose the required information through Scope, and will require the next version of our Core rendering engine. Alpha 2 will debut experimental support for the first two features.
Currently only CSS editing is supported, but much of the code can be reused for DOM editing for alpha 3. CSS can currently be edited by clicking on a property or value in the styles sidebar. User defined values are editable, but not the browser default values. Pressing tab will move to the next token (and shift-tab for the previous token). Pressing the up or down arrows on the keyboard activates auto-complete, that will cycle through the valid values. Typing co then the down arrow when a property is highlighted will suggest
color for example. Pressing the up or down arrow on a value will increase or decrease the value. All changes are live and instant, so it is incredibly useful for testing tweaks and colour or size changes. I find it very useful when using HSL colour values for example, to get the exact shade I want to use. When at the end of a line or when the value is highlighted, pressing return will create a new property.
The docked window mode is now default, but can be changed to a separate window by pressing the icon next to the close button in the top right corner of the Opera Dragonfly UI. The UI for the docked mode is still very experimental as the support came at the end of the Opera 9.5 development phase. The UI will be improved to make it less confusing in alpha 3.
Command Line auto-complete has already been mentioned in this blog, and can be activated by pressing the tab key. If an object is returned it is highlighted and can be clicked on. Doing this will allow the object to be inspected in the Inspection sidebar. A debug menu has also been released to complement Opera Dragonfly, which currently packages existing Opera features that are useful to developers, along with links to reference materials and validators. This will be improved upon in the future to add new functionality. It can be downloaded on the Opera Dragonfly web site.
Once alpha 2 is released there will be a break while the lead developer takes a much deserved holiday, then work will resume on Opera Dragonfly alpha 3. This should include more bug fixes, DOM editing, support for localisation, UI work and more.
You can test out the release candidate of alpha 2 by entering https://dragonfly.opera.com/app/weekly into the Developer Tools URL of opera:config and pressing the save button. Please give us feedback in the usual places.
By Shwetank Dixitshwetankdixit. Monday, June 9, 2008 2:04:52 PM
Today we are releasing the ‘Debug Menu’ targeted at all you web developers out there. This menu is meant to complement Opera Dragonfly and provide web developers with a better experience with performing common tasks.
The goal of the debug menu is to bring developer specific functionality already present
in the browser in one place, further enhanced with some extra features and reference materials.
Extra features include:
How to install
- Open Opera Dragonfly (you might find this easier, instead of going to tools->advanced->developer tools every time you want to open Opera Dragonfly)
- Validate HTML5
- Validate CSS2.1 and CSS3
- Get an Accessibility and Section 508 report.
- Check for broken links.
- Check how your page will display in Opera Mini
- Check the rendering mode of your page
- Reload all images (without reloading the page).
- Check Alexa rank and Compete.com traffic analysis
- Documentation on HTML4.01, CSS2.1, XPath, XSLT and Unicode.
- Check WHOIS information
Just click here
to download the Menu.Requirements
It should be used in Opera 9.5. You can download Opera 9.5 from here
.Customize and build on it
Check out the links below on how to make your own .ini file for a custom menu. You can use the same information to edit this .ini file and add/remove/change the settings.http://operawiki.info/EditingINIFileshttp://operawiki.info/AdvancedToolbarINIGuide
You are not limited by just this Menu. You can download other toolbars, menus and setups as well, that are made by Opera fans.
Have fun with the menu!Newest Opera Dragonfly Weekly now live
You can download build 08-06-09-15-30
. Bug fixing was the major focus of this weekly release, and here is changelog
detailing all the fixes.
One of the major changes is that now Opera Dragonfly can remember its state. Attached or detached.
As mentioned in previous posts as well, automatically updated weekly builds can be found at https://dragonfly.opera.com/app/weekly/
. Update the URL by going to Opera:Config -> Developer Tools -> Developer Tools URL . This way you can always automatically get the latest updates.
By David Storeydstorey. Monday, June 2, 2008 3:36:58 PM
We've just released the latest weekly release of Opera Dragonfly. The biggest change over the previous build is that it now works in a panel, which allows Opera Dragonfly to work in a single window. This has been one of the biggest requests from users. A recent Opera 9.5 build is required for this to work. You can download this from the Desktop Team blog. The support for this is still highly experimental, so the interface is far from complete, and will change. The style sheets view is still under construction for example. There will likely be a number of regressions.
Download build 08-06-02-16-10. Automatically updated weekly builds can be found at https://dragonfly.opera.com/app/weekly/. Update the Opera Dragonfly URL in Opera:config to this address to enable automatic updates to the latest weekly release.