1 / 7

Enhancing Java Program Navigation through Degree of Interest Modeling

This presentation explores innovative methods to improve navigation within Java development environments by leveraging the Degree of Interest (DOI) model. It highlights the limitations of current navigation structures, such as flat histories and shrinking editor tabs, and advocates for a more explicit and responsive navigation experience. Key insights include the importance of tight IDE integration, user-task alignment, and visibility of structural relationships within code. Future work aims to refine DOI functionality, enhance user modeling, and support collaborative development through shared awareness of navigation.

tynice
Télécharger la présentation

Enhancing Java Program Navigation through Degree of Interest Modeling

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. pathfinderfocus+context for java program navigation Mik Kersten University of British Columbia UBC CS-533C Presentation, 2004-04-21

  2. background • Overview+details views are limited • Navigation structure is not explicit • Editor tabs shrink • Navigation history is a flat list • Idea • Model degree of interest (DOI) • Represent user navigation • Leverage program structure UBC CS-533C Presentation, 2004-04-21

  3. Attempts UBC CS-533C Presentation, 2004-04-21

  4. Inspiration • Tufte, Envisioning Information p.91 UBC CS-533C Presentation, 2004-04-21

  5. implementation • User monitor: navigation and IDE lifecycle • Map manager: DOI model and persistence • Pathfinder drawing: visualization • Pathfinder view: main UI component UBC CS-533C Presentation, 2004-04-21

  6. Lessons learned • Tight IDE integration is key • Need to augment existing views • Some views could be hidden • Predictability is important • Files appear/disappear frequently • Where to look needs to obvious • DOI stability is hard • Screen-estate effects • User-task effects • Current parameters are hand-tuned UBC CS-533C Presentation, 2004-04-21

  7. Future work • Improving DOI function & user modeling • Representing more structural relationships for OOP and AOP • Surfacing more structure, guaranteed visibility of highest DOI • Moving down to member granularity & providing semantics-based zooming • Sharing of models and awareness of others’ DOI for collaborative development UBC CS-533C Presentation, 2004-04-21

More Related