WAT? Now this is something else! practicalswift.com
I learned about a package manager for Xcode named Alcatraz when I attended CocoaConf in San Jose earlier this year. Extending the functionality of Xcode through plugins has been something I've been looking into for a while and the only plugins I knew about in the wild could only be found through Google searches or on NSHipster.com The tool makes it much easier to find plugins for Xcode. Buuuut, it actually also serves up themes, templates and more, all from a menu available within Xcode. Installation is also simple. Type in a single Terminal command and hooorah, it's installed:
curl -fsSL https://raw.github.com/supermarin/Alcatraz/master/Scripts/install.sh | shOh, and if you are looking to attend an Apple developer conference, you should definitely consider CocoaConf: the attendee group is primarily developers, attendees and speakers are easy to approach and exchange ideas with, and as they had advertised on CocoaConf's site, the food is good.
You know, I was getting quite comfortable with Obj-C, C++11, and everything else I had learned over the years... now Apple has to go and introduce another language: Swift I don't know what to make of it. How much better can it be than Obj-C? I guess I'll find out over the course of the year. I do have to say though, that "let" and "var" are pretty cool, in the same way that "auto" is pretty cool in C++11. Oh, and if you haven't already read Herb Sutter's article on why you should use "auto" in your code, check it out here: AAA
Ugh! I've been running into problems with my Jenkins scripts that would fail when attempting to run my p4 commands, because the three periods I inserted into the p4 command were automatically converted to an ellipsis by MacOSX, which is not a good thing: Three dots are automatically changed to an ellipsis
So, if you need a good program to show you where your disk space is being used, in Windows, check out Space Sniffer
In a previous post, Perforce and Xcode4, I created applescripts to work with Xcode4 and Perforce. I updated the AppleScripts to work with Xcode5 only and added a couple of new scripts. One, called p4_file_renamed.scpt, is used to update the renamed file Perforce when you are using Xcodes rename functionality, either directly or through the refactor functionality. The other two scripts get the filename of the currently selected file or the full path of the file which is useful for when you want to find a file by path in P4V. You can download the file here: xcode5_p4_applescripts
Ok, so if you want to avoid a file from being analyzed during a static analysis, you can use the following example
#ifndef __clang_analyzer__ // code clang should not analyze #endifhttp://clang-analyzer.llvm.org/faq.html
I created some AppleScripts that allow you to control some basic Perforce functionality in Xcode4, which was lost when Apple released the latest version of their IDE. Perforce actually published a way of checking out files using the Behaviors functionality in Xcode (Xcode and P4), but I wanted a little more. Note, these scripts are a work in progress. If you happen to make improvements, let me know so that those changes can be shared with the community. You can download the AppleScripts here: xcode_p4_applescripts Update The AppleScript files are also being hosted on the public Perforce swarm forum, located here: Perforce Public Swarm Server Update 2013-11-06 I updated the AppleScripts to work with Xcode5 only and added a couple of new scripts. The new applescript files are referenced in post Perforce and Xcode5
On a multi-core Mac, running 10.8, I ran a test to compare the speed differences of incrementing or decrementing a value with no-locks, atomics and finally, a mutex lock. The no-lock is the baseline, and here is the difference in speed with the later 2 items: Atomics: 3X slower on the same thread Mutex: 7X slower on the same thread Hmmm...
I actually automate Instruments to get finer grain information of what an application is actually doing. To automated Instruments, according to Apple's documentation, all you need is the DTPerformanceSession.framework... but, you actually need more than that, and you have to find where the dependencies are located. Here are all of the libraries you need: DTInstrumentsCP.framework DTMessageQueueing.framework DTPerformanceSession.framework DTXConnectionServices.framework InstrumentsSupport.framework And here is where they are located: /Applications/Xcode.app/Contents/Applications/Instruments.app/Contents/Frameworks/DTInstrumentsCP.framework /Applications/Xcode.app/Contents/SharedFrameworks/DTMessageQueueing.framework /Applications/Xcode.app/Contents/Developer/Library/Frameworks/DTPerformanceSession.framework /Applications/Xcode.app/Contents/SharedFrameworks/DTXConnectionServices.framework /Applications/Xcode.app/Contents/Applications/Instruments.app/Contents/Frameworks/InstrumentsSupport.framework