I've read a few posts and I'm a bit fuzzy on the subject. I have an OSG app wrapped up in a C++ library. Now I need a UI. I can attach this and drive this libarary from a console app, MFC GUI, or even the standard Windows API, etc. - All in C++. However, I'm considering using C#. I've heard lots of good things about C# from a UI development perspective. From an OSG/C# point of view - there seems to be lots of pain.
I'm not a C# developer - it's all Greek to me - so what I'm imagining may not be practical in reality hence this post. Is it possible to link in my OSG app wrapped up in a C++ blanket and use my own API from with a C# GUI? Is it painful? What would I lose by going this route? Is possible that at some point I won't be able to take advantage of some latest OSG feature due to some unforeseen incapability? My current UIs (I'm thinking of one MFC UI in particular) don't really interact with the OSG - that's all handled by my own C++ API. I'm just not sure how well all this would glue together using C#. Can some of the veterans comment? _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
