blocks|key|816359|text|a)或b)都是可行的。选择将取决于一些因素，如使用模型层来确定视图呈现顺序的程度。如果表示序列是动态的，那么helper类设计(您的选项b)在MVC分离方面可能更纯粹。最终，决定取决于应用程序的细节和复杂性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|816360|一般来说，我在做出这样的设计决策时会问一些问题：|816361|816362|它如何影响内存管理？|unordered-list-item|offset|length|style|BOLD|816363|设计将如何影响适当的设计分离关注？|816364|设计灵活？是否利用框架/平台设计patterns|816365|来最小化dependencies|816366|Does设计|816367|816368|entityMap^0|0|0|0|5|4|0|C|4|0|2|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|Z|8|@$H|10|I|11|J|K]]|9|@]|A|$]]|$1|L|3|M|5|G|7|12|8|@$H|13|I|14|J|K]]|9|@]|A|$]]|$1|N|3|O|5|G|7|15|8|@$H|16|I|17|J|K]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|18|8|@]|9|@]|A|$]]|$1|R|3|S|5|G|7|19|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|V|$]]

Either a) or b) would work. The choice would depend on factors like the degree to which the model layer is used to determine the sequence of presentation of views. If the presentation sequence is dynamic, then the helper class design (your option b) may be purer in terms of MVC separation. Ultimately, the decision depends on the details and complexity of your application.

Generically, some of the questions I ask when making design decisions like this:

<ul>
<li>How does it affect memory management? </li>
<li>How will the design affect performance?</li>
<li>Does the design appropriately separate concerns? </li>
<li>Is the design flexible? Does it minimize dependencies?</li>
<li>Does the design take advantage of framework/platform design patterns?</li>
</ul>

blocks|key|5208323|text|在你提出的选项中，我最喜欢c)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5208324|选项a)的不足之处在于，它忽略了主要的视图控制器--管理内容的整页视图。在像您这样的情况下使用addSubview需要跨越一大堆障碍，以便管理视图层次结构中所有这些对象的内存，而且您最终会重新发明UIViewController轮子。|offset|length|style|CODE|5208325|选项b)是可以的，但不知何故它似乎永远不会让我满意。只是随意地交换根目录似乎是有风险的--这就是UIViewController要做的事情，它可能会比你我做得更好。无论如何，如果你这样做，你会失去任何动画的好处。这就引出了..。|5208326|选项c)。UINavigationController被编程为根据您的特定情况执行所需的工作。你可以使用UINavigationController的-+(void)setViewControllers:(NSArray+*)viewControllers+animated:(BOOL)animated来管理层级结构。你可以做一个普通的推送，但这会让你的主游戏VC在内存中保留之前的VC，并且需要系统的资源。简而言之，我认为你的c)是简单而有效的。|5208327|正如这里的后处理脚本一样，请注意，除了a、b、c之外，还有其他选择。您可以使用UIPageViewController，尽管我不推荐使用它。iOS+5引入了UIStoryboard作为管理应用程序UI的方法，并引入了UIStoryboardSegue来管理过渡。查看文档，如果你的目标是iOS+5，它们可能也会对你有所帮助。但这听起来像是一个简单的导航控制器将为您工作。|5208328|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/library/ios/#documentation/UIKit/Reference/UINavigationController_Class/Reference/Reference.html#//apple_ref/occ/cl/UINavigationController|1|https://developer.apple.com/library/ios/#documentation/UIKit/Reference/UIPageViewControllerClassReferenceClassRef/UIPageViewControllerClassReference.html#//apple_ref/occ/cl/UIPageViewController|2|https://developer.apple.com/library/ios/#documentation/UIKit/Reference/UIStoryboard_Class/Reference/Reference.html|3|https://developer.apple.com/library/ios/#DOCUMENTATION/UIKit/Reference/UIStoryboardSegue_Class/Reference/Reference.html^0|0|1B|A|2Q|G|0|0|1G|M|23|25|1G|M|0|0|13|K|1|26|C|2|30|H|3|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@$D|13|E|14|F|G]|$D|15|E|16|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|17|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|18|8|@$D|19|E|1A|F|G]|$D|1B|E|1C|F|G]]|9|@$D|1D|E|1E|1|1F]]|A|$]]|$1|L|3|M|5|6|7|1G|8|@]|9|@$D|1H|E|1I|1|1J]|$D|1K|E|1L|1|1M]|$D|1N|E|1O|1|1P]]|A|$]]|$1|N|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]|V|$5|Q|R|S|A|$T|W]]|X|$5|Q|R|S|A|$T|Y]]|Z|$5|Q|R|S|A|$T|10]]]]

