Based on the listing, I’d guess UWP.
Saagar Jha
> On Nov 19, 2019, at 21:18, Richard Charles via Cocoa-dev
> wrote:
>
>> On Nov 13, 2019, at 11:58 AM, Richard Charles wrote:
>>
>> Apple released iTunes for Windows in October 2003.
>>
>
>
> Apple just posted a job opening for a Senior Soft
> On Nov 13, 2019, at 11:58 AM, Richard Charles wrote:
>
> Apple released iTunes for Windows in October 2003.
>
Apple just posted a job opening for a Senior Software Engineer- Windows Media
Apps. It would be interesting to know how they plan on porting the new macOS
media apps to Windows and
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 he
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 arg
> 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 ha
> It’s better for Apple as a company, but personally, I’d rather be able
to upgrade my devices.
It's also extremely bad for the environment.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments
> On Nov 13, 2019, at 6:28 PM, Turtle Creek Software via Cocoa-dev
> wrote:
>
> Convert resources from ResEdit
DUDE. This is what, 20 years overdue?
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or mod
> On Nov 13, 2019, at 2:43 PM, Gabriel Zachmann via Cocoa-dev
> wrote:
>
>
>> be a good time for a SwiftUI pivot. If true, Cocoa is the new Carbon.
>>
>
> I think, eventually, maybe in 5 years' time, that will be the case.
> This is really just a guess, I have no insights into Apple's roadm
You made a business decision and now you must live with that decision.
Otherwise, this thread is really getting tiresome.
> On Nov 13, 2019, at 4:28 PM, Turtle Creek Software via Cocoa-dev
> wrote:
>
> blah blah blah
___
Cocoa-dev mailing list (
Our app is used by remodelers and construction folks to run their
businesses- accounting, estimating, project management, billing, payroll.
It's big- kinda like FileMaker, plus QuickBooks, plus a bit of Excel, plus
a drawing window for customizing. It took about 15 programmer-years for
version 1.0,
> On Nov 13, 2019, at 10:58 AM, Richard Charles via Cocoa-dev
> wrote:
>
> Over the last 16 years would bet that a lot of spit and polish has gone into
> integrating Cocoa with Windows by the iTunes team.
They only integrated the iTunes app with Windows. Getting a single app working
does no
Saagar Jha
> On Nov 13, 2019, at 12:43, Gabriel Zachmann via Cocoa-dev
> wrote:
>
>
>> be a good time for a SwiftUI pivot. If true, Cocoa is the new Carbon.
>>
>
> I think, eventually, maybe in 5 years' time, that will be the case.
> This is really just a guess, I have no insights into Appl
> On 13 Nov 2019, at 19:31, Turtle Creek Software via Cocoa-dev
> wrote:
>
> I made a rather bold statement about Cocoa being doomed. Here's some
> background on where it came from.
>
> Apple and Microsoft are both working on next-generation app development
> platforms, with the goal of havi
> be a good time for a SwiftUI pivot. If true, Cocoa is the new Carbon.
>
I think, eventually, maybe in 5 years' time, that will be the case.
This is really just a guess, I have no insights into Apple's roadmap.
Speaking of which: I have never been there myself, but wouldn't the apple
enginee
You know, I was thinking the same when Casey mentioned how long it was taking
to convert their app to Cocoa...
-Laurent.
--
> On Nov 13, 2019, at 14:38, Gary L. Wade via Cocoa-dev
> wrote:
>
> If it takes you that long, then you need to hire new developers rather than
> wasting your time po
If it takes you that long, then you need to hire new developers rather than
wasting your time posting complaints on an email list.
--
Gary L. Wade
http://www.garywade.com/
> On Nov 13, 2019, at 11:32 AM, Turtle Creek Software via Cocoa-dev
> wrote:
>
> We have to plan 5 or 10 years ahead, beca
I made a rather bold statement about Cocoa being doomed. Here's some
background on where it came from.
Apple and Microsoft are both working on next-generation app development
platforms, with the goal of having one dev library for desktop, tablet,
phone and anything else. Meanwhile, Mozilla also
> On Nov 13, 2019, at 8:47 AM, Glenn L. Austin via Cocoa-dev
> wrote:
>
> Having worked on an Apple cross-platform application that used the same APIs
> that iTunes use...
> ...was a nightmare.
>
> You'd think that it would be easy, but there are so many assumptions about
> *how* the
> On Nov 12, 2019, at 11:56 PM, Chris Ridd via Cocoa-dev
> wrote:
>
>>
>> On 12 Nov 2019, at 21:14, Jean-Daniel via Cocoa-dev
>> wrote:
>>
>>
>>
>>> Le 12 nov. 2019 à 21:30, Richard Charles via Cocoa-dev
>>> a écrit :
>>>
>>>
On Nov 12, 2019, at 1:16 PM, GNDGN wrote:
‘
> On 12 Nov 2019, at 21:14, Jean-Daniel via Cocoa-dev
> wrote:
>
>
>
>> Le 12 nov. 2019 à 21:30, Richard Charles via Cocoa-dev
>> a écrit :
>>
>>
>>> On Nov 12, 2019, at 1:16 PM, GNDGN wrote:
>>>
>>> ‘It’s like giving a glass of ice water to somebody in hell’ - Jobs
>>>
>>
>> Apple re
> On Nov 12, 2019, at 2:14 PM, Jean-Daniel via Cocoa-dev
> wrote:
>
> What would be the benefit for Apple to support public API for Windows ?
>
More applications available for the Mac.
Reduce the number of app developers abandoning the Mac platform.
Reduce the number of inferior electron
> Le 12 nov. 2019 à 21:30, Richard Charles via Cocoa-dev
> a écrit :
>
>
>> On Nov 12, 2019, at 1:16 PM, GNDGN wrote:
>>
>> ‘It’s like giving a glass of ice water to somebody in hell’ - Jobs
>>
>
> Apple released iTunes for Windows in October 2003. Apparently Cocoa and any
> supporting f
That is a cool discovery! It would be a game-changer for us, assuming
Apple also committed to long-term support for Cocoa and Objective-C. Life
would be so much sweeter if we only had to write apps once for all PCs. I'd
prefer to do it on Xcode rather than Visual Studio.
In 2001 we contracted the
>
> I'm not just joking here. Obj-C's dynamic nature is at the heart of a lot of
> Cocoa's powerful features like Interface Builder and KVO. Super-static
> languages like C++ don't work well for GUI development, IMHO, because they
> make it hard to compose high-level objects together.
I agre
Because they want us devs to stay in their own ecosystem .. which is a pretty
right move imo.
> Am 12.11.2019 um 21:30 schrieb Richard Charles :
>
>
>> On Nov 12, 2019, at 1:16 PM, GNDGN wrote:
>>
>> ‘It’s like giving a glass of ice water to somebody in hell’ - Jobs
>>
>
> Apple released
> On Nov 12, 2019, at 1:16 PM, GNDGN wrote:
>
> ‘It’s like giving a glass of ice water to somebody in hell’ - Jobs
>
Apple released iTunes for Windows in October 2003. Apparently Cocoa and any
supporting frameworks were ported to Windows 16 years ago. So what is the
problem providing this to
‘It’s like giving a glass of ice water to somebody in hell’ - Jobs
(;
> Am 12.11.2019 um 21:00 schrieb Richard Charles via Cocoa-dev
> :
>
>
>> On Nov 11, 2019, at 6:05 PM, Turtle Creek Software via Cocoa-dev
>> wrote:
>>
>> Unfortunately, software for any vertical or specialty market has
> On Nov 11, 2019, at 6:05 PM, Turtle Creek Software via Cocoa-dev
> wrote:
>
> Unfortunately, software for any vertical or specialty market has to deal with
> Mac market share.
>
I just downloaded iTunes 12.10.2.3 (64 bit) for Windows 10 Pro. It runs great,
looks great, no crashes. An ex
On Nov 11, 2019, at 17:05 , Turtle Creek Software via Cocoa-dev
wrote:
>
> I didn't mean to start a language war, because it's not about C++ vs
> Objective-C or Swift.
I’ve been staying out of this, because you’ve seemed impervious (in the last
few weeks since this topic has been discussed) to
On Mon, 11 Nov 2019 11:28:57 -0600, you wrote:
>> Thats more open than Obj-C, because Apple never open-sourced Foundation.
>
>AFAIK no Apple frameworks for Swift have been (or will be) open sourced
>either.
>
>> MSVC and .NET are both fully closed, as far as Im aware.
>
>.NET Core is fully open
I didn't mean to start a language war, because it's not about C++ vs
Objective-C or Swift. It's about whatever lets us create software that
runs on Macintosh and pays for the development cost. Right now, it only
makes sense to write an entire app in Objective-C or Swift if it's OK to
limit sales
> On Nov 11, 2019, at 10:46 AM, Turtle Creek Software
> wrote:
>
> That means no use of const. All pointers instead of & references. Both of
> those are good at turning run-time errors into compile-time. […] No
> public/private to manage access. Etc. It was like going back to the early
>
>
> Maybe I'm wrong, but we have experienced enough past pivots and
> bridge-burnings that another seems overdue.
>
Yes, I can understand that.
On the other hand, at least in the old days,
Microsoft kept all the old API's around for so many years
(for backwards compatibility),
including bug
If you wish to solve the problems you perceive to exist, you should join an
Objective-C/Objective-C++ email list or hire developers experienced in those
nuances.
--
Gary
> On Nov 11, 2019, at 10:47 AM, Turtle Creek Software via Cocoa-dev
> wrote:
>
>
>>
>>> Obj-C++ *is* a superset of C++,
>> Obj-C++ *is* a superset of C++, so I’m not sure what you’re wishing for.
In source files Obj-C++ works great. No complaints there. But headers and
method declarations are Obj-C, which is C plus its own additions.
That means no use of const. All pointers instead of & references. Both of
those
> On Nov 11, 2019, at 9:28 AM, Pier Bover wrote:
>
> AFAIK no Apple frameworks for Swift have been (or will be) open sourced
> either.
Not higher-level ones, but the Swift standard libraries include the equivalent
of most of Foundation. Which is a big deal, because the lack of an open-source
> That’s more open than Obj-C, because Apple never open-sourced Foundation.
AFAIK no Apple frameworks for Swift have been (or will be) open sourced
either.
> MSVC and .NET are both fully closed, as far as I’m aware.
.NET Core is fully open source:
https://github.com/dotnet/core
AFAIK Core is on
> On Nov 11, 2019, at 6:15 AM, Turtle Creek Software via Cocoa-dev
> wrote:
>
> Then suggest that Cocoa would work better if Obj-C were a
> superset of C++ rather than plain C. Objective-C++ all the way down, not
> just in source files.
Obj-C++ is a superset of C++, so I’m not sure what you’r
This is the last bit of post-mortem from our failure with Cocoa. Thanks for
the patience of everyone who just wants to give or get tech answers here.
I was originally going to post about how modern C++ has far surpassed
Objective-C. Then suggest that Cocoa would work better if Obj-C were a
superse
39 matches
Mail list logo
