On 6/4/07, E. Wing <[EMAIL PROTECTED]> wrote:
This is how the platform is. It's really not up for discussion. Regardless if agree or disagree with you, it's not up to me. Yes, it's annoying for first time newcomers, but fortunately Mac developers are very aware of this issue and they will always share this information with people. And we have been building/shipping .app bundles for several years now for OSG since the inception of the Xcode projects (and even with the Project Builder projects that Jeremy Bell and I did way back), so this is no new mystery even within the OSG community. Furthermore, bundling is a critical component of OS X, so much in fact that I dedicated an entire 20 minute Quicktime video for OSG focused on the single topic of bundling. And command line options do work with the .app bundle so they can be run so it's not like functionality has been lost.
So let get this straight. The bundling of the examples was already crippling most OSG examples and making them unusable under OSX was acceptable. This is no way shape or form is acceptable, its lunacy. I am appalled that the OSG examples have been so crippled under OSX, I always assumed that things would actually be better supported, not worse. I will not accept this, even if you think current OSX users have grown used to this status quo, it doesn't pain the situation any different.
Please remove the new CMake option.
NO, it stays. I will not cripple OSX examples.
This is something I would have added myself if I thought it was safe and reasonable. (The whole CMake bundle option was implemented because of all the problems bundless apps were causing.) But trust me when I say this will only cause more problems and tech support/mailing list issues/problems/confusion down the line. The hack may work today, but it may break with the next system update or next OS release or maybe if/when we move to GraphicsWindowCocoa. I know you don't want to waste time dealing with this problem especially with your RSI and neither do I. The immutable reminder that you need a .app bundle on Mac is a good reminder and an important lesson to learn for newcomers to the system. I usually defer to your decisions (like the nested api header thing which I'm still working on), but in this case, I really need you to trust my judgement/expertise as a Mac expert on this one and I beg you to respect my wishes on this one seemingly small (but unfortunately, it isn't) topic. We're the ones who actually use the system.
Sorry Eric, the bundless examples *are* now all working, and working far better than then were when they were bundled there really isn't any competition. The OSG has supported almost all examples since it was first ported to OSX. Its only now it turns out that the Xcode projects crippled most of the examples. The change we've made today brings back alive all those broken examples. The new build relies on standard unix facilities that work just fine and aren't going to break unless Apple do something really really dumb. Please remember the OSG is an SDK for developers, its can and should work seamlessly across all platforms. This includes the fact that almost all examples should work, and work in the same way across all platforms, there really is no excuse to not deliver this. You can't do this with bundles. The option for building bundles is still there, no functionality has been lost, but we've gained functionality, and we've gained consistency with other platforms. This is a good thing, today was a good day for the OSG, OSX support was off track and not standing shoulder to shoulder with other platforms, now it is. Robert. _______________________________________________ osg-users mailing list osg-users@openscenegraph.net http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
