 | | | Subject: Re: Thoughts on the Gabe Newell 's Mac comments. | Subject: Re: Thoughts on the Gabe Newell 's Mac comments. 2007-10-05 - By Errol Sayre
Back
> The only thing out of that list that I think would be of any use is
> CoreInput, the other
> things already exist, they simply aren't all prepended with a
> word.. Do we really need
> a word stuck on the front of everything?
I don't think the naming/branding is really the issue, I think it's
simply more a point that Apple really kinda leaves things up in the
air for developers to figure out what they should use. Giving
everything a common name doesn't really address that. Looking at the
Apple games dev site, there's no high level introduction/overview to
give folks a notion of where to start.
Perhaps a "CoreGames" library could simply be a wrapper for all the
existing things, but I'd think it more important to develop an
overview of what folks need to build games, and then fill in the holes.
For instance, if you can come to the point where you've nailed down:
OpenGL for 3D
OpenAL or CoreAudio for sound
Quartz + CoreImage + CoreAnimation? for 2D
OpenPlay? + Sockets + Bonjour for networking
QuickTime + CoreVideo for movies
IOKit + HID Utilities + Force Feedback Framework for input
and try to write a guide for new Mac game developers, you'll probably
come to see the holes fall in networking and input... and then need
to write either a complex set of workaround instructions to teach how
to address these as the developer or simply fill in the holes with
some actual APIs.
The Games section of the Apple site seems fairly neglected,
especially when compared to the plethora of examples/writeups/etc for
CoreData applications and the other "Core" libraries...
<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line
-break: after-white-space; "><DIV><BLOCKQUOTE type="cite"><DIV style="margin-top
: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The only thing
out of that list that I think would be of any use is CoreInput, the other</DIV>
<DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left:
0px; ">things already exist, they simply aren't all prepended with a word.. Do
we really need</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin
-bottom: 0px; margin-left: 0px; ">a word stuck on the front of everything?</DIV>
</BLOCKQUOTE><BR></DIV><DIV><SPAN class="Apple-style-span">I don't think the
naming/branding is really the issue, I think it's simply more a point that
Apple really kinda leaves things up in the air for developers to figure out
what they <I>should</I>?use. Giving everything a common name doesn't really
address that. Looking at the Apple games dev site, there's no high level
introduction/overview to give folks a notion of where to start.</SPAN></DIV>
<DIV><BR class="khtml-block-placeholder"></DIV><DIV>Perhaps a "CoreGames"
library could simply be a wrapper for all the existing things, but I'd think it
more important to develop an overview of what folks need to build games, and
then fill in the holes.</DIV><DIV><BR class="khtml-block-placeholder"></DIV>
<DIV>For instance, if you can come to the point where you've nailed down:</DIV>
<DIV><SPAN class="Apple-tab-span" style="white-space:pre"> </SPAN>OpenGL for 3D<
/DIV><DIV><SPAN class="Apple-tab-span" style="white-space:pre"> </SPAN>OpenAL or
CoreAudio for sound</DIV><DIV><SPAN class="Apple-tab-span" style="white-space
:pre"> </SPAN>Quartz + CoreImage + CoreAnimation? for 2D</DIV><DIV><SPAN class=
"Apple-tab-span" style="white-space:pre"> </SPAN>OpenPlay? +?Sockets + Bonjour
for networking</DIV><DIV><SPAN class="Apple-tab-span" style="white-space:pre">
</SPAN>QuickTime + CoreVideo for movies</DIV><DIV><SPAN class="Apple-tab-span"
style="white-space:pre"> </SPAN>IOKit + HID Utilities +?Force Feedback
Framework for input</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV
>and try to write a guide for new Mac game developers, you'll probably come to
see the holes fall in networking and input... and then need to write either a
complex set of workaround instructions to teach how to address these as the
developer or simply fill in the holes with some actual APIs.</DIV><DIV><BR
class="khtml-block-placeholder"></DIV><DIV>The Games section of the Apple site
seems fairly neglected, especially when compared to the plethora of examples
/writeups/etc for CoreData applications and the other "Core" libraries...</DIV><
/BODY></HTML>
__ ____ ____ ____ ____ ____ ____ ____ ____ ____
Do not post admin requests to the list. They will be ignored.
Mac-games-dev mailing list (Mac-games-dev@(protected))
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/mac-games-dev/junlu%405341.com
This email sent to junlu@(protected)
|
|
|