> Le 10 oct. 2019 à 00:14, Jens Alfke via Cocoa-dev
> a écrit :
>
>
>
>> On Oct 9, 2019, at 11:39 AM, Aandi Inston wrote:
>>
>> * But for whatever reason, I'm using the Mac OS 10.14 SDK. So that will get
>> a compile-time warning.
>
> Only if you don't turn on -Werror, which I really, re
> On Oct 9, 2019, at 11:39 AM, Aandi Inston wrote:
>
> * But for whatever reason, I'm using the Mac OS 10.14 SDK. So that will get a
> compile-time warning.
Only if you don't turn on -Werror, which I really, really recommend everyone
do. Calling a method that a class isn't declared as implem
Nothing is statically linked. The version of the SDK you compile with is
embedded into your application and Cocoa (and other Apple frameworks) consult
this at runtime to determine appropriate behavior. Often this means you don’t
get the new behavior, but sometimes Apple will automatically “opt y
> On Oct 9, 2019, at 10:41 AM, Jens Alfke via Cocoa-dev
> wrote:
>
> You don't want to use the _implementation_ details! Those can and do change
> completely over time
There is a situation where I think it is fine to use the implementation
details, and that is to work around a problem in an
> On Oct 9, 2019, at 11:58 AM, Pier Bover wrote:
>
> For example Imagix is a company that does image transformation in the cloud
> and uses macs because of the high performance of CoreImage
> (https://photos.imgix.com/racking-mac-pros) It's still more cost effective
> for them to use expensi
" . Cocoa is part of the OS, and changes one very OS release. "
This reminds me of a question which pops up for me every few years in
development. I can't call to mind the last
specific details, but it will happen again.
Let's create an imaginary problem:
* Apple add a new class behaviour to Cocoa
> Perhaps Apple does not want to give away the Crown Jewels.
Indeed.
There is some stuff in there that AFAIK no one has been able to replicate.
For example Imagix is a company that does image transformation in the cloud
and uses macs because of the high performance of CoreImage (
https://photos.
> On Oct 9, 2019, at 11:19 AM, Turtle Creek Software via Cocoa-dev
> wrote:
>
> Why is Cocoa source code hidden?
Because Apple does not want to expose Cocoa source source. It is proprietary
software.
> Many of the frustrations we had with the 64-bit update attempt were caused
> by Cocoa's l
Saagar Jha
> On Oct 9, 2019, at 10:19, Turtle Creek Software via Cocoa-dev
> wrote:
>
> Why is Cocoa source code hidden?
>
> Many of the frustrations we had with the 64-bit update attempt were caused
> by Cocoa's lack of visible source. It was a "black box" that often required
> trial-and-err
> On Oct 9, 2019, at 10:19 AM, Turtle Creek Software via Cocoa-dev
> wrote:
>
> Why is Cocoa source code hidden?
So, take this as opinions of someone who worked at Apple, on [among other
things] Mac OS X apps from 2000-2007.
(a) It's part of Apple's crown jewels and seen as a competitive ad
> On 09 Oct 2019, at 1:19 pm, Turtle Creek Software via Cocoa-dev
> wrote:
>
> In fact, why isn't Cocoa open source? Apple open-sources Swift and the
> Darwin kernel. Surely the GUI can't be any riskier to expose to developers?
This is a business strategy question, not a Cocoa development ques
Why is Cocoa source code hidden?
Many of the frustrations we had with the 64-bit update attempt were caused
by Cocoa's lack of visible source. It was a "black box" that often required
trial-and-error to figure out. Yeah, the headers are visible, and Apple has
info online. But sometimes that was no
Just try it with the window code commented out.
In any case, where you do have your code with the window, I would expect that
you would make the window key and visible not manually adjust its layer and on
dismiss, simply resign.
Alex Zavatone
Sent from my iPhone
> On Sep 30, 2019, at 4:48 P
I'm by no means an expert but if I understand what you're trying to do, I think
the approach I would take is to make an extension on UIViewController:
extension UIViewController {
func notificationAlert(_ msg1: String, _ msg2: String) {
// create the UIAlertAlertController
//
14 matches
Mail list logo