I just read that CDSA is deprecated in OS X 10.7.
What is the recommended replacement?
I am especially interested in the plugin framework: what is the new way to implement access to smartcards etc.? Tokend is deprecated now: what does Mail and Safari use to access private keys?
As it seems by Apple's own CommonCrypto system.
Here's a link to the man pages.
It seems to have been originally developed for iOS.
Related
Xcode8 now officially support editor extensions, and forbids code injection, preventing previous extensions (served by Alcatraz for example) to execute.
It may be a dumb question, but I'm totally unable to find an answer:
Where can I search for existing Xcode8 extensions?
For example, with Alcatraz there was a panel in Window > Extensions, which presented a list with all available extensions. With Xcode 8.0 (official release) there is no such option.
In WWDC video, the guy talks abound downloading them from the mac App Store. But again, I'm unable to find a category or any one of them.
(note: I'm still on El Capitain)
This is all I could find:
Awesome native Xcode extensions
Xcode-8-extensions
The Xcode extensions can be found on the App Store, for example i have been able to find this one: Text Toolset
They have to be enabled after installing by going to the system preferences > extensions.
Overall they are really hard to find, as they do not have a separate category on the App Store.
I have to switch from a normal WebView to Chromium because this solution is said to work much better with a special database.
I downloaded the CefSimpleSample and I think I understand how it works.
I included the used libraries but I can't get the project working as it's supposed to be.
Does anybody have experience with Cef in an OS X - XCode - Application?
Cheers
Perhaps the Crosswalk project is something you can try. It uses a dedicated CEF runtime:
currently I'm in the stage where I'll be integrating GameCenter into my games.
I saw these 2 authentication methods in the documentation
authenticateHandler
authenticateWithCompletionHandler: (Deprecated in iOS 6.0)
My question is, which one should I use?
Because my games will be supported by the minimum iOS which is 4.3 and up until 6.0
If I use authenticateWithCompletionHandler: , it says will be deprecated in iOS 6.0
If I use authenticateHandler property, I wonder does iOS 4.x and 5.x able to run it?
Hope someone can explain to me, I'm confused by the compatibility now :(
Usually it is safe to use deprecated methods if you want to support older devices or iOS versions. It does not mean that the function is removed anytime soon... It's just a hint that a better or newer version of the function is available.
If the new function offers something the old don't, you could check if the function is available at runtime (respondsToSelector) and if not use the old one.
for a desktop application I am developing, I have to stick with a 32-bit framework. I am looking for the best path to run the framework in its proper process and develop the rest of the application in a 64-bit process. The application is also meant to be sold in the AppStore, so it should support Apple sandboxing.
I am thinking about XPC: is it suitable for these purposes? Why can't I find it in the Apple documentation related to cross-architecture programming?
XPC: is it suitable for these purposes?
Yes, XPC should work correctly between 32-bit and 64-bit processes.
Why can't I find it in the Apple documentation related to cross-architecture programming?
Because XPC is new in 10.7, and that 64-bit Transition Guide document is rather old and hasn't been updated since 10.6. Apple is not always good at updating older documentation.
I'm in the mood for developing a custom plug-in for Apple's default OS X mail client under OS X Lion (10.7). I can find a lot of plug-ins for older versions of Mail.app online, and some background information on the (officially unsupported and undocumented) plug-in architecture used by these old versions of Mail, but not for the newest version.
I know there are plug-ins for Lion's mail app so I know it's possible to do this, but I'm having a hard time finding out how to begin. Xcode offers templates for Address Book, Quartz Composer and Installer plug-ins, but not for Mail plug-ins.
I specifically do not want to work exclusively with AppleScripts because they won't allow me to do what I want to do: customize the application's interface, views and toolbars and such.
I am an experienced Objective-C developer and have built several apps for iOS, so the language and Xcode will pose no problems.
I think I just need to know 1) where/how to begin and 2) how to find reliable information about Mail.app's plug-in architecture. Can anybody point me in the direction of documentation, example projects or tutorials for developing such plug-ins? Of course, any other remarks, hints and tips are very welcome.
Thanks in advance!
There is at least one plugin for Mail.app which works on Lion. It's Growl Mail, plugin to connect Mail.app to Growl. Growl Mail has sources available on code.google, so, in my opinion, it's good point for start.
Oh, I almost forgot about second plugin, which I use, TruePreview. It has also sources available in internet.
I found these resources to be helpful.
http://www.tikouka.net/mailapp/ - repository of Mail plugins, at least some of which are open source so they can serve as examples (most support Mountain Lion).
http://www.hawkwings.net/ - Tips and add-ons for Apple Mail