Re: ObjC 3D engine
Re: ObjC 3D engine
- Subject: Re: ObjC 3D engine
- From: Half Activist <email@hidden>
- Date: Mon, 25 Jun 2007 08:56:02 +0200
who would actually like a cocoa 3D engine,
Cocoa/GNUStep developers dissatisfied of existing C++ engines.
or does core animation do everything you want
I believe Core Animation is not a 3D engine, it's only for animations.
eg: I don't think Core Animation handles collisions.
Also, considering Physics engines are becoming an essential part of
many 3D games, a 3D engine should be capable
to be connected to a physics engine, if all your 3D objects are
objective-c and the physics engine's ones are C++,
this might be a problem. Or am i defintly wrong?
Regards.
On Jun 24, 2007, at 2:51 AM, Jonathan deWerd wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
About a year ago I was looking for a good open-source objc/cocoa 3D
engine. After several days of searching, the best I could find were
a few outdated and/or abandoned frameworks (note: I could just
suck at searching, so if you are working on one don't take
offense). I decided that it would be a huge learning experience to
write my own, so I did. Or, to be more accurate, I hacked together
a bunch of classes which suited my needs. In any case, I now have
about 15k lines of cocoa 3D code that I want to put to some use. I
will say again that I *do not* have anything resembling any of the
mature C++ engines out there. I just have a start, if that. But I
would like to get some of your thoughts.
1) Is it worth turning this into an open source project at all (who
would actually like a cocoa 3D engine, or does core animation do
everything you want)?
2) Who would be willing to work on it with me?
3) If it is worth turning into a project, how much should I clean
my codebase before opening it up? Going through and presenting a
unified interface, documentation, and convention set would be
essential, but a lot of work. Should I do this before opening the
project to avoid scaring devs away or would it be best to "harness
the power of open source" and do it after? For that matter, should
I get it to a working "alpha" stage on my own?
4) What should I go with as far as SCM/forums/website are
concerned? Personally I really, really love git for SCM (seriously,
check it out. It blows svn out of the water in just about every
area, and it's really easy to compile. Just one dependancy, which
is itself a clean build on a default dev install of OSX). Should I
give up all the git goodness to conform? Should I use sourceforge,
host the dev stuff myself (then look for a better webserver when
approaching production), or do something else?
And I think that's all I can think of for now. Please tell me what
you think :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFGfamdJFLIvUXTZHsRAhz7AJ92ZQ4wBAQxJXQFiAXtkkafCLShhgCfcdKy
C09h/YZdcwVVgb7MQdJMDZg=
=WE+s
-----END PGP SIGNATURE-----
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden