RE: [mylar-dev] issues with task context management

["Mik Kersten" <beatmik@xxxxxxx>]

Eugene, we need to make sure that we have bugs for each of these under the
Core component and ensure that any bugs not linked below get scheduled for
1.0.  All linked were already scheduled as such, but this summary provides a
great check-list of the context model updates we need.

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
...
> -- fail to unfilter elements in package explorer when project has
> multiple source folders. This one is particularly painful, especially
> for Maven and WTP projects.

I recall you mentioning this somewhere but didn't find a bug, please submit
one.

> -- temporary unfiltering is screwed in a number of ways: clicked element
> does not gain interest and not stick (get filtered out again after
> releasing alt), can't select two elements from temporarily unfiltered
> folder, can't use popup menu on those elements... That is leaving
> keyboard-only navigation alone.

Added this comment to: 

112233: improve interaction for filtered element navigation
https://bugs.eclipse.org/bugs/show_bug.cgi?id=112233

> -- "lower interest" propagation to parents (especially in package
> explorer). E.g. when closing editor, its interest is lowered, but parent
> folder/package/project still have interest and clutter the view. So, if
> user just open several random classes using Ctrl-Shift-T or Ctrl-Click
> navigation and then close those opened editors, he'll end up with bunch
> of unfiltered projects/folders that will stay after editors been closed

118542: Open/close Java files leave interest on packages
https://bugs.eclipse.org/bugs/show_bug.cgi?id=118542

> -- Mylar fail to restore/save custom filters when enable/disable "Mylar"
> mode for package explorer and outline views. For instance I see closed
> projects when Closed projects filter is checked in the view settings.
> So, have to disable/enable filter to clean that.

I haven't noticed this, please submit a bug.

> -- The defaults for disabling filters should be adjusted. For example,
> filters for closed projects, empty packages, import and package
> declarations should not be disabled.

Please add this to the above bug.  I agree for all other than "empty
packages" which have a use case (Alt+click empty package, then drag in a
class).  Not clear if the use case is worth it. 

> -- unfiltering of the same jar (e.g. in plugin dependencies) several
> times when there is an interesting class opened from one of those jars.
> Note that link with editor actually able to figure out content of what
> jar need to be expanded, but Mylar somehow loose uniqueness of the
> context for this interesting class.

150331: libraries lose interest too quickly
https://bugs.eclipse.org/bugs/show_bug.cgi?id=150331

> -- picking up interest on externally changed resources (e.g. after vcs
> checkout or build). This been discussed many times and we don't have
> acceptable solution yet. If user not intentionally run background
> checkout when task is active, he may literally loose his context because
> of those incoming changes and the worst part that because context may
> grow very big, whole IDE became unusable.
>   I think that it would be much better to do not include changed
> resources (at least on checkout/refresh) unless they are within one of
> the projects that already have interest. Though, in my understanding,
> current problem is that Mylar does not know in context of what operation
> resource has gain its interest...

I added your comment to the corresponding bug.  We may be able to do the
right solution (detect when the resource addition events are in the workflow
of a checkout).  If that turns out to be too much work for 1.0 we can
implement the suggested work-around.

120499: Mylar should make explicitly created resources interesting, and
ignore others, e.g. from CVS checkout
https://bugs.eclipse.org/bugs/show_bug.cgi?id=120499

Mik