| Summary: | [context] add files to context only when it is edited, not on selection | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Christoph <christoph> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P5 | CC: | akshay.pandit, Martin.Kersten |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Christoph
This goes against the current design of having everything you touch be part of your context. We rely on the the notion of decay in the degree-of-interest model in order to ensure that not too much of what's touched but not interesting is in the context model. I'd like to avoid us adding a preference unless there is considerable interest in this feature, since I worry that it would make Mylyn feel unintuitive. In addition, the Synchronize view can already be used for checking all of the edited files that are interesting. Same over here. It's like working on a task and pollute the whole context. It's especially annoying working with local tasks and getting marks all over. Often I just search and dig in the code base to get inspirations and remember certain details I once know about and bam context polluted. These diggs are often off-topic in what relation but relevant in implementation logic (same problem different context) and should be in no means part of the context. Cleaning up the context after this is a pain... . Best would be like a rule set for the non-edited things. Rules might be: * Always add the non-edited stuff. (actual behavior may be default in some way) * Always add the non-edited stuff if it is of certain type. * Always add the non-edited stuff if it is within a project in context (allows to search other projects and once something of these objects get edited (relevant in behavior change) it gets added to context). * Always add the non-edited stuff if it is within a folder(package) part of the context. The gui for this would not be to difficult nor problematic, I think. It should be something similar to the filter dialog of the package explorer. Cheers, Martin (Kersten) *** Bug 244758 has been marked as a duplicate of this bug. *** Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |