• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Custom views in navigationbar (iOS 3.2)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Custom views in navigationbar (iOS 3.2)


  • Subject: Re: Custom views in navigationbar (iOS 3.2)
  • From: glenn andreas <email@hidden>
  • Date: Wed, 23 Jun 2010 09:02:00 -0500

On Jun 23, 2010, at 5:51 AM, Christian Ziegler wrote:

> Hi guys,
>
> I'm having a hard time with the navigation bar. What I'm trying to do is adding a custom breadcrumbs navigation to the bar. I coded two classes, a subclass of UIButton for the breadcrumbs segments and a sublcass of UIView for the whole bar. The bar has a home segment which represents the rootViewController of the navigationController and you can add additional segments when you push new viewControllers on to the navigationController's stack.

You do realize that the HIG explicitly says to not do that?   From <http://developer.apple.com/iphone/library/documentation/userexperience/conceptual/mobilehig/SpecialViews/SpecialViews.html#//apple_ref/doc/uid/TP40006556-CH10-SW21>

Using a multi-segment back button causes several problems:

	• The extended width of a multi-segment back button does not leave room for the title of the current screen.
	• There is no way to indicate the selected state of an individual segment.
	• The more segments there are, the smaller the hit region for each one, which makes it difficult for users to tap a specific one.
	• Choosing which levels to display as users navigate deeper in the hierarchy is problematic.
If you think users might get lost without a multi-segment back button that displays a type of breadcrumb path, it probably means that users must go too deeply into the information hierarchy to find what they need. To address this, you should flatten your information hierarchy.




So once you spend hours and hours coding and getting this working perfectly, it will probably end up being rejected by the AppStore approval process.


Glenn Andreas                      email@hidden
The most merciful thing in the world ... is the inability of the human mind to correlate all its contents - HPL

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Custom views in navigationbar (iOS 3.2) (From: Christian Ziegler <email@hidden>)

  • Prev by Date: Re: File descriptors not freed up without a -closeFile call
  • Next by Date: Re: Problem with stopModalWithCode on a different thread
  • Previous by thread: Custom views in navigationbar (iOS 3.2)
  • Next by thread: IBPlugin with Core Animated button.
  • Index(es):
    • Date
    • Thread