Confirmed users
371
edits
(saving process section before i lose that) |
No edit summary |
||
(10 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
'''NOTE''': The content on this page has been moved to MDC: [http://developer.mozilla.org/en/Thunderbird/Activity_Manager Activity Manager], [http://developer.mozilla.org/en/Thunderbird/Activity_Manager_interfaces Activity Manager Interfaces] and [http://developer.mozilla.org/en/Extensions/Thunderbird/HowTos/Activity_Manager Activity Manager Examples] | |||
{{draft}} | {{draft}} | ||
== Activity Manager == | == Activity Manager == | ||
Is a simple component that understands how do display a combination of user activity and history. The activity manager works in conjunction with the [[Thunderbird:Interactive Status Bar]] to give the user the right level of notifications concerning what Thunderbird is doing on it's own and how Thunderbird has handled user requests. | |||
* [[Thunderbird: | * [[Thunderbird:Interactive Status Bar]] — displays important events and process activity to the user | ||
* [[Thunderbird:Activity Manager/Window]] — displays | * [[Thunderbird:Activity Manager/Window]] — displays a more detailed summary of activity for each process and event with relevant actions for each item | ||
Events are persistent in the Activity Manager, they should be saved for a set period of time which can be determined after some performance work and testing. | |||
Development for the Activity Manager can be tracked in {{bug|257942}} | Development for the Activity Manager can be tracked in {{bug|257942}} | ||
== Activity Items == | == Activity Items == | ||
Line 38: | Line 38: | ||
** Not all processes need to convert to events (such as sending mail) | ** Not all processes need to convert to events (such as sending mail) | ||
There is no failure state included in the process state, there is only try again and wait for input. This is intentional because there should never be a time that Thunderbird completely quits on it's user, it can and should continue trying until it has succeeded or been told to cancel. During this period of continually trying it's important that, through these changes, the user is aware of what Thunderbird is doing and has the capability to alter it's actions by cancelling the try again process. | |||
Processes should (essentially) be directly attached to a server URL. With incoming email accounts and outgoing email accounts the errors are almost always problems with server connections. When a connection fails the group of actions running will often all block at the same issue, be it trying the connection again or waiting for user input. Therefore by creating a relationship of process to server with multiple actions in the process we can have a user interface where single actions are available to ''try now'' for all actions running in a process. | |||
''Sort Order'' | |||
Here are 2 examples of processes | An active process is always sorted at the top of the Activity Manager Window by start time while it is active. Once a process is finished it can convert to an event and then is sorted like an event. If a process is in the Try Again state it is sorted above active processes and a process in the Waiting for Input state is sorted above all. | ||
''Here are 2 examples of processes'' | |||
==== Account Activity ==== | ==== Account Activity ==== | ||
A Process connected to the mail account which creates multiple events for different activities. This is the parent process essentially responsible for the connections between | A Process connected to the mail account which creates multiple events for different activities. This is the parent process essentially responsible for the connections between Thunderbird and a mail server. As it synchronizes mail or performs user initiated actions it can create events or errors in the Activity Manager. | ||
A single account process can perform multiple actions at the same time, for example. | |||
<pre> | |||
+--------------------------------------------------------------------+ | |||
| Moz Mail ( v ) | | |||
| | | |||
| [===================== ] 100 of 300 messages | | |||
| Synchronizing Folder 'bugs' | | |||
| [============ ] 3 of 20 messages | | |||
| Moving Conversation from 'Inbox' to 'Personal' | | |||
| [=============================== ] 23 of 30 messages | | |||
| Filtering messages in 'Inbox' | | |||
| | | |||
+--------------------------------------------------------------------+ | |||
</pre> | |||
''More examples at the [[Thunderbird:Activity Manager/Process/Account Activity|Account Activity]] page'' | |||
Possible Events Created | Possible Events Created | ||
* Moved - Folder / Message / Conversation | * Moved - Folder / Message / Conversation | ||
* Copied - Folder / Message / Conversation | * Copied - Folder / Message / Conversation | ||
* Deleted - Folder / Message / Conversation | * Deleted - Folder / Message / Conversation | ||
Possible | Possible Try Again States | ||
* | * Connection Error | ||
* | |||
Possible Waiting for Input State | |||
* Password Error | |||
Possible Finished State | |||
* Completed Sync | |||
==== Sending Mail ==== | ==== Sending Mail ==== | ||
A parent process which represents the connection to an SMTP server. The display of this process is transient | A parent process which represents the connection to an SMTP server. The display of this process is transient, therefore on finished state it disappears from the Activity Manager Window leaving behind only the Sent Mail Events. | ||
Once the connection to the server is made this process can display progress as it creates Sent Message events for each message sent. | |||
<pre> | |||
+--------------------------------------------------------------------+ | |||
| Account - /Default SMTP/ | | |||
| | | |||
| [===================== ] 10 of 30 messages | | |||
| Sending Messages | | |||
| | | |||
+--------------------------------------------------------------------+ | |||
</pre> | |||
Possible Events Created | |||
* Sent Message | |||
Possible Try Again States | |||
* Connection Error | |||
* General Error | |||
Possible Waiting for Input State | |||
* Password Error | |||
Finished State | |||
* ''Disappear'' | |||
=== Events === | === Events === | ||
Line 76: | Line 120: | ||
The goal of an event is to provide a historical context to the user about actions they performed, such as sending mail or deleting contacts. In future versions events could have an and undo context to all people to recover from operations they didn't intend. | The goal of an event is to provide a historical context to the user about actions they performed, such as sending mail or deleting contacts. In future versions events could have an and undo context to all people to recover from operations they didn't intend. | ||
== | == Relevant Links == | ||
* [http://clarkbw.net/blog/2008/06/04/activity-is-the-new-download/ Activity is the new Download] | |||
* [http://clarkbw.net/designs/interactive-status-bar/ interactive status bar designs] | |||
== Relevant Bugs == | == Relevant Bugs == |