All geek questions in one place

UITabBarController UINavigationController Design Advice

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

The iPhone SDK documentation indicates that you may have a tab bar controller containing a navigation controller, but you cannot have a navigation controller with a tab bar controller. It seems that there are times when you might need to organize the views in a view that is part of the navigation controller stack in a tabular form. Is it unreasonable?

I accept what Apple dictates in these areas as the gospel, because HIG does provide best practices that seem to show the path of least resistance (I'm sure there are exceptions). However, in the tab bar area, I'm not sure if this is related to the design. This may be obvious to others, but I can't figure out why you would not allow tabs anything but the root level controller.

What do you all think or know? What design flaw does this create? How would you solve this problem to get a table view of the views in the view? Do I need to rethink the whole design?

Thanks.

+3
source share
3

, , . , , navbars . , , , , , , , . Three20 , , , , .

, Tweetie , , UITabbarController, , .

+1

, UITabBars . , , , . UITabBar, . , , , , UITabBar.

.

"" , . (. HangTime ). , , "".

, , Facebook, , " " , , UITabBar. Three20 . : http://github.com/joehewitt/three20/tree/master

+1

I think the controller of the tab bar should be the main point of navigation in the application, if used. If the nav controller contains a tab controller, the tabs will switch whenever you move to another place, which may confuse users who are used to using them in other applications. I think this is a cool idea, but an apple may not feel the same way.

0
source

Source: https://habr.com/ru/post/1714674/

More articles:


All Articles