How to compile for macOS 10.11 ?

I have some code that works fine in macOS 10.14. The only warnings I get during compilation are related to the GUI (about clipping and constraints and the like). Now I would like to compile this for 10.11 (El Capitan). Problem is, I only have one Macbook running 10.14 In Xcode, I switched the

Re: Thoughts on Cocoa source code

> > Builders are mobile, and would love access to the accounting file in the > office. Those apps will each do just one thing (e.g. enter a purchase or > check an estimate). I know this is the Cocoa devs list... but why not make a website? It would be easier to develop, completely

Re: Thoughts on Cocoa source code

>> I know this is the Cocoa devs list... but why not make a website? >> It would be easier to develop, completely crossplatform, no app store complications, you would be in total control of your stack, etc. QuickBooks has gone that route. They still grudgingly sell desktop apps, but really push

Re: Thoughts on Cocoa source code

It does the useful thing on 10.15. I just had to add some scene code to our iOS app that had availability indicators around the methods indicating to use them on iOS 13 and greater. Sent from my iPhone > On Oct 9, 2019, at 1:39 PM, Aandi Inston via Cocoa-dev > wrote: > > " . Cocoa is part

Re: Thoughts on Cocoa source code

> On Oct 11, 2019, at 11:21 AM, Jens Alfke via Cocoa-dev > wrote: > > What you can do is give them feedback about your specific experience, as > you're doing, and I hope that someone at Apple is reading this thread and > taking notice. When creating a new project in Xcode one of the choices

Re: Thoughts on Cocoa

> On Oct 11, 2019, at 12:44 AM, Jens Alfke wrote: > > >> On Oct 10, 2019, at 6:18 PM, Richard Charles via Cocoa-dev >> wrote: >> >> Just a guess but perhaps management had an awakening when they found the >> time and effort expended to write the next even better version of Finder in >>

Re: Thoughts on Cocoa

There’s a (short, I think) chapter missing from this story. I attended a public (technical) talk in Town Hall (I think it’s called) at Apple shortly before or after I went to work there. It would have been around 2000-2001. The speaker’s message was that the future of the desktop was Java. A

Re: Thoughts on Cocoa source code

> Le 11 oct. 2019 à 16:59, Turtle Creek Software via Cocoa-dev > a écrit : > > I checked the GNUstep project, and it does seem decently clear and > well-commented. If Apple made it possible to see and step through some of > the basic Cocoa classes, that would be a good starting point. The

Re: Thoughts on Cocoa source code

After we finish the Windows update, the plan is to write small phone/pad apps that will talk to it. Builders are mobile, and would love access to the accounting file in the office. Those apps will each do just one thing (e.g. enter a purchase or check an estimate). Swift and the current Cocoa

Re: Thoughts on Cocoa source code

I’m one of the few on the list who has experienced every growing pain you’ve mentioned from 680x0 Macintosh now up to SwiftUI, and not only supporting a US English environment but even RTL UI (Arabic and Hebrew scripts) mixed with LTR languages across every current platform, and I will admit

Re: How to compile for macOS 10.11 ?

> On Oct 11, 2019, at 1:36 AM, Gabriel Zachmann via Cocoa-dev > wrote: > > But a customer tells me that it does not work under El Capitan on their > machine. > It displays the message "This screen saver requires OS X 10.14". If the alert is that specific, it sounds like your bundle has an

Re: Thoughts on Cocoa source code

Clarification: For long-time Mac and now available in SwiftUI, you can even write “no” code to do some things with bindings. -- Gary L. Wade http://www.garywade.com/ > On Oct 11, 2019, at 8:31 AM, Gary L. Wade > wrote: > > For Mac and SwiftUI, you can even write “no” code to do some things

Re: Thoughts on Cocoa source code

