le, for
example
Being able to do this would lead to an large increase in the number of
Macintosh applications available.
Bill Royds
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to
On 14-Jul-08, at 09:20 , Kyle Sluder wrote:
It would lead to a large increase in poorly-designed, auto-ported Mac
applications. And then developers would wonder why nobody wants to
purchase their software, even though the Windows version did so well.
Not necessarily. You are assuming that al
a failing of the Mac or its
market, rather than an acknowledgment that just possibly the app
itself was crap. Elitist as it may sound on first blush, the reality
is that software tends to be better when the developer is required
to think.
Software is also worse when the developer has
On 14-Jul-08, at 17:55 , Kyle Sluder wrote:
I suppose the question I should be asking you is, who is your
audience? What does your product do? Why do you want to
auto-generate your user interface in a serialized object graph form
from a textual template? That certainly wouldn't be my first c
ficulty.
I find that I use dot syntax for value (including property)
extraction, while bracket for message passing. That makes my code
easier to scan looking for calls versus value change.
Bill Royds
___
Cocoa-dev mailing list (Cocoa-dev@
On 10-Sep-08, at 04:59 , [EMAIL PROTECTED] wrote:
Anyway, if Mac software starts heading back down the road to
everything having an installer, the appeal of the Mac platform vs.
Windows will be severely diminished in my eyes. Drag and drop puts
the user in control - installers put the user
On 11-Sep-08, at 05:53 , [EMAIL PROTECTED] wrote:
From: Neil Brewitt <[EMAIL PROTECTED]>
Date: September 11, 2008 03:55:29 GMT-04:00
To: Cocoa Developers
Subject: Re: OT: Installing Apps
On 10 Sep 2008, at 20:41, Steven W Riggins wrote:
I for one, being a Mac user since Feb, 1984, am dismay
On 13-Sep-08, at 07:45 , Daniel Luis dos Santos wrote:
That said, STL can be used only within a library's own code. Then
when coding a shared library one must implement all kinds of data
structures that can be used at the boundary. Isn't that like
reinventing the wheel ?
Yes. But that is
