It has been a while since I’ve posted here, but today there’s more than a good reason to pick up the habit again :-) Here at Opera (I’ve been working for Opera’s Tokyo office since last Summer), we’ve released a first alpha of our developer tools, also known as Opera Dragonfly.
Over at Dev.Opera, you find a first introduction to Dragonfly, and for those interested in the different components of this complex JavaScript app, there is a Dragonfly architecture article.
We’re planning to release more in-depth Dragonfly articles soon, but in the meantime, have fun, and let us know what you think in the comments of this post, or on the Dragonfly forum.
Opera has a second beta out for version 9.5. Go get it!
Also, it’s a long lime since I first heard about this project. But I’ve not been able to say anything before now… Opera has for a while been the only one of the four major browsers to not ship any form of JavaScript debugger. Opera Dragonfly is going to rectify that. It’s first alpha is going to be released to the masses May 6th according to Opera’s Chief Web Opener, David Storey. While the first release is not going to be feature complete, I promise you it’s going to be sweet. Firebug-like sweet.
If you read this website with any regularity you may have noticed it was replaced with a 500 error for a while. My apologies, I have no idea what triggered it.
After some fruitless searching, I feel duty-bound to at least blog about how I fixed the issue:
Also worth noting - this issue has nothing to do with Media Temple (my preferred host for personal and professional work) I just mentioned them since this seemed like a hosting issue and I tended to include them when scouring for solutions.