    
|
|
|
In his latest op-ed published January 14 in The Baltimore Sun, political science professor Thomas Schaller comments on the current state of today’s media, arguing the most popular stories are ones that feed off of emotion and feelings of moral superiority.
“In today’s media age, whether in the regular news or so-called reality television, the best stories are those for which viewers and listeners need almost zero information or background as a point of entry,” Schaller writes.
In his column titled “The outrage machine,” Schaller mentions certain programs and stories that tend to draw out emotion and feelings of superiority and cautions viewers: “all this tele-voyeurism coarsens the way we feel toward others. The mix of disgust, bemusement, horror or loathing generated from our couches can’t possibly make us more empathetic toward neighbors and compatriots.”
You can read the full op-ed in The Baltimore Sun here.
]]>|
|
Tim Finin, Computer Science and Electrical Engineering, has been appointed as a co-editor of the Viewpoints section of the Communications of the ACM, the monthly magazine of the Association for Computing Machinery.
Established in 1957, CACM is sent to all ACM members (currently over 100,000) and is considered “the leading print and online publication for the computing and information technology fields”. CACM’s Viewpoints section is publishes short articles expressing opinions and views that pertain to issues of broad interest to the computing community, covering a wide range of topics, including scientific, technical, educational and social. Each month a handful of articles are published from those contributed by a set of distinguished ACM columnists and submitted by ACM members and computing professionals.
]]>|
|
|
|
When working with Objective-C projects in Xcode, you will occasionally want to work with third party libraries. This can be a bit cumbersome as Xcode doesn’t have a clean solution. You can either link a static library, which involves setting up the header paths to point to the correct location, or you can download the source files from the library and include it in your project. Neither of these options are great, especially if you want to keep your libraries up to date.
CocoaPods is an Objective-C dependency manager and offers a great solution to this problem. If you are familiar with Ruby, this works much like a Ruby Gem. CocoaPods is built with Ruby and can be installed using the default Ruby on OS X. To understand how CocoaPods simplifies the process of including third party libraries, we’re going to create an Xcode project and add a few different libraries to it. Let’s start by installing CocoaPods:
$ sudo gem install cocoapods
When using the default Ruby install you have to use sudo when installing a gem (what the heck is sudo?). If you have the Ruby Version Manager, or RVM, installed you won’t have to use sudo and can just run:
$ gem install cocoapods
You now have CocoaPods installed on your system. To search for libraries you can run:
$ pod list
That shows you all libraries in the CocoaPods directory and that probably doesn’t help you very much, since there are, at the writing of this post, 3136 pods. You can also be more specific and search for individual pods. Running the following command searches for pods with ‘cup’ in the name and returns a pod called CupertinoYankee:
$ pod search cup
-> CupertinoYankee (1.0.0)
An NSDate Category With Locale-Aware Calculations for Beginning & End of Day, Week, Month, and Year.
pod 'CupertinoYankee', '~> 1.0.0'
- Homepage: https://github.com/mattt/CupertinoYankee
- Source: https://github.com/mattt/CupertinoYankee.git
- Versions: 1.0.0, 0.1.1, 0.1.0 [master repo]
Let’s create a simple Xcode project. We have all the files you’d expect in a new project.
I want to add the following libraries to the project: CupertinoYankee, GroundControl and AFNetworking. To do this, in the main Xcode project directory, create a file called Podfile and add the following:
platform :ios, '7.0'
pod 'CupertinoYankee', '~> 1.0.0'
pod 'GroundControl', '~> 2.0.0'
pod 'AFNetworking', '~> 2.0.3'
A Podfile is similar to a Gemfile. All we’re doing is specifying the platform and listing each dependency along with the version required. If you don’t know how to list the dependency, search for it on the CocoaPods website. When you find the library you are looking for, click the clipboard icon next to the library name to copy the necessary text. Then it’s as easy as running:
$ pod install
When you run this command CocoaPods creates a workspace, adds our current project to the workspace and adds all the pods we specified into a Pods project which it then statically links. Once the command executes it reminds you to use the workspace, instead of opening up our project directly.
[!] From now on use `SampleProject.xcworkspace`.
If we go ahead and open up our workspace, we can see the Pods project that was generated, along with the libraries and relevant source files.
In our project directory, you will notice a new Pods.xcconfig file that specifies the relevant header search paths automatically.
So let’s go ahead and use these libraries in our project. Navigate to theSampleViewController.m file and add import the following headers:
#import "AFNetworking.h"
#import "NSDate+CupertinoYankee.h"
#import "NSUserDefaults+GroundControl.h"
And that’s it! An easy and clean way to manage any dependencies in your Objective-C projects.
The post Managing Dependencies in Objective-C Projects appeared first on Treehouse Blog.
]]>When working with Objective-C projects in Xcode, you will occasionally want to work with third party libraries. This can be a bit cumbersome as Xcode doesn’t have a clean solution. You can either link a static library, which involves setting up the header paths to point to the correct location, or you can download the source files from the library and include it in your project. Neither of these options are great, especially if you want to keep your libraries up to date.
CocoaPods is an Objective-C dependency manager and offers a great solution to this problem. If you are familiar with Ruby, this works much like a Ruby Gem. CocoaPods is built with Ruby and can be installed using the default Ruby on OS X. To understand how CocoaPods simplifies the process of including third party libraries, we’re going to create an Xcode project and add a few different libraries to it. Let’s start by installing CocoaPods:
$ sudo gem install cocoapods
When using the default Ruby install you have to use sudo when installing a gem (what the heck is sudo?). If you have the Ruby Version Manager, or RVM, installed you won’t have to use sudo and can just run:
$ gem install cocoapods
You now have CocoaPods installed on your system. To search for libraries you can run:
$ pod list
That shows you all libraries in the CocoaPods directory and that probably doesn’t help you very much, since there are, at the writing of this post, 3136 pods. You can also be more specific and search for individual pods. Running the following command searches for pods with ‘cup’ in the name and returns a pod called CupertinoYankee:
$ pod search cup
-> CupertinoYankee (1.0.0)
An NSDate Category With Locale-Aware Calculations for Beginning & End of Day, Week, Month, and Year.
pod 'CupertinoYankee', '~> 1.0.0'
- Homepage: https://github.com/mattt/CupertinoYankee
- Source: https://github.com/mattt/CupertinoYankee.git
- Versions: 1.0.0, 0.1.1, 0.1.0 [master repo]
Let’s create a simple Xcode project. We have all the files you’d expect in a new project.
I want to add the following libraries to the project: CupertinoYankee, GroundControl and AFNetworking. To do this, in the main Xcode project directory, create a file called Podfile and add the following:
platform :ios, '7.0'
pod 'CupertinoYankee', '~> 1.0.0'
pod 'GroundControl', '~> 2.0.0'
pod 'AFNetworking', '~> 2.0.3'
A Podfile is similar to a Gemfile. All we’re doing is specifying the platform and listing each dependency along with the version required. If you don’t know how to list the dependency, search for it on the CocoaPods website. When you find the library you are looking for, click the clipboard icon next to the library name to copy the necessary text. Then it’s as easy as running:
$ pod install
When you run this command CocoaPods creates a workspace, adds our current project to the workspace and adds all the pods we specified into a Pods project which it then statically links. Once the command executes it reminds you to use the workspace, instead of opening up our project directly.
[!] From now on use `SampleProject.xcworkspace`.
If we go ahead and open up our workspace, we can see the Pods project that was generated, along with the libraries and relevant source files.
In our project directory, you will notice a new Pods.xcconfig file that specifies the relevant header search paths automatically.
So let’s go ahead and use these libraries in our project. Navigate to theSampleViewController.m file and add import the following headers:
#import "AFNetworking.h"
#import "NSDate+CupertinoYankee.h"
#import "NSUserDefaults+GroundControl.h"
And that’s it! An easy and clean way to manage any dependencies in your Objective-C projects.
The post Managing Dependencies in Objective-C Projects appeared first on Treehouse Blog.
]]>