Firefox/Projects/New Theme: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 4: Line 4:
'''Timeframe:''' (beginning 2009/07/13)–(ending ?)<br/>
'''Timeframe:''' (beginning 2009/07/13)–(ending ?)<br/>


'''Description:''' Exploring a revamp of the Windows theme in evolutionary phases. Identifying current issues and weaknesses. Focus on modernizing and streamlining.
'''Description:''' Exploring a revamp of the Firefox Theme/UI in evolutionary phases for 3.7 and 4.0. Identifying current issues and weaknesses. Focus on modernizing and streamlining. Specific emphasis on apperance and behavior on Windows Vista/7. Increased cross-platform cohesiveness.
 
= Current Theme Issues =
[[Firefox/3.0 Windows Default Theme Issues|3.0 Windows Default Theme Issues]]
 
= Visually Appealing Windows Applications =
[[Firefox/Projects/Windows_Theme_Revamp/Visually_Appealing_Windows_Applications|Visually Appealing Windows Applications]]


= Goals =
= Goals =
== General ==
* Streamline UI Elements
* Streamline UI Elements
* Reduce Visual Footprint
* Reduce Visual Footprint
* Modernize Look and Feel
* Modernize Look and Feel
* Retain Visual Integration While Still Being Attractive
* Retain Visual Integration While Still Being Attractive
* Increased Cross Platform Consistency (Where Applicable)


= Design =
= Windows =
New theme implementation should be accomplished in two(or more) evolutionary phases.
== Current Theme Issues ==
[[Firefox/3.0 Windows Default Theme Issues|3.0 Windows Default Theme Issues]]: This is a good starting point that identifies problems and shortcomings with the current Theme/UI on Windows. Focus on Windows Vista and 7.


== Mockups ==
== Visually Appealing Windows Applications ==
* '''<span style="color: #26A5D0">(Updated)</span>''' 3.7 Mockups: [[Firefox/3.7 Windows Theme Mockups]]
[[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Visually_Appealing_Windows_Applications|Visually Appealing Windows Applications]]: Some examples of Windows applications that are visually appealing and/or have good UI design.
* 4.0 Mockups: [[Firefox/4.0 Windows Theme Mockups]]


== Short-Term (Firefox 3.7): ==
== Design: ==
'''<span style="color: #26A5D0">(Updated)</span>'''
New theme implementation should be accomplished in two(or more) evolutionary phases.
[[File:(Windows)-(Firefox.next)-(3.5–3.7-Evolution)-Wireframe-(Ver-001).png|300px|left|thumb|3.7 Evolution Wireframe (Rev 02)]]
 
<br style="clear:both" />
=== Short-Term (Firefox 3.7): ===
[[File:(Windows)-(Firefox.next)-(3.5–3.7-Evolution)-Wireframe-(Ver-001).png|200px|right|thumb|3.7 Evolution Wireframe (Rev 02)]]
Style and texture changes. Removal of menubar. Some element shifting.
Style and texture changes. Removal of menubar. Some element shifting.
* Make use of Aero Glass
* Make use of Aero Glass
Line 44: Line 39:
* General icon cleanup/polish
* General icon cleanup/polish


== Long-Term (Firefox 4.0): ==
=== Long-Term (Firefox 4.0): ===
'''<span style="color: #26A5D0">(Updated)</span>'''
[[File:(Windows)-(Firefox.next)-(3.7–4.0-Evolution)-Wireframe-(Ver-001).png|200px|right|thumb|4.0 Evolution Wireframe (Rev 02)]]
[[File:(Windows)-(Firefox.next)-(3.7–4.0-Evolution)-Wireframe-(Ver-001).png|300px|left|thumb|4.0 Evolution Wireframe (Rev 02)]]
<br style="clear:both" />
Major changes. New UI elements, removal and/or relocation of traditional elements.
Major changes. New UI elements, removal and/or relocation of traditional elements.
* Combine Reload/Stop/Go
* Combine Reload/Stop/Go
Line 60: Line 53:
* Even less system native styling
* Even less system native styling
* Download notification overlay UI
* Download notification overlay UI
=== Mockups ===
* [[Firefox/3.7 Windows Theme Mockups]]
* [[Firefox/4.0 Windows Theme Mockups]]
= Mac =
== Design: ==
The design for Mac is very similar to what has been [[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Direction_and_Feedback|proposed for Windows]]. With some exceptions:
* The Menubar, being a system wide element, will stay.
* The Page and Tools buttons will be hidden by default.
There are many stylistic changes that are addressed in depth in the [[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Mac_Specific_Visual_Refresh|Mac Specific Visual Refresh]] article.
=== Mockups ===
* [[Firefox/3.7 Mac Theme Mockups]]
* [[Firefox/4.0 Mac Theme Mockups]]


= Proposed Theme/UI Direction and Feedback =
= Proposed Theme/UI Direction and Feedback =
== Direction and Feedback ==
[[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Direction_and_Feedback|Direction and Feedback]]: In depth exploration of proposed ideas for Firefox 3.7 and 4.0.
== Mac Specific Visual Refresh ==
[[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Mac_Specific_Visual_Refresh|Mac Specific Visual Refresh]]: Proposed Mac specific visual refresh.


[[Firefox/Sprints/Windows Theme Revamp/Direction and Feedback|Direction and Feedback]]


= Platform Capabilities  =
= Platform Capabilities  =
Line 69: Line 84:
These are all things that we would need to be able to do to create the theme changes that have been mocked up.&nbsp; As new limitations emerge I'll add them to this list as well.  
These are all things that we would need to be able to do to create the theme changes that have been mocked up.&nbsp; As new limitations emerge I'll add them to this list as well.  


=== All Platforms: General ===
== All Platforms: General ==


* {{bug|513157}} Ability to draw the title bar ourselves (possibly tabs, weave, OS theme integration, personas)  
* {{bug|513157}} Ability to draw the title bar ourselves (possibly tabs, weave, OS theme integration, personas)  
Line 88: Line 103:
**Dao got started on doing this, it's a build time thing
**Dao got started on doing this, it's a build time thing


=== All Platforms: Customization ===
== All Platforms: Customization ==


*Ability to have multiple instances of the same control in the customization palette  
*Ability to have multiple instances of the same control in the customization palette  
Line 96: Line 111:
**Possible, but a lot easier to just do it based off of the immediate right and left items. We can go farther than that but it starts to get intractably complex.
**Possible, but a lot easier to just do it based off of the immediate right and left items. We can go farther than that but it starts to get intractably complex.


=== Windows ===
== Windows ==


*Ability to package multiple themes (XP, Vista, 7) instead of relying on chrome overrides  
*Ability to package multiple themes (XP, Vista, 7) instead of relying on chrome overrides  
canmove, Confirmed users
455

edits

Navigation menu