Mylar: a degree-of-interest model for IDEs

By Mik Kersten, Gail C. Murphy. Aspect-Oriented Software Development, 2005

359 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Evaluating the evaluations of code recommender systems: A reality check (2016, background): “However, existing approaches either capture data that is not appropriate to build or evaluate source-based RSSE (e.g., [10,11]) or they do not perform automated evaluations and evaluate results manually (e.g., [16]).”
The road ahead for Mining Software Repositories (2008, background): “HATARI [60], Hipikat [12], Myln [35], and eROSE [68] are examples of MSR research along this direction.”
Why don't software developers use static analysis tools to find bugs? (2013, background): “One way to allow developers to focus on making judgments about defects is to treat each warning like a Mylyn task [39], where the program elements”
A review of overview+detail, zooming, and focus+context interfaces (2009, methodology): “Investigates the value of manual elision and DOI fisheye techniques over a traditional linear representation of code.”
A Study of Visual Studio Usage in Practice (2016, background): “4) A discussion of opportunities to advance the research in IDEs and developer-assistance tools.”
Using task context to improve programmer productivity (2006, background): “Java1 code in the Eclipse2 Integrated Development Environment (IDE) is through a view of the containment hierarchy called the Package Explorer, which shows the modular structure of projects, packages, files, and classes.”