Re: Cocoa-dev Digest, Vol 16, Issue 144

>> >> Convert resources from ResEdit >> DUDE. This is what, 20 years overdue? Dude. Why would we change them before it was necessary? Don't fix it if it ain't broke. There were better things to work on in the past 20 years. We wrote code to go through each type of resource and convert them

Re: Cocoa-dev Digest, Vol 16, Issue 144

Not to create a conflict, but I like to think about it this way. I had to do it with my parents as they approached their elderly years and we have to do it whenever the next version of Swift and Xcode come out. A train is moving to a cliff. The cliff is far away but eventually, if you do

Re: Cocoa-dev Digest, Vol 16, Issue 144

>> The longer you wait, the closer the train is to the edge of the cliff. Correct. But what we have learned from many years with Apple is that some of those cliffs disappear before you get close, or they just turn into bumps. Waiting til 2014 rather than 2004 meant using much better versions of

Re: Cocoa-dev Digest, Vol 16, Issue 144

> On Nov 14, 2019, at 6:11 AM, Turtle Creek Software via Cocoa-dev > wrote: > > Convert resources from ResEdit >>> DUDE. This is what, 20 years overdue? > > Dude. Why would we change them before it was necessary? Don't fix it if > it ain't broke. There were better things to work on in

Re: Cocoa-dev Digest, Vol 16, Issue 144

Yes, we use derez for the Windows app (still running in MS DOS!) It flattens resources, but doesn't make them easy to parse or maintain. Casey McDermott TurtleSoft.com On Thu, Nov 14, 2019 at 10:02 AM Glenn L. Austin wrote: > > On Nov 14, 2019, at 6:11 AM, Turtle Creek Software via Cocoa-dev

Re: Cocoa-dev Digest, Vol 16, Issue 144

>> Here’s your free advice and prognostications: https://developer.apple.com/videos/wwdc2019/ https://developer.apple.com/develop/ Neither of those mention Cocoa at all, just SwiftUI. Only slight mention of Objective-C in a couple of video descriptions about Clang/LLVM and profiling. That does

Re: Cocoa-dev Digest, Vol 16, Issue 144

> I think this gets back to the transparency issue. If Apple were more open > about the future, it would be easier to know which cliffs are real. That is one of my major gripes with Apple. Not only as a dev but also as a end user. It's like riding a car in at night and only seeing what's

Re: Thoughts on Objective-C++

I must confess I’m pretty interested by all opinions since these threads started (27th of september I think). Working in the construction industry, as I am, it might help to get interested in this and maybe this list is not the ideal vehicle for this kind of discussions but nonetheless, all

Re: Cocoa-dev Digest, Vol 16, Issue 144

As a mostly silent member for years and years, I agree when the list goes off on a complaint tangent (and when it is flagged by moderators, which is rare but sometimes necessary), but I have found this Turtle Creek thread quite useful and agree with many points, particularly these later ones.

Re: Thoughts on Objective-C++

Last year or so, there was much discussion about Apple shutting down many of their lists (some did go away, but this one persists). An external solution was found, by some of those list members, although they have been extremely quiet in the last year+. Here's a message from Steve Mills (is

Re: Cocoa-dev Digest, Vol 16, Issue 144

> On Nov 14, 2019, at 8:29 AM, Turtle Creek Software via Cocoa-dev > wrote: > > I think this gets back to the transparency issue. If Apple were more open > about the future, it would be easier to know which cliffs are real. > Here’s your free advice and prognostications:

Re: other developer lists

>> Maybe another list for meta or post-mortem discussions could be created ? Reddit is a decent place for communities like this. You can have it in your feed, or view threads when you feel like it. Here is what is already applicable: r/apple (mostly consumers, 1.2 million members) r/cpp (C++

Re: Cocoa-dev Digest, Vol 16, Issue 144

> Either way, the chart you linked to kind of proves my point though. It shows that the majority of users are using the latest released OS after less than a year. 52% (in the case of peak Mojave adoption) is a very slight majority unlike in iOS where usually 80-90% of users are on the latest

Re: Cocoa-dev Digest, Vol 16, Issue 144

You seem to be overlooking the fact that many of these current and past years’ videos talk about Cocoa by referencing their constituent components like AppKit, MapKit, Collection View, etc. You would benefit greatly by sitting down and watching as many of these videos as possible. -- Gary L.

Re: Cocoa-dev Digest, Vol 16, Issue 144

Well I think the point is to go SwiftUI. Go where the puck is going. Develop for iPad Pro and use SwiftUI to gain MacOS too. I got to believe enough of your business logic is now separated enough from the UI. Regards, James Cicenia Founder James John Group, LLC (+1) 773-398-4649  

Re: Cocoa-dev Digest, Vol 16, Issue 144

Well about right in terms of timing if you start architecting / developing now. Meanwhile a iPad Pro is pretty sweet for the construction/architecture industry. > On Nov 14, 2019, at 2:30 PM, Pier Bover wrote: > > What if you want to support previous macOS versions older than Catalina? >

Re: Cocoa-dev Digest, Vol 16, Issue 144

> Well I think the point is to go SwiftUI What if you want to support previous macOS versions older than Catalina? I doubt the majority of users will update to Catalina for at least 1-2 years. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Re: Cocoa-dev Digest, Vol 16, Issue 144

> On Nov 14, 2019, at 1:13 PM, Pier Bover wrote: > > > I wouldn’t be so pessimistic about macOS or even iOS update rates. > > According to StatCounter Mojave never went above 52% or market share, which > means at its peak 48% of users were still on previous versions. > >

Re: Cocoa-dev Digest, Vol 16, Issue 144

I wouldn’t be so pessimistic about macOS or even iOS update rates. Its considerably quicker than you think. IMS, they announce upgrade rates during public earnings report conference calls typically to brag about how well a new OS is being received by the public over previous releases or

Re: Cocoa-dev Digest, Vol 16, Issue 144

> I wouldn’t be so pessimistic about macOS or even iOS update rates. According to StatCounter Mojave never went above 52% or market share, which means at its peak 48% of users were still on previous versions. https://gs.statcounter.com/macos-version-market-share/desktop/worldwide I think it

Re: other developer lists

>>> Maybe another list for meta or post-mortem discussions could be created ? I manage the apple-dev.groups.io site, which hosts a number of Apple developer lists including a Cocoa one. I'd be happy to create a list for these kinds of discussions, if we can come

Re: other developer lists

Another reason why there's really no harm -if not some truly topical good- in this kind of thread (even w/ some critiques/defenses) bubbling up here now and again... Thanks, all, -Matt > On Nov 14, 2019, at 5:25 PM, Jens Alfke via Cocoa-dev > wrote: > > Maybe another list for meta or

Re: Thoughts on Objective-C++

> Phil mentioned to me in about 1996, 1997 back at Macromedia that it was the > goal for Apple to turn computers into the equivalent o kitchen appliances. > You won’t upgrade your Maybe the metaphor was more referring to the ease-of-use or the market proliferation. The metaphors certainly