I mostly program in postscript, which I use for a general purpose
language and MIDI parsing. From time to time I make a little coca app
when I need to do interactive views or real world interaction.
I have a working app that I wrote under 10.5 that makes a little
framework, where I can parse
I started playing with OS X storyboards a few weeks ago. It took more time than
it should to figure them out because the documentation is inadequate, but
Google searches led me to lots of helpful third-party articles. At this point,
they are working well for me. I think they are better than
On Mar 2, 2016, at 10:00 , Daryle Walker wrote:
>
> If this is a policy change …
Yes and no.
With state restoration enabled (the default), the application re-launches to
the same state as when it terminated. If there was no untitled window at quit,
there’s none when it
On Mar 2, 2016, at 12:00 PM, Daryle Walker wrote:
>
> The Apple-Event handling guide says that “-applicationOpenUntitledFile:” (at
> least on OS X 10.4) is supposed to be called on app-open. That didn’t happen
> when creating a default project on Xcode 7 using Swift and
The Apple-Event handling guide says that “-applicationOpenUntitledFile:” (at
least on OS X 10.4) is supposed to be called on app-open. That didn’t happen
when creating a default project on Xcode 7 using Swift and without documents
nor Core Data. I made a “newDocument:” action handler and a
> On Mar 1, 2016, at 8:20 AM, Jerry Krinock wrote:
>
> If:
>
> • Your primary experience is in OS X>
> • You know nibs.
> • Your purpose is to ship OS X apps, not broaden your horizons.
>
> Is there any reason to learn and use storyboards?
No.
I tried Mac storyboards a while