Opera Dragonfly

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:

• 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
  

How to install
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/EditingINIFiles
http://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.

We have just released our first weekly build of Opera Dragonfly today. These are development snap shots and are not guaranteed to be stable, or even work at all. The weekly builds are released to get feedback and testing of the latest changes. If you'd like to report issues please go to the Opera Dragonfly feedback page.

Weekly snap shots will appear on the URL https://dragonfly.opera.com/app/weekly and should automatically update when a new version comes out. The snapshots can be downloaded at http://dragonfly.opera.com/app/weekly/zips/. The regular shipped url will update when official releases are updated.

There have been a number of bug fixes since the first alpha. A list can be found in the change logs. The most notable new features are Command Line completion and the Object Inspector. If you press the tab key when using the Command Line, it will auto-complete the first match. Pressing tab again will cycle through the matches. If you enter a command that returns a Object, you will be able to click on it and inspect the Object in the Object Inspector. This is located in a tab next to the Frame Inspector. Developing this functionality highlighted bugs in recent builds of the Opera Browser, so there are known issues with these features. Entries in the Object Inspector will not expand for example.

Progress is still on course for a second alpha release in the not too distant future. A desktop build will also be released soon that will fix the issues with Opera Dragonfly not working in offline mode, due to a bug with persistent cache not working over HTTPS. We're looking forward to you trying out this and subsequent weekly builds, and any feedback or bug reports that you send.

In somewhat related news, Opera also announced the launch of the Opera Widgets SDK this week. Opera Widgets can be debugged using Opera Dragonfly, and the SDK includes a useful Widgets Emulator for emulating how Widgets will look on different types of devices. Widgets currently work on devices such as the Nintendo Wii and ARCHOS, and upcoming UIQ 3.3 mobile phones. Widgets are currently Opera only, but we are standardising the spec at the W3C and will change our implementation to match the spec when it is finalised. We are also standardising the File I/O API spec at the W3C. This is a new API we have developed to access the file system, and is very useful for Widgets.