Bugzilla – Full Text Bug Listing
| Summary: | [Improve emitters] Add support for emitter UI extenion | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | CDE Administration <cdeadmin> | ||||
| Component: | BIRT | Assignee: | Zhiqiang Qian <zqian> | ||||
| Status: | VERIFIED FIXED | QA Contact: | Xiaodan Wang <xwang> | ||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | camle, clin, kitlo, mindan.xu, rkanguri, wenfeng.fwd, wyan, xwang, zqian | ||||
| Version: | 2.2.0 | Keywords: | plan | ||||
| Target Milestone: | 2.5.0 M7 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux-GTK | ||||||
| URL: | 525 | ||||||
| Whiteboard: | Obsolete | ||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 189107, 246259 | ||||||
| Attachments: |
|
||||||
|
Description
CDE Administration
Created attachment 69620 [details]
04.002000.jpg
<cde:tctdetail> Testcase: 04.002000 Project: WSW33 Component: CDE - BIRT/Report Designer Priority: 3 Subject: pl: View Report -> items not externalized Article ID: 525 Originator: tctbroadcast@pl.moraviaworldwide.com </cde:tctdetail> <response_by> Bryan Green at 2007.05.31.16.24.06 </response_by> Changing status in TCT. 190347 TVT33:TCT525: pl: View Report -> items not externalized
189107 [Accessibility] There is no short cut for View Report [00]
I think all those issue should resolved by UI as:
1. The UI/localization is not the core task for emitter.
2. The emitter may used by multiple applications, such as Report Designer, WEB-VIEWER, IV. Different applications have different requests for the UI resources.
3. The emitter may be develped by third party contributor, which may not concern about the UI operations.
4. The emitter developer has no resource to resolve the UI issues, such as localization, ICON etc.
UI can handle those issues as:
1. UI defines a repository which contains all those visual datas, the reporsitory should support localization and interlization:has following strcutures:
emitter id.
locale
display name
icon
shortcut key
description etc.
2. UI get all supported emitters from report engine, for each emitter, searchs the displayed information from
the reporsitory, uses the localized information to define the UI components, such as meanu, dialog etc.
3. UI needs create a default implementation for all extened emitters which has no pre-defined resources.
I think in this case, engine need also add a "display name" item in the emitter extension schema, as it already has an "icon" entry. This information is not bound to any particular designer implementation, it can be used by any emitter consumers. A complete solution need UI introduce a new extension point, which will provide all the info UI need. Ideally, it includes all the localized messages, icon, shortcut key, a new configuration dialog, etc. *** Bug 227722 has been marked as a duplicate of this bug. *** We plan add this in next major release as it contains big UI behavior change. (In reply to comment #6) > A complete solution need UI introduce a new extension point, which will provide > all the info UI need. Ideally, it includes all the localized messages, icon, > shortcut key, a new configuration dialog, etc. IS this extension for the entire designer UI or only for the emitter/output format list? I think it is better for the emitter to return the output format display name based on locale, since it is the emitter itself to decide what the output format name should be for each locale. The emitter has to externalize error message too, can we use the same mechanism to externalize output format display name? (In reply to comment #9) > IS this extension for the entire designer UI or only for the emitter/output > format list? > > I think it is better for the emitter to return the output format display name > based on locale, since it is the emitter itself to decide what the output > format name should be for each locale. The emitter has to externalize error > message too, can we use the same mechanism to externalize output format display > name? > This extension is for emitter/output format. So ideally it can be used for both designer and viewer UI. The extension will be responsible for the text localization. The extension interface will contain refined methods to query miscellaneous display information from each emitter. How about enhance the emitter extension to return a output format display name based on locale? The emitter extension needs to return localized error message anyway, so it should already have the infrastructure to return localized output format display name. try to avoid adding an extension just for a display name. (In reply to comment #11) > How about enhance the emitter extension to return a output format display name > based on locale? The emitter extension needs to return localized error > message anyway, so it should already have the infrastructure to return > localized output format display name. > > try to avoid adding an extension just for a display name. > This interface not only provides the display name, it also provides other information like detailed description, optional icon, configurable emitter options. Each emitter option can define the option type, description, default value, etc. In nature, it's a complementary of current emitter interface. Regarding the design, I think it's also ok to enhance current emitter extension. We can add an optional "descriptor" element under current emitter extension, this element defines an IEmitterDescriptor instance which returns above information. The new extension point is added. The new extension point is added. Verified. |