[TIMOB-45] NavBar Color on "More" tab

GitHub Issue	n/a
Type	Bug
Priority	Medium
Status	Closed
Resolution	Fixed
Resolution Date	2011-04-17T01:50:12.000+0000
Affected Version/s	n/a
Fix Version/s	Backlog
Components	iOS
Labels	ios, iphone, mobile, tabbed
Reporter	Tobias Gaiselmann
Assignee	Reggie Seagraves
Created	2011-04-15T02:22:55.000+0000
Updated	2012-10-02T03:10:23.000+0000

Description

My tiapp.xml file contains about 7 windows. All have the backgroundColor set to #000.
Titanium Mobile automaticly create the "more" tab for pages 5,6 and 7.
When I switch to the "more" tab the NavBar has the default color.
It would be nice if it takes #000 as backgroundColor, too.

Comments

Jeff Haynie 2011-04-15

Blain, can you look at this in the next milestone?
Blain Hamon 2011-04-15

Clarifying here: I'm assuming you mean the barColor (the color/tint/style of the nav bar) instead of backgroundColor (The color of the content area where the actual extra tabs are listed).

It looks like it's certainly doable, although this raises the question of where to specify it in the TiApp.xml. I'm also thinking, since repeating the same properties over and over is tiresome, it might be good to be able to specify properties that are treated as the default for app windows, the more tab included.
Tobias Gaiselmann 2011-04-15

The barColor is what I mean.
I think, application-wide properties would be very usefull.
Blain Hamon 2011-04-15

Okay, possible proposal for feature functionality:

in tiapp.plist (And by extension, tiapp.xml) an optional entry of 'template' is a dictionary-type object that represents an abstract titanium window.

Possible properties that can be inherited from the template may include 'barColor', 'background', 'backgroundImage', 'orientation', 'barImage', 'landscapeBackgroundImage', 'statusBarStyle', 'fullscreen', 'hideNavBar', and 'hideTabBar'.

Some of these could apply to a custom moreNavigationController.
Blain Hamon 2011-04-15

Followup of possible pitfall or very subtle difference.

A barColor can be one of three possible states: Null, a color, or 'transparent'. If Null, the standard blueish color is used (Nontinted).

Given a template that specifies a black barColor, there is a subtle yet important difference between specifying a window having a null barColor and a window having an undefined barColor. The former is to use the blue. The latter is to inherit the black from the template. This might trip people up.

Given that android doesn't have a difference between null and undefined, this might be trouble in the future (Not with barColor given that it's iPhone-only, but in general)
Blain Hamon 2011-04-15

barColor is a property of the tab group to allow this to work. Clearing out old fixed bugs.

JSON Source