|
|
10.4: Retain old WebKit with Safari 3 Public Beta
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.
10.4: Retain old WebKit with Safari 3 Public Beta
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...
10.4: Retain old WebKit with Safari 3 Public Beta
MattHaffner is right: This hint allows you to run the Safari 3 beta without altering the /S/L/F version of Webkit.
10.4: Retain old WebKit with Safari 3 Public Beta
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. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|