I checked the GNUstep project, and it does seem decently clear and well-commented. If Apple made it possible to see and step through some of the basic Cocoa classes, that would be a good starting point. The hard parts for us were NSView and its subclasses (especially NSTableView & associates,

Re: Thoughts on Cocoa source code

> On Oct 11, 2019, at 6:18 AM, Turtle Creek Software via Cocoa-dev > wrote: > > Our time is best > spent solving business-related problems. Along the way we have learned > many programming and human-interface skills, but the less time we need to > spend on that, the better. Totally

Re: Thoughts on Cocoa source code

> 2019. 10. 12. 오전 9:55, Richard Charles via Cocoa-dev > 작성: > >  >> On Oct 11, 2019, at 1:14 PM, Turtle Creek Software via Cocoa-dev >> wrote: >> I know this is the Cocoa devs list... but why not make a website? It would be easier to develop, completely crossplatform, no app

Re: Need for Swift

> On Oct 11, 2019, at 10:09 PM, Kirk Kerekes via Cocoa-dev > wrote: > > I would not want to be at the mercy of a vehicle piloted by C++. In the immortal words that I have in an email from John Carmack, “Failure in brakes.dll." ___ Cocoa-dev

Re: Thoughts on Cocoa source code

The hard thing to make work best with NSComboBox is what to have its data source return when a user enters something not available in the list, so there is that decision to make, especially if your list is very sparse. You could also just use a pop up button that allows both mouse selection and

Re: Need for Swift

> On Oct 11, 2019, at 8:10 PM, Kirk Kerekes via Cocoa-dev > wrote: > > I further infer that the perceived need arose due to the confluence of > aggravation over publicity over security bugs and the desire to develop > autonomous vehicle software. I don’t think so. Language people don’t

Re: Thoughts on Cocoa source code

> On Oct 11, 2019, at 12:22 PM, Richard Charles wrote: > > A second choice "Cross-platform Cocoa App" would be great for the small > developer who’s focus is on business applications. All whole world doesn’t > revolve around games. https://developer.apple.com/xcode/swiftui/

Re: Thoughts on Cocoa source code

> On Oct 11, 2019, at 1:14 PM, Turtle Creek Software via Cocoa-dev > wrote: > >>> I know this is the Cocoa devs list... but why not make a website? >>> It would be easier to develop, completely crossplatform, no app store >>> complications, you would be in total control of your stack, etc. >

Need for Swift

> On Oct 11, 2019, at 7:55 PM, cocoa-dev-requ...@lists.apple.com wrote: > > Me, I still don?t understand why, given the long history of support at > Apple/NeXT for C++ and the maturity of the compilers available, there is any > need for Swift. But there it is. It is my inference that Swift

Re: Thoughts on Cocoa source code

> On Oct 11, 2019, at 7:07 PM, 조성빈 wrote: > >> 2019. 10. 12. 오전 9:55, Richard Charles via Cocoa-dev >> 작성: >> >> None but the biggest of companies can do this. > > That’s not true, web apps aren’t really complex if you get to use the npm > ecosystem. There are high quality libraries that do

Re: Thoughts on Cocoa source code

> On Oct 11, 2019, at 4:46 PM, Jens Alfke wrote: > >> On Oct 11, 2019, at 12:22 PM, Richard Charles wrote: >> >> A second choice "Cross-platform Cocoa App" would be great for the small >> developer who’s focus is on business applications. All whole world doesn’t >> revolve around games. >

Re: Thoughts on Cocoa source code

>> If you combine otool, classdump and Hopper Disassembler, you can find how some Cocoa methods are working in any Obj-C executable pretty easily. Here's the thing. We started out as construction folks who learned Excel. Then HyperTalk. Then C++. As a business, our main strength is knowing the

Re: Thoughts on Cocoa source code

I’m sure much of the Cocoa code is quite old, but it’s mostly all Objective-C. If you’re curious how it might work, but don’t want to use a disassembler, the GNUstep project has a somewhat decent (though incomplete) reimplementation that you can look at.