| Summary: | Spurious "Could not test xml nature" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] MoDisco | Reporter: | Ed Willink <ed> | ||||
| Component: | Infrastructure | Assignee: | Nicolas Bros <nicolas.bros> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | fabien.giquel, gdupe, hugo.bruneliere, modisco.web-inbox, nicolas.bros | ||||
| Version: | 0.9.0 | Flags: | nicolas.bros:
indigo+
fabien.giquel: review+ |
||||
| Target Milestone: | 0.9.0 M2 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows Vista | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Ed Willink
Created attachment 178250 [details]
patch
Here is a patch:
- don't emit a warning if the file is not synchronized with the workspace
- compute applicable discoverers lazily, when the "MoDisco" sub-menu is being opened. This avoids incurring a performance cost for each right-click (which grows as new discoverers are added). But as a side-effect, the "MoDisco" item always appears, even when there are no applicable discoverers. In this case, if this "MoDisco" sub-menu is opened, it contains a disabled item that reads "No discoverer is applicable to this selection".
I had a look on generic part of the fix : I totally agree with "lazy applicable discoverers computing" strategy, even if it causes some empty submenu in some cases. As Edward pointed it out, is was a real problem to impose recurrent scanning time for the eclipse user. Committed in revision 3004. The patch has been successfully applied. |