Well, wouldn’t you know it; today we launched the very first beta of the new Opera Developer Community site, named “Dev.Opera”:http://dev.opera.com/
First of all, when we say beta, we mean beta, so we welcome any and all feedback for the site in “the beta thread”:http://dev.opera.com/forums/topic/165025 in the developer forums.
So, what’s there? Let’s do a little walkthrough, in no particular order.
h3. User contribution
Like “Soylent Green”:http://en.wikipedia.org/wiki/Soylent_green, Dev.Opera is made of people. This means that you, as a developer are welcome to “contribute content”:http://dev.opera.com/articles/info/ to us.
One of the keystones of the site is the “article repository”:http://dev.opera.com/articles/ – currently featuring articles on mobile, SVG and voice. However, we are planning on expanding this, with content from both external contributors and Opera staff (I plan on, whenever time permits, to write something massive on the use of canvas).
h3. Forums and article discussions
Every article published on Dev.Opera has “discussions attached”:http://dev.opera.com/forums/forum/3589 and there is a forum for “general developer discussion”:http://dev.opera.com/forums/forum/3590
h4. Open Source
h4. What’s different?
In the Web Application team here at Opera, we often work with many more constraints than you normally have when working on desktop. When we first released the “Opera Platform SDK beta”:http://www.opera.com/products/mobile/platform/ our target devices were Series 60 phones that were beyond slow; clocking in at around 100MHz, and with next to no memory we wrote code that performed fairly well. This has also affected the libraries, because rather than having larger, monolithic libraries, these libraries are in the “pick-and-choose” category, written to perform well within constrained scenarios. This does not however mean that what you find in here can’t be applied towards other scenarios than our own.
Also note that the libraries are, since we haven’t usually been constrained to the must-work-in-a-zillion-browsers-problem written more to conform to standards than to browser. Which means that your luck in applying some of these libraries towards IE6 may vary. Also note that we do not deliberately break scripts for other browsers.
Please realise that when I said we meant beta, we meant beta: We’re planning on adding more here. A lot more. And we would welcome feedback on what _you_ would like to see as well.
The term “we” in this post does not mean that anything I’ve written here is from the Gospel of Opera, nor do I mean that the opinions herein neccesarily reflect those of my employer or all of my co-workers. I use the term “we” because I believe Dev.Opera is a team effort. It’s made of Soylent Green. Kudos to the team of editors, developers, internal beta testers and contributors who got us so far.