You are currently viewing a snapshot of www.mozilla.org taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to www.mozilla.org, please file a bug.



 
Communicator Seamonkey cross components
UI Specification

Communicator Task Bar

send feedback to the component specific newsgroup

Last Modification:
Author German W. Bauer 
Initial Creation Date:  08 February 1999 
Status: Implemetable spec, exact co ntent and names of the category folders/popdowns is dynamic. Initial default TBD
What's related : 
Design Overview
Design Cheat sheet

Design Details 

 

UE Framework for Seamonkey
Menu Framework for Seamonkey (Tasks Menu esp)
Overall Seamonkey UI Specs Page

Feature Team
 
 

Older spec, will be updated

 

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

Provide a "portable" access point to and easy discovery of applications and services outside the current task context. Use the same consistent location throughout all applications.

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

     

    Tasks Menu        
         


    Design Details

    Overview of component groups in the task bar

    Related: check out the PM document with a more detailed description on task bar contents etc.
     
     
    Component
    Core Applications
    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") 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)
  • 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
  • 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
  • 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
  • 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
  • components are already represented in C5 menu
  • yes
  • The aforementioned Tasks menu (formerly known as Communicator menu) may look like this

    Tasks Menu        
         

     


    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

    Click to see larger image

    Approach C: Quick Access Priority

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

    Approach D: Combined Design

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




    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.
    Click to see larger image

    above all toolbars visually separated
    Click to see larger image

    below all toolbars visually separated
    Click to see larger image

    between toolbars visually integrated
    Click to see larger image

     

    as a floating palette
    Click to see larger image


    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

    No specific prefs are expected at this point in time. Most configuration is done through either Netcenter or by advanced users using a context menu "Properties" dialog.

    Error Messages and Dialogs
     
    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

    This is a pre-release document based on refined designs