Re: Another Xcode update, another failure to build.

> On 13 Aug 2015, at 11:37, Graham Cox wrote: > But the linker fails to find the framework: > > ld: warning: directory not found for option > '-F"/Users/grahamcox/Projects/Mapdiva > Projects/Artboard/../../Library/Developer/Xcode/DerivedData/Drawkit-gzweppsofrkdiyasaleyeleblyor/Build/Products

Re: Mavericks vs Yosemite line spacing

Control of vertical alignment is something Cocoa devs have wanted for years. Usually what you end up doing is subclassing NSTextFieldCell to customise the layout/drawing, such that text appears at the desired point. > On 13 Aug 2015, at 00:56, Trygve Inda wrote: > > I have an NSTextField that

What version of OpenGL bundled in El Capitan?

I've been googling all over the place. The only references I find are the ones that say Metal is going to replace OpenGL. But I know that OpenGL is still bundled. I haven't got around to install El Capitan on my system (I only have one and I use it for production, having been burnt in the past, I p

Re: Initialisation pattern

> On Aug 12, 2015, at 8:07 PM, André Francisco > wrote: > > Hi all, > I've been reading about object initialisation in Objective-c, as well as the > recent additions of NS_UNAVAILABLE and NS_DESIGNATED_INITIALIZER. It's been > confusing what the correct approach would be, mostly due to limit

Xcode 7b5 Swift Strings

Between b4 and b5, Apple has changed some NSString methods in Swift. I used to be able to do this: let s : String = ... let s2 = s.stringByExpandingTildeInPath.stringByAppendingPathComponent("foo") Now I have to write: let s2 = ((s as NSString).stringByExpandingTildeInPath as NSString).stringB

Re: Xcode 7b5 Swift Strings

On Aug 13, 2015, at 12:56 , Rick Mann wrote: > > Now I have to write: > > let s2 = ((s as NSString).stringByExpandingTildeInPath as > NSString).stringByAppendingPathComponent("foo") > > How is this better? What happened is that the methods in NSPathUtilities.h are no longer available to the

Re: Xcode 7b5 Swift Strings

> On Aug 13, 2015, at 13:08 , Quincey Morris > wrote: > > On Aug 13, 2015, at 12:56 , Rick Mann wrote: >> >> Now I have to write: >> >> let s2 = ((s as NSString).stringByExpandingTildeInPath as >> NSString).stringByAppendingPathComponent("foo") >> >> How is this better? > > What happened

RE: Initialisation pattern

I only got Seth's email on the digest, not really sure why. Anyway, I copy pasted his response below.@Seth, thank for your answer. That's exactly what I've been doing all along, I didn't mention it because that's precisely what I'm trying to change. The problem is that it's not fine, I just test

Swift differences between projects?

I have two projects open in Xcode 7b5. One is mine, which chokes on the latest changes around NSString path methods. The file that chokes is from the Swifter HTTP server Github project. The other project is the one that comes with the Swifter project itself. Here's the thing: it compiles just f

Re: Initialisation pattern

> On Aug 13, 2015, at 1:32 PM, André Francisco > wrote: > > I only got Seth's email on the digest, not really sure why. Anyway, I copy > pasted his response below.@Seth, thank for your answer. That's exactly what > I've been doing all along, I didn't mention it because that's precisely what >

Re: Xcode 7b5 Swift Strings

> On Aug 13, 2015, at 3:08 PM, Quincey Morris > wrote: > > On Aug 13, 2015, at 12:56 , Rick Mann > wrote: >> >> Now I have to write: >> >> let s2 = ((s as NSString).stringByExpandingTildeInPath as >> NSString).stringByAppendingPathComponent("foo") >> >> How is

Tech update avoiding legacy code

Hi List, My Mac application starts running from 10.5 onwards. We are planning to adopt new technologies like GCD, Storyboards, ARC, Auto Layout and Swift. We have benefits to start using like App performance improvements, reducing memory leaks, reduce number of files and code size reduction...

Re: Tech update avoiding legacy code

Do you have a definite business need to keep supporting 10.5? I can’t believe you have many customers still running it — it came out in 2007 (the last release I worked on at Apple!) In terms of priorities, I think ARC is the biggest win, followed by GCD. Some people might rate auto-layout highe

Re: Tech update avoiding legacy code

We have limited people on 10.5, but revenue prospective we couldn¹t ignore them. Thanks for the priority order. In GDC Vs ARC, GCD is the first one to opt unless if you are app has more memory leaks. Correct me If I am wrong. Not sure, different code base will workout in this case. Implementation