在应用程序中实现 iPhone 应用程序
我有两个应用程序,我想通过将较小的应用程序引入主应用程序来合并它们,这样较小的应用程序不是最初从其应用程序代理实例化,而是通过主控制器的现有导航控制器推送。
但是原始开发人员对应用程序的结构和原始应用程序委托单例有各种依赖关系,这使得在不重新安排代码的情况下推送它的主视图控制器变得非常重要......这需要时间。
人们通常如何采用标准的可可项目并将其转变为其他现有应用程序的功能,同时保留保持事物良好解耦的能力?
XCode Project 1 - Does X features
XCode Project 2 - Does YZ features, but also want it to do the X features. Such that it does XYZ features :)
I have two apps, I want to merge them, by bringing the smaller app in to the main application, such that instead of the smaller app originally being instantiated from it's App Delegate, is instead pushed via the existing navigation controller of the main controller.
But the original developer has got various dependencies on the structure of the app and the original app delegate singleton, making it non trivial to push it's main View controller without re arranging code.. which takes time.
How do people normally take a standard cocoa project and turn it into a feature of some other existing application, while retaining the ability to keep things nicely decoupled?
XCode Project 1 - Does X features
XCode Project 2 - Does YZ features, but also want it to do the X features. Such that it does XYZ features :)
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
![扫码二维码加入Web技术交流群](/public/img/jiaqun_03.jpg)
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
如果应用程序的设计和构建不是为了促进这一点,那么您可能需要进行一些重写。
真正的答案是使用封装和松散耦合等原则提前计划,并采用模型-视图-控制器等架构模式。
我浏览过这个网站,其中有大量涉及OO 设计原则的文章链接。
If an application is not designed and constructed to facilitate this then you will probably be doing some rewriting.
The real answer is to plan for this ahead of time using principles like encapsulation, and loose coupling, and employing an architectural pattern like Model–view–controller.
I ran across this website with a ton of links to articles covering OO Design Principles.
您可以将项目 A 转换为静态库并在项目 B 中使用它。
You would convert your project A to a static lib and use it in project B.