Confirmed users
1,059
edits
Thunderbird:Activity Manager: Difference between revisions
no edit summary
No edit summary |
|||
| 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. | |||
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. | ||
''Here are 2 examples of processes'' | |||
==== Account Activity ==== | ==== Account Activity ==== | ||
| Line 106: | Line 108: | ||
Finished State | Finished State | ||
* ''Disappear'' | * ''Disappear'' | ||
=== Events === | === Events === | ||