RE: [mylyn-dev] Bug or Feature

["Mik Kersten" <beatmik@xxxxxxx>]

Good points Martin.  I think that we still have to figure out the following:

1) What to do when close means "free up resources" and not "I'm not
interested in this".  The premise Mylyn currently works with is that when
there are less than a few dozen editors open excessive resources are not
used.  We should gather all the cases where this is not true.

2) Handle the case of something being marked explicitly interesting.
Mylyn's current model assumes that over time everything can decay in
interest.  For two reasons:

	* Some task contexts can be very long lived (e.g. update web site)
and could become overloaded with landmarks.

	* We do not distinguish between implicitly created landmarks and
explicitly created ones in order to keep the UI simple (i.e. either it's
bold or it isn't).

What we could do for (1) is provide some kind of new command that closes
without reducing interest.  To determine how prominent this command would be
we will need a number of concrete use cases where this functionality is
desired.

What we could do for (2) is change the scaling of what it means to
explicitly mark something a landmark to make it require something like 10x
the current amount of lack of interaction with it to make it decay to be a
non-landmark.

Mik

> -----Original Message-----
> From: mylyn-dev-bounces@xxxxxxxxxxx [mailto:mylyn-dev-
> bounces@xxxxxxxxxxx] On Behalf Of Martin Wood-Mitrovski
> Sent: Wednesday, July 04, 2007 12:06 AM
> To: Mylyn developer discussions
> Subject: Re: [mylyn-dev] Bug or Feature
> 
> Hi,
> 
> I was just wondering about how this worked as well and would like to
> suggest
> that there could be an option for keeping the interest level of what I
> select as
> a landmark consistent even if its associated editor / viewer is closed.
> 
> For example, when working with actionscript the 'end product' is a swf
> file
> within that project which when it is run is launched within its own
> editor in
> the workspace.
> 
> So in that project the swf often needs to be closed whilst coding
> because it can
> take up a significant chunk of processor time and memory (or it may
> contain
> media like audio or video which i dont want to leave running because
> theyre a
> distraction while coding). This doesnt mean that is any less
> interesting within
> that context.
> 
> I think that if I have actually marked something as a landmark by hand
> then my
> input should be 'trusted' no matter what I do with the landmark in
> future (apart
> from of course manually marking it unimportant within this context)
> 
> You could call the option 'Always keep landmarks in context' or
> something like that.
> 
> I understand that there is the existing option of managing open editors
> but I
> dont want to forego that useful feature just because some of my files
> dont fit
> into the current scheme. :)
> 
> thanks,
> 
> Martin
> 
> 
> Jevgeni Holodkov wrote:
> >  The reason is that Mylyn by default thinks that if you have closed
> > your editor, then you have lost the interest in it, even if it was a
> > landmark. You can disable this feature via Window > Preferences >
> > Mylyn > Context - disable Manage open editors with task context.
> _______________________________________________
> mylyn-dev mailing list
> mylyn-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylyn-dev