RE: [mylar-dev] Interest calculation rules

["Mik Kersten" <beatmik@xxxxxxx>]

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Igor Fedorenko
...
> Linking with editor does not help with new projects and folders as no
> editor is opened upon their creation.

That's right, so I added:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=115903

> I am not 100% convienced about "has to be triggered by user" part yet.
> More specifically, I am very interested in all locally changed files (as
> in "compared to version from CVS") and I do not really care if I changed
> these files directly, they were changed as a result of refactoring or
> were changed on filesystem. Not sure what is the desired behaviour here...

Yes, there is also a case for things that weren't changed directly.  I the
model it's called "predicted interest" and the originator of the interest is
a tool and not the programmer.  So it would be very straightforward to add a
mechanism for inducing interest on every element that changed as the result
of a refactoring.  I have some ideas about how that could be useful in the
long term (e.g. Mylar could keep the AST for all predicted interest elements
in memory and make refactorings not require a search) but I'm much less
clear on UIs for exposing this kind of structure.  Other than the current
Active Search which can show you what will change as the result of common
reference and hierarchy refactorings.  If you have any other ideas please
post them or create a bug report.

Mik
 
--
Mik Kersten, http://kerstens.org/mik
Mylar project lead, http://eclipse.org/mylar