需要升级公司应用程序中的图形工具包的行动计划
我的工作是将我们所有使用 OpenSceneGraph（一个 openGl 工具包）版本 0.9.9 的应用程序升级到最新最好的 2.8。这项任务有很多注意事项：
1.) 在 .9.9 版本之后，对核心 OpenSceneGraph (OSG) 进行了重大修改。添加和删除了常用的函数和类。简而言之，我不能只是用新的替换旧的并修改一些已弃用或删除的功能 - 还有很多需要更改。
2.) 我们的应用程序是使用 Visual Studio 2003 中的 MFC 构建的。他们希望我继续使用它进行升级。
3.) 对于我的 OSG 特定场景来说，组织良好的文档似乎不可能找到，充其量也是无组织且分散的。
我的问题是：解决这个问题的详细方法是什么？我有大约两周的时间来升级其中一个应用程序。然后计划遵循此方法并将其应用于其余应用程序。对我来说，最大的障碍是找到起点。在我从事的大多数项目中，我可以轻松地直接深入挖掘并通过手头的一些组织和计划来解决它。这似乎是一个更复杂的问题，需要更准确和精确的行动计划。非常感谢您的想法和建议。
My job is to upgrade all of our applications that use OpenSceneGraph (an openGl toolkit) version 0.9.9 to the latest and greatest 2.8. Well quite a few caveats come with this task:
1.) After version .9.9 there was a major overhaul the the core OpenSceneGraph (OSG). Commonly used functions and classes were added and removed. Simply put, I can't just replace the old with the new and modify a few deprecated or removed functions - there is a lot that needs to be changed.
2.) Our applications were built using MFC in Visual Studio 2003. They want me to stick with using that for the upgrade.
3.) Good organized documentation for my particular scenerio for OSG seems impossible to find and unorganized and scattered at best.
My question is: What would be a somewhat detailed methodical approach for tackling this problem. I've got about two weeks to upgrade one of the applications. The plan is then to follow and apply this approach for the rest of the applications. For me, the biggest hurdle is finding a starting point. On most projects I work on, I can easily just dig right in and figure it out with a little organization and plan at hand. This seems like a bit more convoluted problem, with a more accurate and precise plan of action needed. Your ideas and suggestions are much appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在我看来，你应该将你的osg升级到新版本并尝试再次构建它，直到没有异常为止。
对于每个不容易解决的异常，您可以向osg-mailing list 询问。
您还可以询问您当前版本和最新版本的主要变化是什么。
In my opinion, you should upgrade your osg to new version and try to build it again until you get no exception.
for every exception which is not solved easily, you can ask to osg-mailing list.
you can also ask what are the major changes with your current version and latest version.