Thunderbird Metro: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 5: Line 5:
|Feature health=OK
|Feature health=OK
}}
}}
{{FeatureTeam}}
{{FeatureTeam
|Feature additional members=Nate Watson
}}
{{FeaturePageBody
{{FeaturePageBody
|Feature open issues and risks=1. Microsoft will be the only provider of Metro apps. Getting it through is going to be a problem.
2. Running an E-mail client with the suspend system is going to cause some annoyances to the users and developers.
3. If this feature ships, what are we going to call Thunderbird on the classic desktop?
|Feature overview=Windows 8 will have 2 application environments: classic and metro. Thunderbird only has a classic version. Comments about metro aside, Thunderbird will need a metro version in order to compete with Microsoft's proprietary clients, and to work on WOA. The goal of this feature is to port Thunderbird to the Metro environment, while continuing to use Mozilla's technologies.
|Feature overview=Windows 8 will have 2 application environments: classic and metro. Thunderbird only has a classic version. Comments about metro aside, Thunderbird will need a metro version in order to compete with Microsoft's proprietary clients, and to work on WOA. The goal of this feature is to port Thunderbird to the Metro environment, while continuing to use Mozilla's technologies.
|Feature users and use cases=The target users in this case are Windows 8 users who would prefer a Metro version of Thunderbird, and WOA users who have no alternative.
|Feature users and use cases=The target users in this case are Windows 8 users who would prefer a Metro version of Thunderbird, and WOA users who have no alternative.
Line 16: Line 23:


Inter-compatibility with Thunderbird Classic add-ons.
Inter-compatibility with Thunderbird Classic add-ons.
|Feature functional spec=This feature will provide a Thunderbird interface that is designed to run on Metro.
|Feature functional spec=This feature will provide a Thunderbird interface that is designed to run on Metro. Large amounts of configuration will need to be introduced, due to the support for both touch screens and kb/m/m interfaces.
Due to Thunderbird's shortage of developers, in the early versions, Thunderbird Metro's interface will probably need to be as close as possible to Thunderbird main as possible.
 
For Metro, we should include 2 tabs systems: standard, like the one in Firefox; and visual, like the one in Firefox for tablets in horizontal mode. We may want to introduce some adaptations and/or port this over to Thunderbird for Classic. Introducing visual tabs may even necessitate its own feature due to the release cycles.
 
Thunderbird Metro will need to be just as customizable as classic; but this will need to have various components released over different cycles.
}}
}}
{{FeatureInfo
{{FeatureInfo
|Feature priority=Unprioritized
|Feature priority=Unprioritized
|Feature theme=Experience
}}
}}
{{FeatureTeamStatus
{{FeatureTeamStatus
59

edits

Navigation menu