Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "E4/EAS/Status Reporting"
(→Eclipse 3.x API) |
(→Eclipse 3.x API) |
||
Line 2: | Line 2: | ||
==Eclipse 3.x API== | ==Eclipse 3.x API== | ||
− | The StatusLineManager and the 'Progress' view allows progress reporting to be done on it with some limited customization capabilities. | + | The StatusLineManager and the 'Progress' view allows status and progress reporting to be done on it with some limited customization capabilities. |
Critique | Critique | ||
+ | * The client code (the code reporting a problem) currently has to know too much about how it is reported | ||
+ | ** Need to set the StatusManager styles when calling the status handler | ||
+ | ** When creating a job, need to know the special IProgressConstants job properties to control how status is reported while a job is running. | ||
* The progress manager doesn't play well with wizards and dialogs | * The progress manager doesn't play well with wizards and dialogs | ||
− | ** If you a run a job in a modal dialog, there is no jobs progress dialog | + | ** If you a run a job in a modal dialog, there is no jobs progress dialog |
− | ** If you want to show progress in multiple places, you have to wrap the monitor | + | ** If you want to show progress in multiple places, you have to wrap the monitor. |
Revision as of 16:22, 29 October 2009
When operations are initiated, whether by the system or by the end user, it is helpful to be able to provide the user with updates about the status of these operations. This ties in with the progress service in that status reporting is concerned with a customizable way of rendering status information to the user whereas the progress service is concerned with how the work is scheduled and whether status information should be rendered at all or not.
Eclipse 3.x API
The StatusLineManager and the 'Progress' view allows status and progress reporting to be done on it with some limited customization capabilities.
Critique
- The client code (the code reporting a problem) currently has to know too much about how it is reported
- Need to set the StatusManager styles when calling the status handler
- When creating a job, need to know the special IProgressConstants job properties to control how status is reported while a job is running.
- The progress manager doesn't play well with wizards and dialogs
- If you a run a job in a modal dialog, there is no jobs progress dialog
- If you want to show progress in multiple places, you have to wrap the monitor.