|
|
Code Signing = Solution to code signature/Autofill/Keychain incompatibility?
Hi Camel,
Yes, that is indeed what i'm saying. I've made a copy available http://www.mediafire.com/?mjxg1cwscjn That way you can see for yourself :-) Cheers, Peter
Code Signing = You are Da Man
Peter,
Code Signing = Ben Da Man, You Da Man!
Hi again Camel,
That's very nice of you, but all the glory rightfully goes to Ben Rockhold. I just flipped through the developer docs to the chapter on CodeSigning, so if thanks are due, they must be given to Apple's good documentation :-) If Ben or Rob would like to re-post all of the good info in this hint+thread, and include the file as a demo, I think that it'd be a good idea, but i can't rightfully do it myself... Be Well! Peter
I don't mean to insist
I doubt anyone is still reading this, but there was one last problem with this configuration:
If Safari and SafariBeta were not running, no matter how often you told the "internet preferences" that SafariBeta was your choice, clicking a link in, say, Mail, would open it in Safari (current). So, I just went into the version.plist file and changed the CFBundleIdentifier from com.apple.safari to com.apple.Safari_beta also changed CFBundleName to Safari_beta Finally, I made a duplicate of the preference file (~/Library/Preferences/com.apple.safari) and called it, you guessed it, com.apple.Safari_beta Now Safari_beta is treated as a proper app by the MacOS 10.5 or 10.6. I will post the new app asap Be Well, Peter |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks 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.06 seconds |
|