They are not crippled until your change. You cannot double-click launch a non app bundle which makes bundless is crippled. Most Mac users will be confused or assume osg programs can't be double-clicked to launch. This is not good.
And being on par isn't enough. A universally poor, but consistent user experience is not what it is about. This is the Java GUI affect. It works the same on all platforms, but very few users are impressed. This is arguing the wrong thing. Users need to learn both. They need to understand OSG, but they also need to understand the platform they develop for. When users look to the examples, they are looking at both the osg code, but also how it is put together for their platform. When there were Visual Studio projects, Xcode projects, and Makefiles, users would not only look at the source code, but they would also try to understand how to build the applications by looking at the projects. Improperly building a project would be a disservice to the user and ultimately a poor reflection on OSG itself. Now people are going to look at our CMake system and are going to draw the wrong conclusions. At the very least, the default option needs to be for an .app bundle. User experience and first impressions are important. Users have an unconscious expectation of how a program should run on their platform. When they run the application for the first time, the experience should be positive. You want the person to say, 'Wow, OSG is great and has a good understanding of what it does and also how to make it work on my platform. They must know what they are doing. I want to use it.'. You don't want them to say, 'Gee, this really sucks. They don't understand my platform at all so they probably didn't do many other things right.' and move on to something else. It might not be true or fair, but this is how people make judgments. _______________________________________________ osg-users mailing list osg-users@openscenegraph.net http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/