| Summary: | Readonly file widget: Implementing status service and error handling. | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | libing wang <libingw> |
| Component: | Client | Assignee: | libing wang <libingw> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | simon_kaegi |
| Version: | 5.0 | ||
| Target Milestone: | 5.0 RC1 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
libing wang
Most of the file client API calls happen in the inputManager. It relies on the service registry to get the status service then call the status service API to render errors. The widget is basically reusing the inputManager to handle the fileClient API calls. E.g. fetchChildren, read content, read meta data, etc. We can either: 1. Register a new status service impl in the serviceRegistry and pass it into inputmanager. Or: 2. Refactor the inputManager a little so that it optionally accept a passed in status service. I prefer option so far. Already fixed. |