UITabBarController UINavigationController设计建议 [英] UITabBarController UINavigationController Design Advice

查看:160
本文介绍了UITabBarController UINavigationController设计建议的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

这是一个更哲学的问题比任何,所以给我你的想法。



iPhone SDK文档指定您可能有一个标签栏控制器包含导航控制器,但是您不能具有包含选项卡栏控制器的导航控制器。看来有时候你可能想要在一个视图中组织视图,它是导航控制器堆栈的一部分,以表格的方式。这是不合理的吗?



我接受苹果在这些领域指示为福音,因为HIG确实提供了最佳实践,似乎揭示了最小阻力的路径有例外)。然而,在标签栏的情况下,我不确定它背后的设计推理。也许对别人很明显,但我不能想到一个很好的理由,为什么你不允许选项卡作为根级别视图控制器。



所有认为/知道?这将创造什么设计缺陷?你将如何解决这个问题,希望在视图中的表格表示视图?我需要重新考虑整个设计吗?



谢谢。

解决方案

我可以从设计的角度看到他们来自哪里。 Tabbars感觉锚定,常量,其中navbars感觉动态和mutable。因此,包含动态内容的选项卡是有意义的,而包含定位到屏幕底部的选项卡栏的导航堆栈的动态层次结构中的单个点并不正确。 Three20实现以一种更有意义的方式来处理这个问题,将标签固定在导航栏下面,以便他们感觉更像是导航堆栈中该点的一部分。


$ b $如果没有UITabbarController来绕过UI指南中的这个细节,Tweetie会自己创建一个标签栏,并且从交互的角度来看,它完全起作用。


This is more of a philosophical question than anything, so give me your thoughts.

The iPhone SDK documentation specifies that you may have a tab bar controller contain a navigation controller, but you can't have a navigation controller contain a tab bar controller. It seems that there are times when you might want to organize views within a view that is part of a navigation controller stack in a tabular fashion. Is this unreasonable?

I accept what Apple dictates in these areas as gospel as the HIG does provide best practices that seem to reveal the path of least resistance (I'm sure there are exceptions to that). In the tab bar case, however, I'm not sure the design reasoning behind it. Maybe it's obvious to others, but I can't think of a good reason why you wouldn't allow tabs as anything but a root level view controller.

What do you all think/know? What design flaw would this create? How would you solve this problem of wanting a tabular presentation of views within a view? Do I need to re-think the entire design?

Thanks.

解决方案

I can see where they are coming from, from a design perspective. Tabbars feel anchored, constant, where navbars feel dynamic and mutable. So a tab containing dynamic content makes sense, whereas a single spot in the dynamic hierarchy of a navigation stack containing a tab bar, anchored to the bottom of the screen doesn't feel as right. The Three20 implementation does handle this in a way that makes more sense, anchoring the tabs underneath the nav bar, so that they feel more like they are part of that spot in the navigation stack.

Having said that, Tweetie rolls it's own tab bar, if I remember correctly, without a UITabbarController to circumvent this detail in the UI guidelines, and it totally works from an interaction perspective.

这篇关于UITabBarController UINavigationController设计建议的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