Quote:
|
Originally Posted by Gregory
I myself found the instructions confusing. I downloaded the recommended webkit, launched it, found it to launch instead of install, found that it looked like Safari, quit it, copied it to Applications and left it there.
do we need WebKit or not?
should it be running in the background or placed in a special place?
|
In a nutshell:
1. OmniWeb 5.5 is based on WebKit but the version it uses (I assume) will be a part of the OmniWeb package itself.
2. Safari will use the system-wide version of the WebKit framework (I assume)
3. The WebKit application you download is like OmniWeb - its version of WebKit is bundled as part of the application. It looks exactly like Safari when it is running because it is Safari, just using a newer version of WebKit.
Note: You can run all three at once if you want to because they all use independent versions of WebKit.
The confusion stems from the developers of WebKit the framework choosing to call their Nightly builds WebKit
as well, even though it is a bundled application.
Now, why do you want to have the WebKit, as the bundled application, that OmniWeb is currently based on?
So that any issues with rendering or other UI bugs can be checked against the WebKit application - if that app suffers the same issue then the bug is in the WebKit framework and needs to be reported to Apple and the WebKit developers. If it is only in OmniWeb then it needs to be reported to OmniGroup. Make sense now?