Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.4: Retain old WebKit with Safari 3 Public Beta' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Retain old WebKit with Safari 3 Public Beta
Authored by: boredzo on Jun 29, '07 01:07:00PM

But this doesn't really keep "the old" WebKit framework; it "keeps" the current tip-of-tree WebKit framework (even newer than Safari 3's framework!) That's why they're nightly builds—because it changes every night.

If you want to retain the old WebKit, copy it from /System/Library/Frameworks into the WebKit.app before installing Safari 3. I haven't tested it, but that's how you achieve the goal stated in the title. The hint as presented won't do that.

I think the previous hint is a much better solution, env hackery aside. Also, it should be possible to invert that solution (end up with the Tiger WebKit in /S/L/F and the Safari 3 WebKit in WebKit.app) if you find that most of your apps choke on the newer WebKit, though I don't know how much Safari 3 will like that solution.



[ Reply to This | # ]
10.4: Retain old WebKit with Safari 3 Public Beta
Authored by: MattHaffner on Jun 29, '07 02:06:35PM

This hint is meant to "keep" the Tiger WebKit in /S/L/F completely intact with no changes so that other apps that use the framework are still using the Tiger version. Only Safari 3 will use the nightly WebKit. At least that's how I read it...



[ Reply to This | # ]
10.4: Retain old WebKit with Safari 3 Public Beta
Authored by: SineOtter on Jun 30, '07 07:44:02PM

MattHaffner is right: This hint allows you to run the Safari 3 beta without altering the /S/L/F version of Webkit.

Safari 3 requires some of the new features of WebKit that you can only get with the nightly or beta build- Hence why it was included in the Safari 3 beta install- But instead of doing it as a self contained framework they have it alter the /S/L/F version. This method uses the Webkit nightly build to shoe horn in the beta WebKit that Safari 3 needs without touching your /S/L/F version, leaving it at the shipping Tiger version and stepping around all the bugs caused by the beta build in other apps.

In summary: Your /S/L/F Webkit isn't touched at all (letting you keep the "old" version, not replacing it like you implied) meaning no bugs with other apps, and you can run Safari 3 using the WebKit contained in the webkit nightly build.



[ Reply to This | # ]
10.4: Retain old WebKit with Safari 3 Public Beta
Authored by: brad-x on Aug 04, '07 07:17:06AM
You're right, an inversion of the previous hint is superior. Notably, this hint also breaks the ability to use Safari as default RSS reader.

This can be done without pacifist, too. I derived the following from the method Michel Fortin uses to create standalone copies of older Safari versions.

1) Right click the .pkg file for Safari 3 and 'show package contents', and unpack Archive.pax.gz.
2) navigate into the new Archive folder. Take Safari.app out of Archive/Applications and place it somewhere.
3) Grab all frameworks from Archive/System/Library/Frameworks/ and place them inside Safari.app itself (via show package contents) - create a folder here called 'Frameworks'

(http://www.michelf.com/weblog/2005/multi-safari/ Explains some of the details from here on out)

4) Then use the following script: http://www.michelf.com/docs/blog/safari-script.zip - this is an extract from WebKit CVS which sets the Framework path to the location of the Application bundle itself rather than looking systemwide. Rename Safari.app/Contents/MacOS/Safari to TrueSafari and place this script in that location.
5) Make a backup of the Safari.app in /Applications
6) Move your new Safari.app to /Applications

This also has the benefit of using the release version of the webkit framework, not the current nightly version, which can cause crashes. As mentioned, you can now use Safari.app normally, without having to bother with webkit.app or do without Safari RSS feed URL handling.

[ Reply to This | # ]