Omni Releases OmniWeb 4.5 Using Safari Engine
John C. Worsley writes "The Omni Group released version 4.5 of OmniWeb, based on Apple's WebCore and JavaScriptCore frameworks (the same KHTML-derived APIs that Safari uses)."
← Back to Stories (view on slashdot.org)
For the record, OmniWeb 4.5 does not use the "Safari engine." See, Safari is based on a framework called "WebKit." It's an Objective C framework. OmniWeb uses only WebCore and JavaScriptCore, open source libraries that are not really intended for public use.
The correct course of action would have been for Omni Group to wait for WebKit's release, rather than using WebCore and JavaScriptCore themselves. Alas, they chose to do it the wrong way. The result will be compatibility problems and bugs, unfortunately.
I applaud Omni Group for being really cool in many ways. This time, though, they really pulled a lame one.
omniweb has some stuff that apple could do well to integrate into safari - but they won't!
which is why I'm glad they've opened the engine up for third party use, because it means Apple can focus on speed and integration with the OS, and 3rd parties can get on with innovating.
The coolest feature in omniweb has to be the ability to customise urls in the url line; for example, I've set it up so if I type
fedex 574849
then it goes to the fedex order tracking site, and tracks order 574849. You can set these up for google, imdb, and anything else that gives results based on variables stored in the URL. It's awesome, and I haven't seen anything implemented like it anywhere else.
-- james
He was referring to pre-4.5 release where OmniWeb had it's own render engine.
Konq also has this feature, with built in queries for many popular sites.
Spencer Ogden
Actually ... checks CVS... (yes, I work for Omni)
OmniWeb's shortcuts have been around since at least Apr, 1998 (compared to May, 2001 according to Old Mozilla Releases). They were around in less featureful incarnations back to 1996 or 1997, judging from what I see in CVS.
Remember, OmniWeb is one of the oldest browsers still around:
We love it when other browsers copy OmniWeb's features (and we've certainly copied features from other places). What is even better is that with WebCore/JavaScriptCore we have to spend less time futzing with web standards (if they can be called that) and can work on honest-to-goodness innovations.
You can do that in Mozilla, as well.
(1) Live-Searchable History
(2) Form Spell Check (I'm Soaking in it)
(3) Self Updating Bookmarks Through The Dock
(4) Self-Fixing Bookmarks
(5) Superior Cookie Management (Three Levels)
(6) Programmable Address Bar Searches (Google, VersionTracker.. etc)
(7) Ad Blocking (And Yes OmniWeb Has Pop-up Blocking Too)
(8) Unbeatable Download Manager (Never seen it's Match)
(9) Extensive Source View, Edit, Publishing Capabilities
(10) Fully Voice Activated Interface and Link Navigation
(11) Speakable Pages (Useful When Your Eyes Just Can't Read Anymore)
(12) Browser Compatibility Settings
(13) JavaScript Compatibility Settings (Can Tie in or out With #11)
(14) JavaScript Bookmarklets
(15) Application Helper Settings For Downloads
(16) Network Activity Monitor (Similar to Mail.app's)
(17) Much More that I'm Overlooking
Um, I hate to break it to you - but Omni's page change notification system is hopelessly broken. It relies on websites returning a "304" response to indicate pages haven't been changed since a certain date, and a "200" response if they have. This worked back in the 90's. It doesn't anymore.
Many many many web sites now always return "200" no matter what. Google? 200. Any blogs you happen to read at Xanga, Blogspot, etc? 200. CNN, MSNBC, ABC, CBS, Slashdot, Yahoo, Apple? 200. Always. Without fail. Check every second - check every half-second, the website will still say it's been updated.
Don't believe me? Go through and set some of your bookmarks to check every minute, rather than the every couple of hours they're set at now. Then come back and tell me how great Omni's update checking is.
Builds of Camino existed with this feature. It matched Omniweb's behavior exactly. The feature was pulled because it was found to be worthless.
I think this was true several years ago, but we've been using the word count of the page (after stripping markup) for a long time now (since at least Apr 2000 according to CVS).
This approach generates some false positives, but in general, it's pretty good. Still, this is something that we'll be able to improve upon now that we can leave a bunch of the ugly stuff to Apple's WebCore/JavaScriptCore.
Cocoa Gestures is your answer... works in all cocoa apps -Rocks!!!
Well, you could have looked at an OmniWeb bookmarks file :)
My bookmarks file has, for example:
For some strange reason, OmniWeb and Metallifizer don't get along. The best workaround is to add OmniWeb to Metallifizer's "Exclude" list.
You're running Metallifizer, which attempts to change the appearance of running applications by loading code into them. I'd hardly consider that an OmniWeb problem. On a normally-functioning OS X system, OmniWeb renders fine.