Since the inception of Opera Dragonfly, we planned for it to become an open source project. It has always been released under an open source BSD licence, but the source repositories were on Opera servers. Starting today, Opera Dragonfly is a fully open source project, hosted on BitBucket. Since the previous version of Opera Dragonfly, a lot of work has gone on behind the scenes replacing the existing architecture with a modern version of the Scope Protocol STP-1. Opera Dragonfly has been rewritten to use this faster and more efficient version of Scope. Now that we believe that the underlying protocol is stable and performant, and a public desktop build has been released with this included, it is time to put Opera Dragonfly on a public Mercurial repository.
If you have a Mercurial client you can visit the Opera Dragonfly STP-1 repository and check out the source code. We have provided initial documentation in the Wiki to get you started. This is Operas first full open source project, so there will be a learning curve. We ask you to bear with us while we get everything up and running and policies in place. Coming from a closed source background there are some hurdles to overcome, such as the current bug tracking system being on a closed server. We hope to migrate to an open bug tracking system as the project gets on its feet.
As well as the current and previous versions of the Opera Dragonfly source code, we have released a couple of tools to help with Opera Dragonfly development. The first is Dragonkeeper. This is a standalone proxy, which translates STP (Scope Transport Protocol) to HTTP. This can also be useful for remote debugging. The second tool is Hob. Hob is a utility to create code from Protocol Buffer descriptions. Protocol Buffers are one of the formats Scope STP-1 supports along with JSON and XML.
The focus of the current release of Opera Dragonfly was stability and performance. As such you will not see a great deal of new features. We believe it was invaluable to build a strong foundation, so we can advance faster, with less issues in the future. Two new features you may notice since the previous desktop release are a new element highlight (first introduced in Opera Mobile), and a colour picker utility. The highlight has been optimised since the mobile release, and supports visualising the metrics of an element on the page, and multiple element selection. The colour picker is still in early development. It allows for the magnification and selection of colours from the Web page. The value of the colour is displayed in both HSL, RGB and hexadecimal formats. Work has also began behind the scenes to take advantage of HTML5 Web Storage to store users settings and preferences. This will eventually allow the application to be greatly customisable, and to remember layout and settings from a previous session. One of the biggest usability issues has also been solved, with inspect element being available from the Web page context menu. This reduces the steps needed to start debugging a Web page.
The current focus for the Scope protocol is improving the JavaScript debugger. This work is nearing completion on the Scope side, and will provide functionality such as the Firebug Console API.
We hope you enjoy this version of Opera Dragonfly, and that some of you will be inspired enough to help with the Opera Dragonfly project. If you like a challenge, this is a great place to start. Visit the Opera Dragonfly repository to find out more information.
Note that there is a precise definition of the terms MUST, SHOULD, MAY, SHOULD NOT and MUST NOT found in RFC 2119, which every W3C spec references (and in certain cases extend) for defining these terms. Look for any section or chapter using the word "Conformance". On should, it says:
SHOULD This word, or the adjective "RECOMMENDED", mean that there
may exist valid reasons in particular circumstances to ignore a
particular item, but the full implications must be understood and
carefully weighed before choosing a different course.
I'm somewhat surprised that this crowd hasn't picked up that there is also a Chris Pine who was lead programmer for Civilization III, author of Learn to Program, and a current Opera employee.
Unless you are doing a lot of Ajax it isn't hard to support Opera.
The only reason is because you are lazy.
I'll start with the disclaimer first: I work at Opera Software, with Web applications. Then I'll continue with an honest-to-god question, as I have more of an interest in understanding why people's sentiments are as they are:
Where does the misconception that Opera can't do "a lot of Ajax" come from? Because it clearly can, for instance, see Aida, the Ajax phone -- a rather massive Ajax framework and appplication running on top of Opera Platform (a runtime which provides access to certain aspects of the device, such as battery status, connectivity, message stores and such).
What I have to ask is, "Is CSS to blame for the tiny text in boxes with horizontal scrollbars?"
Ok. I realise this answer is coming very late, but no: Your browser is. This is a particular aspect of Gecko's special handling of font declarations that specify monospace. See Monospace, Firefox and braindeath and Sizing monospaced fonts
But ahhhhhh! I opened my history to come here to post this and I dont like the new history. i like the giant list, not collapsable folders.. AHHHHHH::head explodes::
There is a View view button in the history tab. Select "By time visited" and you have what you used to have.
I would however also suggest that you learn to use the new history, and the quickfilter feature. I love the "By time and site" feature. Usually when I want something in history, I have a vague idea about what I wanted to go back to, and when I did so.
The Opera canvas extension
on
Opera 9.0 Released
·
· Score: 3, Informative
The canvas extension in question is the opera-2dgame context. Some of what it features is:
setPixel and getPixel
point in path-detection, using checkCollision
canvas update locking
There is work underway to get a similar API for the canvas into the specification.
Disclaimer: I am the author of the mentioned blog post detailing the opera-2dgame context.
No, it's not academic at all. ACID2 tests support for a few key standards, and how error handling works. As such, developers can expect browsers that pass the test to behave somewhat predictably.
UserJS.org -- Granted, Opera can run many Greasemonkey scripts, the userjs.org feature of Opera allows some additional capabilities. These scripts are all compatible with Opera, and have undergone QA to verify that scripts are non-malicious, and as efficient as possible
Assuming that they actually eat their own dog food, and use their own tool to create their Own site, I wouldn't trust this tool. Their site is an inaccessible piece of table-based rubble with missing alternative texts all over the place. Not even Slashdot in it's old incarnation was this ugly, standards-wise.
Adding to that, their site is severly SEO-deoptimized, which might -- now that I think of it -- be a good thing to end-users, as this will undoubtedly reduce the spread of said markup rubble
I'll never get Slashdotters' obsession with KDE and GNOME. Both projects absolutely suck. Their APIs are a joke. GNUStep/OpenStep, on the other hand, is a true object-oriented environment, and it really does make Gnome and KDE obsolete.
I'll never get someone's obsession to shove hideously ugly GUIs down users' throats. This looks like something I used when my Unix terminal was still using a black-and-white screen. This looks like something I used when my Unix desktop was totally useless.
Gnome and KDE can at least be made to look and feel nice. That is all I need to know. I don't care about any "elegant" solutions under the hood.
Dysons research is not a justification for marathon line lengths. It merely indicates that the issue is more complex than in print typography, and, I infer, that categorical declarations are hard to back up with evidence.
On my always full-sized browser-window, Jakob Nielsen suffers from these marathon line lengths, which is exactly why I wrote that fix.
Looking at the Alexa traffic details for your site, I somehow doubt that you have a real userbase of 200 000. Compare it to for instance kottke.org's traffic details, I'd say that you need visitors before anything else. Kottke has loads of more traffic, and took a hefty paycut to blog full-time
And yes, I am aware that Alexa is not an exact measure, but it should act as an indication that you very likely won't find a business model at all that is fit for supporting a full-time staff.
As for maximizing revenue with what you have, the colors and placement of your Google ads is pretty appaling: They are below the fold for many users, and they are hidden where users won't look for them, and they have a color scheme as inviting as a World-War II bunker.
So, then I presume you can point out each and every aspect of Acid2 that violates CSS 2.1.
We'll also expect you to hold your breath doing this excercise on a live webcam, so we can see you turn blue in the face.
The acid2 test consists of perfectly valid CSS2.1, HTML 4.01, SGML, RFC 2396 and RFC 2397. It tests some basic, and some not-so-basic aspects of these specs.
Slashdot Mirror
Here:
Since the inception of Opera Dragonfly, we planned for it to become an open source project. It has always been released under an open source BSD licence, but the source repositories were on Opera servers. Starting today, Opera Dragonfly is a fully open source project, hosted on BitBucket. Since the previous version of Opera Dragonfly, a lot of work has gone on behind the scenes replacing the existing architecture with a modern version of the Scope Protocol STP-1. Opera Dragonfly has been rewritten to use this faster and more efficient version of Scope. Now that we believe that the underlying protocol is stable and performant, and a public desktop build has been released with this included, it is time to put Opera Dragonfly on a public Mercurial repository.
If you have a Mercurial client you can visit the Opera Dragonfly STP-1 repository and check out the source code. We have provided initial documentation in the Wiki to get you started. This is Operas first full open source project, so there will be a learning curve. We ask you to bear with us while we get everything up and running and policies in place. Coming from a closed source background there are some hurdles to overcome, such as the current bug tracking system being on a closed server. We hope to migrate to an open bug tracking system as the project gets on its feet.
As well as the current and previous versions of the Opera Dragonfly source code, we have released a couple of tools to help with Opera Dragonfly development. The first is Dragonkeeper. This is a standalone proxy, which translates STP (Scope Transport Protocol) to HTTP. This can also be useful for remote debugging. The second tool is Hob. Hob is a utility to create code from Protocol Buffer descriptions. Protocol Buffers are one of the formats Scope STP-1 supports along with JSON and XML.
The focus of the current release of Opera Dragonfly was stability and performance. As such you will not see a great deal of new features. We believe it was invaluable to build a strong foundation, so we can advance faster, with less issues in the future. Two new features you may notice since the previous desktop release are a new element highlight (first introduced in Opera Mobile), and a colour picker utility. The highlight has been optimised since the mobile release, and supports visualising the metrics of an element on the page, and multiple element selection. The colour picker is still in early development. It allows for the magnification and selection of colours from the Web page. The value of the colour is displayed in both HSL, RGB and hexadecimal formats. Work has also began behind the scenes to take advantage of HTML5 Web Storage to store users settings and preferences. This will eventually allow the application to be greatly customisable, and to remember layout and settings from a previous session. One of the biggest usability issues has also been solved, with inspect element being available from the Web page context menu. This reduces the steps needed to start debugging a Web page.
The current focus for the Scope protocol is improving the JavaScript debugger. This work is nearing completion on the Scope side, and will provide functionality such as the Firebug Console API.
We hope you enjoy this version of Opera Dragonfly, and that some of you will be inspired enough to help with the Opera Dragonfly project. If you like a challenge, this is a great place to start. Visit the Opera Dragonfly repository to find out more information.
While Ruby and Java are nice and all, I give you Brainfuck and Ook!.
Note that there is a precise definition of the terms MUST, SHOULD, MAY, SHOULD NOT and MUST NOT found in RFC 2119, which every W3C spec references (and in certain cases extend) for defining these terms. Look for any section or chapter using the word "Conformance". On should, it says:
I'm somewhat surprised that this crowd hasn't picked up that there is also a Chris Pine who was lead programmer for Civilization III, author of Learn to Program, and a current Opera employee.
I'm not sure I would trust a survey that has an obscure scripting language clocking in at 0.13% in the September 2007 results.
vrms seems a bit outdated. Example output:
Xara Xtreme is GPL
I'll start with the disclaimer first: I work at Opera Software, with Web applications. Then I'll continue with an honest-to-god question, as I have more of an interest in understanding why people's sentiments are as they are:
Where does the misconception that Opera can't do "a lot of Ajax" come from? Because it clearly can, for instance, see Aida, the Ajax phone -- a rather massive Ajax framework and appplication running on top of Opera Platform (a runtime which provides access to certain aspects of the device, such as battery status, connectivity, message stores and such).
Ok. I realise this answer is coming very late, but no: Your browser is. This is a particular aspect of Gecko's special handling of font declarations that specify monospace. See Monospace, Firefox and braindeath and Sizing monospaced fonts
There is a View view button in the history tab. Select "By time visited" and you have what you used to have.
I would however also suggest that you learn to use the new history, and the quickfilter feature. I love the "By time and site" feature. Usually when I want something in history, I have a vague idea about what I wanted to go back to, and when I did so.
The canvas extension in question is the opera-2dgame context. Some of what it features is:
There is work underway to get a similar API for the canvas into the specification.
Disclaimer: I am the author of the mentioned blog post detailing the opera-2dgame context.
New York times has a bit about Oslo on a budget.
If it did, GWB would probably just declare "War on Meteorites", and Americans would all be so much safer.
Uh. Wait.
IANAL, but from my understanding, EULAs are not legally binding contracts under Norwegian law.
Indeed. I'm impressed. A technology that forces me to remain seated and eyes glued to the screen.
No, it's not academic at all. ACID2 tests support for a few key standards, and how error handling works. As such, developers can expect browsers that pass the test to behave somewhat predictably.
Here are some additional links with more information and screenshots, so you won't have to wade through all of the Opera forums to find them:
Assuming that they actually eat their own dog food, and use their own tool to create their Own site, I wouldn't trust this tool. Their site is an inaccessible piece of table-based rubble with missing alternative texts all over the place. Not even Slashdot in it's old incarnation was this ugly, standards-wise.
Adding to that, their site is severly SEO-deoptimized, which might -- now that I think of it -- be a good thing to end-users, as this will undoubtedly reduce the spread of said markup rubble
I'll never get someone's obsession to shove hideously ugly GUIs down users' throats. This looks like something I used when my Unix terminal was still using a black-and-white screen. This looks like something I used when my Unix desktop was totally useless.
Gnome and KDE can at least be made to look and feel nice. That is all I need to know. I don't care about any "elegant" solutions under the hood.
From the story you quoted
On my always full-sized browser-window, Jakob Nielsen suffers from these marathon line lengths, which is exactly why I wrote that fix.
And no, don't ask me to resize my browser window.
What about reading the series updated for Opera 8
The torrent files are offered by Opera.com, so they are not "random" torrents.
Looking at the Alexa traffic details for your site, I somehow doubt that you have a real userbase of 200 000. Compare it to for instance kottke.org's traffic details, I'd say that you need visitors before anything else. Kottke has loads of more traffic, and took a hefty paycut to blog full-time
And yes, I am aware that Alexa is not an exact measure, but it should act as an indication that you very likely won't find a business model at all that is fit for supporting a full-time staff.
As for maximizing revenue with what you have, the colors and placement of your Google ads is pretty appaling: They are below the fold for many users, and they are hidden where users won't look for them, and they have a color scheme as inviting as a World-War II bunker.
And, whacking myself with the cluehammer: It does contain invalid statements, but these are not the main point of the test.
So, then I presume you can point out each and every aspect of Acid2 that violates CSS 2.1.
We'll also expect you to hold your breath doing this excercise on a live webcam, so we can see you turn blue in the face.
The acid2 test consists of perfectly valid CSS2.1, HTML 4.01, SGML, RFC 2396 and RFC 2397. It tests some basic, and some not-so-basic aspects of these specs.
I love questions answer themselves.