Mozilla

• Roadmap
• Projects
• Coding
  • Module Owners
  • Hacking
  • Get the Source
  • Build It
• Testing
  • Releases
  • Nightly Builds
  • Report A Problem
• Tools
  • Bugzilla
  • Tinderbox
  • Bonsai
  • LXR
• FAQs

Summary/Overview

The task bar will be the place in Communicator Seamonkey where users launch or switch tasks, applications or net based services. In additions the Menu Framework specification will also offer a Tasks menu (formerly Communicator menu) that lets users access applications and services.

Goals for our end users

Target Audience

The target user for this feature are Communicator Seamonkey users as described in the Seamonkey PRD, but especially users new to either Navigator or Netcenter.

User Tasks

 

Fundamental Tasks Intermediate Tasks Advanced Tasks Start core browsing, email or chat activities from within everywhere of the product. Easily switch between open/running windows and tasks Discovery of available Netcenter services Collapse task bar if real estate is needed Reconfigure items in task bar

---

Design Cheat sheet

---

Design Details

Overview of component groups in the task bar

			"Extensible services area"
Component		Core Applications	Additional Tasks/Services	QwikApps Launcher	Window Switcher
Purpose		Users will have access to our core level applications such as email, browsing and potentially chat (possibly falling under "people")	Expose Users to second-level functionality grouped under meaningful user-termed categories	One-click access to 3-4 core apps in Communicator. Some small-form-factor apps may use this as a substitute for the bulkier full taskbar.	Alleviate 'window futzing' as observed time and time again in our end user studies.  Open windows are treated as tasks that users can switch to. This way open windows do not "get lost" (when covered up) for some users with maximized window settings. More discoverable for a certain class of end users that don't see the windows menu item we'll still keep the windows submenu for keyboard access to switching and for legacy reasons
Presentation		Core apps are presented as one top level button ("menu") per applications These items will have a constant location and should be grouped starting on the left margin Total number of core app buttons may not exceed 4 Top level item will have a name no longer than 1-2 words Sub items may contain no more than 3-4 words per item (except for that list specific content/titles)	will be presented as top level groupings/categories,  Those service groups will fill the available space to the right of the core apps items The task bar may display more than one line of items (i.e.. wrap) if needed Total number of containers in this section may not exceed 4 Top level item will have a name no longer than 1-2 words Sub items may contain no more than 3-4 words per item (except for that list specific content/titles)	small space-saving icons Total number of quick access buttons may not exceed 5	The window switcher is presented as a top level item on the Taskbar. We should aim to give it a constant location. Possible locations: to the right of core apps, at the right border of the task bar  Top level item will have a name no longer than 1-2 words Sub items may contain no more than 3-4 words per item (except for that list specific content/titles)
Contents		will contain the basic activities that can be started with these applications	each containing a number of services that fit within that category	just the core apps (behaves like 4.5 task bar)	similar to the 4.5 Communicator Window menu this will contain access to all open windows. One sub item per open window in the form "activity verb + window content title", e.g. "Compose 'document2000.html'"
Can be removed? (prelim thinking)		no, except for by advanced end users is even available when component is not currently downloaded to promote component to access integrated 3rd party component (e.g. Eudora Pro) need to be able to return to default	Netcenter may remove outdated items after users consent Netcenter may modify items inside containers	no, except for by advanced end users	no, except for by advanced end users
who can add to/update it? (prelim thinking)		should stay constant	Netcenter may update containers as well as items inside containers. Needs users consent. I.e. dialog asking user	Items cannot be added to it from outside	Items cannot be added to it from outside, this will be automatically filled by client enumerating the open windows
get reflected into Tasks menu?		yes	generally no, some core items may get reflected under their main category and a submenu	components are already represented in C5 menu	yes

The aforementioned Tasks menu (formerly known as Communicator menu) may look like this

Content presentation

Recommended Approach A: Combination

One-click buttons for core applications, folders/popdowns for non-core services

the following approaches were also considered (click on image to see real scale):

Approach B: Breadth Priority

folders/popdowns for all apps and services

Approach C: Quick Access Priority

One-click icons for quick access to core applications, on folder for all other services

Approach D: Combined Design

folders/popdowns for all apps and services along with one-click icons for quick access to core applications
 

Layout of Taskbar functionality

below the status bar (favored approach)

the following approaches were also considered (click on image to see real scale):

combined task bar with quick access icons at lower right corner of each window.

above all toolbars visually separated

below all toolbars visually separated

between toolbars visually integrated

as a floating palette

Open Issues

• Net2phone button integration

Menus & Preferences 

Context Menus

The will be specific items here to get at the properties of the task bar for advanced users with the ability, as well as to let the user reset the bar to the 'factory default

Preferences

 

Condition Message User Choices

---

Archived Documents

Revisions

Rev 1: first stab, based on  UI design docs

Rev 2: added new concepts for layout, bringing back the 4.5 taskbar in bottom right corner as an idea (some feedback was received that users rely on it for quick access)

Special Notes