• Blog
  • Info Support
  • Career
  • Training
  • International Group
  • Info Support
  • Blog
  • Career
  • Training
  • International Group
  • Search
logo InfoSupport
  • Latest blogs
  • Popular blogs
  • Experts
      • All
      • Bloggers
      • Speakers
  • Meet us
  • About us
    • nl
    • en
    • .NET
    • 3D printing
    • Advanced Analytics
    • Agile
    • Akka
    • Alexa
    • Algorithms
    • Api's
    • Architectuur
    • Artificial Intelligence
    • ATDD
    • Augmented Reality
    • AWS
    • Azure
    • Big Data
    • Blockchain
    • Business Intelligence
    • Chatbots
    • Cloud
    • Code Combat
    • Cognitive Services
    • Communicatie
    • Containers
    • Continuous Delivery
    • CQRS
    • Cyber Security
    • Dapr
    • Data
    • Data & Analystics
    • Data Science
    • Data Warehousing
    • Databricks
    • DataOps
    • Developers life
    • DevOps
    • Digital Days
    • Digital Twin
    • Docker
    • eHealth
    • Enterprise Architecture
    • Event Sourcing
    • Hacking
    • Infrastructure & Hosting
    • Innovatie
    • Integration
    • Internet of Things
    • Java
    • Machine Learning
    • Microservices
    • Microsoft
    • Microsoft Bot Framework
    • Microsoft Data Platform
    • Mobile Development
    • Mutation Testing
    • Open source
    • Pepper
    • Power BI
    • Privacy & Ethiek
    • Python
    • Quality Assistance & Test
    • Quality Assurance & Test
    • Requirements Management
    • Scala
    • Scratch
    • Security
    • SharePoint
    • Software Architecture
    • Software development
    • Software Factory
    • SQL Server
    • SSL
    • Start-up
    • Startup thinking
    • Stryker
    • Test Quality
    • Testing
    • TLS
    • TypeScript
    • Various
    • Web Development
    • Web-scale IT
    • Xamarin
    • All
    • Bloggers
    • Speakers
Home » Eclipse Mylar: Less is More
  • Eclipse Mylar: Less is More

    • By Peter Hendriks
    • Java 16 years ago
    • Java 0 comments
    • Java Java
    Eclipse Mylar: Less is More

    Mylar screenshotIf you work with Eclipse 3.1 or higher and you have a lot of source files in the workspace you have to give Mylar a try. Mylar (named after the material you supposed to look through while watching a solar eclipse) attempts to reduce clutter in the user interface, showing only the relevant files for the task you are working on. It does this by gathering how “interesting” some parts of your code are while you are working. Methods you change, XML files you look at, editors you click on all generate some interest and brings the file into view. Other files that are never used are not interesting and removed from view.

    I have been using this plug-in for a few weeks now on a pretty big codebase. It’s great! The filtering works very intuitive (once you find out that you really need to keep holding “Alt” down while clicking to show filtered files). It is also seems pretty robust when you refactor or otherwise change stuff. It’s like a “magic working set”, because it does everything a normal working set does, only without me having to click on a zillion check boxes over and over again: it works pretty much automagically. 🙂

    The “interesting” monitoring is, well, interesting. 🙂 The most interesting methods and classes according to Mylar are marked with bold text. The accuracy of this is pretty impressive and it is a great way to keep track of the big picture. It would be interesting to integrate the interest with stuff like code coverage (interesting methods require a higher coverage) or a class diagram generator which could quickly generate a diagram based on a specific task, but that is not possible (yet).

    Mylar has integration features for Bugzilla and JIRA but also works stand-alone. The Bugzilla integration allows you to share the task context (the “interesting” filter) of a task in the Bugzilla repository. Imagine this: I could look at some code and spot a bug. I don’t want to fix it myself for some reason and submit a bug in Bugzilla with the “interesting” info automatically gathered by Mylar. Another developer picks up this bug and the context and immediately sees only the files relevant to the problem. He fixes the bug, generating interest in some other files as well, and updates the bug (and the task context). A year and a half later I pick up the bug again because of some regression. I immediately can see what was interesting for this bug before, giving me a great head-start while dealing with the code. It seems a really useful (and effortless) extra. Too bad we don’t use Bugzilla at my current project…

     

    Share this

Peter Hendriks

View profile

Related IT training

Go to training website

Related Consultancy solutions

Go to infosupport.com

Related blogs

  • It’s Java 20 Release Day! Here’s What’s New

    It’s Java 20 Release Day! Here’s What’s New Hanno Embregts - 1 week ago

  • Exploring sustainability in tech (without the guilt-tri…

    Exploring sustainability in tech (without the guilt-tri… Hanno Embregts - 4 months ago

  • Eleven crazy learnings from the Java 11 certification: …

    Eleven crazy learnings from the Java 11 certification: … Hanno Embregts - 6 months ago

Data Discovery Channel

  • Explainable AI - Break open the blackbox

  • Toekomstvaste microservice data architecturen

  • Modern Data Platform

Nieuwsbrief

* verplichte velden

Contact

  • Head office NL
  • Kruisboog 42
  • 3905 TG Veenendaal
  • T +31 318 552020
  • Call
  • Mail
  • Directions
  • Head office BE
  • Generaal De Wittelaan 17
  • bus 30 2800 Mechelen
  • T +32 15 286370
  • Call
  • Mail
  • Directions

Follow us

  • Twitter
  • Facebook
  • Linkedin
  • Youtube

Newsletter

Sign in

Extra

  • Media Library
  • Disclaimer
  • Algemene voorwaarden
  • ISHBS Webmail
  • Extranet
Beheer cookie toestemming
Deze website maakt gebruik van Functionele en Analytische cookies voor website optimalisatie en statistieken.
Functioneel Always active
De technische opslag of toegang is strikt noodzakelijk voor het legitieme doel het gebruik mogelijk te maken van een specifieke dienst waarom de abonnee of gebruiker uitdrukkelijk heeft gevraagd, of met als enig doel de uitvoering van de transmissie van een communicatie over een elektronisch communicatienetwerk.
Voorkeuren
De technische opslag of toegang is noodzakelijk voor het legitieme doel voorkeuren op te slaan die niet door de abonnee of gebruiker zijn aangevraagd.
Statistieken
De technische opslag of toegang die uitsluitend voor statistische doeleinden wordt gebruikt. De technische opslag of toegang die uitsluitend wordt gebruikt voor anonieme statistische doeleinden. Zonder dagvaarding, vrijwillige naleving door uw Internet Service Provider, of aanvullende gegevens van een derde partij, kan informatie die alleen voor dit doel wordt opgeslagen of opgehaald gewoonlijk niet worden gebruikt om je te identificeren.
Marketing
De technische opslag of toegang is nodig om gebruikersprofielen op te stellen voor het verzenden van reclame, of om de gebruiker op een website of over verschillende websites te volgen voor soortgelijke marketingdoeleinden.
Manage options Manage services Manage vendors Read more about these purposes
Voorkeuren
{title} {title} {title}