Community
Participate
Working Groups
When I right-click on a .java file I have the option of setting it as a landmark. It seems that this doesn't have any effect. What I would like to happen is for the class(es) in the file become a landmark and the file to become bold in the package explorer. This is of particular interest when using the Mylar java declaration filter so that landmarked .java files can become an indication of interesting corresponding classes. If this isn't the right thing to do then at least the option to make a file a landmark should be removed (or it should state that the operation failed). Might be related to bug #110472 (CVS ">" text decorator interfering with landmark bolding)
I've made the UI complain about setting things that can not be landmarks to be landamrks (e.g. files). I haven't gone as far as disabling this action because it is feasible that files can become landmarks at some point, so I'm marking this report accordingly. The main issue is the dual purpose that landmarks serve: 1) The are the elements that populate active views 2) They are elements that pop out as being very interesting and are included in the first degree of separation search
I would like to mark Classes and Packages as landmarks, because I would like to being able to group packages from multiple projects around one task. My plan was to improve the package-explorers filtering using Mylar. That way I could have a list of tasks that show packages from various projects that are important for that task. Ben
The current idea is that the packages become implicitly interesting by your working with their contents (e.g. methods, classes). The packages actually do end up with landmark-level interest, but it doesn't show that way because too much bold ends up appearing on the screen. But I'm not sure I understand your use case, are you talking about having mutliple tasks active, and only showing interesting packages? The Visualiser integration (http://www.eclipse.org/ajdt/visualiser/) that we have yet to release will support that since it has a package mode...
Thanks I will have a look at the Visualizer. My usecase was to create Tasks with Mylar that are not fine-granular. So I am interested in creating tasks for various scenarios in my application. The application itself is split up to more than 5 Plugins, for example a Model-Plugin, a DB-Plugin and a View-Plugin. I could think of creating one task that deals with persistance of the Model. I would then mark the various packages in the model-plugin and db-plugin as landmark. This is a bit different to just working with methods/classes and let Mylar automatically decide which classes are landmarks. My approach would be that I already know which classes make landmarks, and want to mark them interesting before working with them. As I mentioned this is a bit like Working Sets and Filters in the Package Explorer, but with far more functionality. E.g. I can quickly switch tasks from the Mylar Tasks view. Ben
I have another use case to add (actually I'm surprised nobody has entered it yet). While building web applications, I use Eclipse to edit a lot of files other than Java sources: JSPs, XMLs, Javascript an the like. These files never become landmarks, and Mylar seems to drop them from the interest view every once in a while, so I have to look them up manually. Letting important files other than Java become landmarks would certainly help.
That same use case is annoying me too. First, Mylar seems to lose interest too quickly when it doesn't know about the structure of a file (only understands Java, build.xml, and plugin.xml right now). Also those files can become landmarks, and it is sometimes useful to tag them this way manually, so we'll figure out a way to support this better for 0.5.
I also suggest to support landmark all type files
*** Bug 118007 has been marked as a duplicate of this bug. ***
I also agree that files should be able to be made landmarks. I am currently working on ruby projects and not being able to make certain ruby files landmarks is a bit of a disadvantage. ;P
Done for 0.4.10, scheduled for tomorrow. Generic files can now become landmarks implicitly, and can be explicitly set to be landmarks. Files for which structured elements within them can become landmarks (currently only .java) can not be made landmarks because the elements within them can (otherwise there would be too much bold in the Package Explorer).
