Hi Eric,
On 6/4/07, Eric Sokolowsky <[EMAIL PROTECTED]> wrote:
> I don't think running things using
> ./osganimate,app/Contents/MacOS/osganimate is any way acceptable
> though, users who work on other platforms will expect the examples to
> all build and run like on any other platforms, its seems crazy that
> OSX should be so different. For instance try running the
> runexamples.bat with the .app approach...
Like it or not, OS/X *is* different. An overbroad generalization is that
the Mac makes application development more difficult in order to
simplify the end user's experience.
Well actually OSX isn't actually that different, its Unix under the
hood. What is different is Apples layer on top of this.
Here lies the crux of the matter. What is the intended audience of the
example programs for OS/X users? Is the audience an OSG user that
happens to use a Mac, or is it a Mac user that want to learn OSG? If the
former, then forcing them to use the command-line is acceptable. If the
latter, then forcing them to use the command-line is unacceptable. I
suspect that the latter community is 100+ times larger than the former.
The audience of all OSG examples and applications is purely
developers, they serve no beyond help OSG users get to grips with how
to use the API, and to test it. The OSG is an SDK, its not an end
user application, this is the way it always will be.
Apps written on top of the OSG are a different topic though, these can
be distributed in any way the app develop finds appropriate, the OSG's
role here is really just to keep out of the way, and enable people to
release things how they want.
Robert.
Robert.
_______________________________________________
osg-users mailing list
osg-users@openscenegraph.net
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
