Hey folks,
Apple removed Scripting Additions from developer builds of Lion and brought them back only at the last minute. This is likely a sign that Apple plans to phase this technology out, and soon, but is giving developers a little more time to make the transition. Because we're trying to standardize our extension experience across browsers and prepare for the future, we have already taken Apple's progressive philosophy to heart and are looking towards the future to create a better experience for all customers.
At the moment we don't have any plans to support OmniWeb, as it does not provide the same extensions framework available in Safari. For now we're focusing our efforts on browsers with a rich set of tools for extensions; currently this includes Safari, Firefox, and Chrome.
The aforelinked AgileBits forum thread has the longer explanation. Jeff did a good job of outlining both the technical and business angles of the situation:
http://forum.agilebits.com/index.php...post__p__35068
http://forum.agilebits.com/index.php...post__p__35261
I am an OmniWeb lover myself, so it gives me no joy to have it unsupported at this time. Point of fact: one of the top links in a Google search for "why use omniweb" is a link to
a blog post I wrote about my love for OmniWeb.
Quoting from Jeff:
As for plans, all I can say is what our hopes are. We hope to restore support, either through Scripting Additions or through the new technology.
I really wish I could give you something more definitive at this point. There are scenarios in which restored support for OmniWeb could happen quickly and scenarios under which it takes considerable time. I just don't know how these will play out at this point.
--
Khad Young
Forum Choreographer, AgileBits