By David Storey.
Thursday, 19. February 2009, 15:58:32
localisation, Opera Dragonfly, alpha 3
[UPDATE] Added Bulgarian, Tamil, Telugu, Turkish and Ukrainian, which I accidently missed from the list.
We have just released a further update to the alpha 3 branch of Opera Dragonfly. This is mainly a bug fix release, with numerous stability enhancements. Check out the change logs for full details of the included fixes.
The main noteworthy fix for this release is the localisation of Opera Dragonfly into 37 different languages. A big thank you should go out to everyone that helped us with these translations. The included localisations include:
- bg: Bulgarian
- cs: Czech
- da: Danish
- de: German
- el: Greek
- en: English
- es-ES: Spanish (Spain)
- es-LA: Spanish (Latin America)
- et: Estonian
- fi: Finnish
- fr: French
- fr-CA: French Canadian
- fy: Friesian
- hi: Hindi
- hr: Croatian
- hu: Hungarian
- id: Indonesian
- it: Italian
- ja: Japanese
- ka: Georgian
- ko: Korean
- lt: Lithuanian
- mk: Macedonian
- nb: Norwegian bokmål
- nl: Dutch
- nn: Norwegian nynork
- pl: Polish
- pt: Portuguese
- pt-BR: Portuguese (Brazilian)
- ru: Russian
- sv: Swedish
- ta: Tamil
- te: Telugu
- tr: Turkish
- uk: Ukrainian
- zh-cn: Simplified Chinese
- zh-tw: Traditional Chinese
You can change the UI language of Opera Dragonfly by clicking the settings icon (lower right hand corner), clicking the general expander (the text is now clickable as well as the arrow icon), and select the language from the drop down list.
This release is scheduled to be the last release on the Scope protocol 3 branch, which is for Opera Presto 2.1 based browsers, such as Opera 9.6. Full focus will now be on Scope protocol 4 based releases for Opera Presto 2.2, and the upcoming Opera Dragonfly alpha 4 release. You can track progress of this by using builds of Opera 10. Much requested features such as automatically detecting the active tab are now working in the Scope 4 branch of Opera Dragonfly.
By David Storey.
Thursday, 30. October 2008, 15:54:48
DOM, alpha 3, developer tools, Opera Dragonfly
We’ve got a couple of announcments related to Opera Dragonfly today. The first piece of news is that Opera Dragonfly alpha 3 has just been released. The main focus of this release has been fixing reported bugs, to make the user experience more pleasant. We’ve also added localisation support—which was introduced in the previous weekly release. The German translation is ready, and we are working on other locales, that will be pushed live as they are completed and QA'd. We hope this will make Opera Dragonfly more useful in the none-English speaking world. Obviously markets where Opera is more popular have high priority, such as Russian and Indonesian.
One of the key new features of Opera Dragonfly alpha 3 is DOM editing support. There is two modes. The first mode allows you to edit, add and delete attributes and text nodes in real time. You can activate this by double clicking on a attribute, value or text node. The second mode allows you to do free form editing, such as adding new DOM node. You can activate this by double clicking on the opening or closing tag of a element. This will turn the entire element and its children into a free form text field. There is currently a known issue with the first mode, where focus doesn't leave the editing mode when pressing the enter/return key. This will be silently updated as soon as it is fixed.
The other main new feature is that the breadcrumb trail has been updated. Now each node acts like a button, so you can navigate the element hierarchy more easily.
The next release will be Opera Dragonfly alpha 4, which is under heavy development. This has been under development at the same time as alpha 3, as it requires new features found in the Scope module that is part of the upcoming Opera Presto 2.2 rendering engine. It will refine the user experience some what, as the currently active tab will be detected. This will tidy up the layout and make the docked mode much more logical to navigate. It will also introduce a HTTP inspector.
The way experimental releases are handled has also changed. Now instead of switching to the path for weekly releases, Opera Dragonfly will detect if you are on a stable release version of Opera or a pre-released version, such as an alpha, beta, or weekly release. If you are using a stable release it will use the latest official release of Opera Dragonfly (currently alpha 3). If you are using a pre-released version of Opera it will automatically updated to the latest experimental version of Opera Dragonfly. It is possible to force the use of a stable or experimental version. This is explained in the URL Schema document.
In further Opera Dragonfly news, we now have a person who is focusing on Project Management for Opera Dragonfly. I’ve been handling Product Management, but the Project Manager role has been vacant. The new Project Manager is Arve Bersvendsen, whom many of you may know already. He will bring a great deal of experience and knowledge into the project. I’ll let him introduce himself further in this blog when we have some more news to tell. For now, have fun playing with the latest release.
WIDGETIZE