Of the options you present, I like c) the best.

Option a) falls short because it ignores the primary rôle of view controllers - to manage full-page views of content. Using <code>addSubview</code> in situations like yours requires you to jump through a bunch of hurdles in order to manage the memory of all those objects in the view hierarchy, and you would just wind up reinventing the <code>UIViewController</code> wheel.

Option b) is ok, but somehow it never seems to satisfy me. Just swapping the root in and out willy-nilly seems risky - this is what UIViewController is made to do, and it will probably do it better than you or I could. At any rate, you lose any benefits of animation if you do this. Which brings us to...

Option c). UINavigationController is programmed to do the work required of your particular situation. You can manage the hierarchy using <a href="https://developer.apple.com/library/ios/#documentation/UIKit/Reference/UINavigationController_Class/Reference/Reference.html#//apple_ref/occ/cl/UINavigationController" rel="nofollow"><code>UINavigationController</code></a>'s <code>- (void)setViewControllers:(NSArray *)viewControllers animated:(BOOL)animated</code>. You could do a normal push, but this will keep the previous VC in memory while your main game VC sits in front and demands resources from the system. In short, I think your c) is easy and effective.

As as post script here, be aware that there are alternatives other than your a,b,c. You might get by with using a <a href="https://developer.apple.com/library/ios/#documentation/UIKit/Reference/UIPageViewControllerClassReferenceClassRef/UIPageViewControllerClassReference.html#//apple_ref/occ/cl/UIPageViewController" rel="nofollow">UIPageViewController</a>, though I'm not recommending it. iOS 5 introduced <a href="https://developer.apple.com/library/ios/#documentation/UIKit/Reference/UIStoryboard_Class/Reference/Reference.html" rel="nofollow">UIStoryboard</a> as a method to manage your app's UI, and <a href="https://developer.apple.com/library/ios/#DOCUMENTATION/UIKit/Reference/UIStoryboardSegue_Class/Reference/Reference.html" rel="nofollow">UIStoryboardSegue</a> to manage transitions. Check out the docs, if you're targeting iOS 5, they might help you as well. But it sounds like a simple nav controller will work for you.

I am making a multiplayer game. My First screen , should show a login form (not modally). When it finishes, it should call a delegate to my "root class" and the "root class" should remove this view controller and add another.Then when the game ends the "root class" will be called with another delegate method and it should show another screen etc..

I have 3 ideas about it and I would like to know which is going to work better.

a) My root class is a uiviewcontroller and it adds/removes subviews when the delegate methods are called.

b) My root class is NSObject subclass and it changes the window rootViewControoler when it has to.

c) Navigation controller without navigation bar. But how i manage view hiearchy?

What is better logic to manage my view hieararchy? Any other idea than a and b?

Architecture of view hierarchy - iPhone

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我在做一个多人游戏。我的第一个屏幕，应该显示一个登录表单(非模态)。当它结束时，它应该调用一个委托给我的“根类”，“根类”应该删除这个视图控制器，并在游戏结束时添加another.Then。“根类”将用另一个委托方法调用，它应该显示另一个屏幕，等等。我有3个想法，我想知道哪一个会更好。a)我的根类是一个uiviewco...

问视图层次结构- iPhone
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问视图层次结构- iPhoneEN