Is there a way i can display fully qualified class names for the debugger's callstack?
E.g. rather than this:
I would like to have the packages of the classes included - like where the green boxes remain here:
(NOTE: Actually i dont care where they are displayed as long as there is a easy way to determine the package of a class in the callstack)
Motivation:
I am currently working on legacy systems where there is multiple layers of frameworks (both self-made as well as old stuff like Struts 1.1.), service components etc. etc. and i try to figure out the first point our code is included in some way). Since there are now about 100 Projects in my Eclipse -all with their Maven dependencies - things get complicated by just "Link with Editor" and see where the according class is placed in.
What i tried:
Aprox. 20min Webresearch (incl. reading the SO questions/ answers recommended when i created this question) without any remarkable results.
Using my entire design skills combinated with my 15+ years of MS Paint experience i drew the above images (Feel free to add those stunners to your art collection).
Does this help? In the upper right-hand corner of the Debug (callstack) view, click the menu button (the upside down white triangle), then Java, then see the 'Show Qualified Names' option.
Related
Sorry for my vague question, but I'm missing the words to be more to the point. That's part of my question.
I'm using Eclipse Mars. Several views display little images next to, e.g., project names. Furthermore, these images are enriched by additional graphical features, depending on the properties and states of the entities they are attached to. So,
How are these images called?
How are the additions called?
How do I find out, what a specific addition means?
For example, I have no clue about the meaning of the strange antlers on the bottommost image in the following screen.
They are called 'decorations' or 'decorators'. They are added by various plugins to provide additional information about the file / folder / projects. Decorations can also be added to the beginning or end of the label text.
For example the first three projects in your image are Java projects (small J at the top right), they are under source control (bottom right image) and they all have some warnings about problems (warning sign at the bottom left).
You can control the display of many of these images in the Preferences in the 'General > Appearance > Label Decorations' page. Other decorations are controlled in other preference pages specific to the plugin that provides them (for example 'Team > SVN > Label Decorations').
Because they are added by many plugins it is hard to give a list of what they all mean. This answer lists some of them.
Plugins use the org.eclipse.ui.decorators to declare decorations.
I'm not sure but my guess is the 'strange antlers' decoration are because you have an ANTLR project.
Here's the official icon reference for the basic icons and decorators.
Plugins (including standard plugins) will add additional decorations. For example, the ones used by Git are listed in Preferences>Team>Git>Label Decorations, along with a key. You can enable/disable plugin-specific decorations in Preferences>General>Appearance>Label Decorations.
The antlers in your selected icon are from the ANTLR plugin. So that project is an ANTLR project (as well as being a Git-tracked project that causes a warning, per the other icons).
I hope that helps!
I noticed #javadoc view in my eclipse. Could you please tell me what is the use of this and how to use it.
Eclipse actually does provide decent tools for creating your own JavaDoc, which is a good idea, as then others who have to use your code will have the ability to see what it does.
There is a keyboard shortcut for adding a block for a class or method (on Mac it's Command-Shift-J I think, but search Javadoc in the key mappings.
You can define templates for adding things like links, which are pretty important, that make creation of JavaDoc go very quickly
When you document in Eclipse, it is intelligent enough to point to existing docs, so say you make an interface, you document the methods in the interface, then inside each implementer, if you created them after the interface, you will get a block that points you back to the interface
When you have added your own, or other people on your team have, this view let's you see what that will look like, so it's got a dual purpose: for making it easier to read the markup of others' JavaDoc, and for previewing your own.
The view you are showing is the Eclipse # Javadoc view. The Javadoc view shows the Javadoc of the element selected in the Java editor or in a Java view.
To use it, simply open a Java file that contains Javadoc in the Java view (or use the Java perspective). Once you do so the Javadoc view will automatically populate.
I am using Eclipse (Indigo) for Java development. My personal, idiosyncratic style prefers to see Java methods one-at-a-time, instead and not as a region of a longer .java file.
I am looking for a preference, view, or plug-in that shows me a java method, and only that method, when I select the method name from a explorer or browser. For reference, here is a screen-shot of a typical Smalltalk browser (Cincom's VisualWorks). The "Method Code Area" shows on only one methods as opposed scrolling through all methods in the class.
The Java Browsing Perspective comes close to a Smalltalk browser. I customized it a little bit and found it very useful.
Enable 'Show Source of Selected Element Only' and you will see only the selected method.
On today's widescreens, you won't need the whole width for the method source, and projects and methods take some vertical space. So I decided to vary the original Smalltalk layout.
Make sure that Eclipse closes open files automatically, as you want to browse, not to open and close files.
One thing that is missing is the 'Protocol' view. Maybe the developers had something like that in mind while introducing the #category Javadoc tag, but the only thing you can do is to filter by category. I hope that some lucky day someone will develop a protocol view.
Is there a way in eclipse to assign certain files a colour (much like OSX's Finder):
Such that opened editor's tabs are assigned the same colour - (and maybe even the text editor's background
For instance if I am working with MVC, I could assign all the Models blue, all the Views Green, Mediators Yellow etc...
I can't find one, but it seems so natural/obvious to me I thought I'd better ask.
Else, does anyone else have problems visually grouping th
Kind of...
Please have a look at Andrei Loskutov's Extended VS presentation plugin which, as its name suggests, is a Visual Studio skin for Eclipse. It has some tab colouring features (although may be the one you describe).
On a general note Andrei's eclipse plugins have, since version 2.x, garnered a lot of well deserved praise...
I'm working on some reflection stuff using Java across XML files. The process would be made much faster and less prone to error if I could get content assist to behave like a tree in a small window off to the side, but more than by my current cursor location.
My question is can this really be done without reinventing the wheel too much? Essentially I want to display a list of classes, choose a class, then drill down a TreeView similar to the outline view Eclipse has for a current open file and at some point I click a button below and it generates the desired XML formatted text I would have typed manually, this is generated based on whatever in the tree I have highlighted.
I've designed and begun work on the front and back end, but the piece that keeps eluding me is harnessing Eclipse's content assist to gather a list of practically anything I could possibly call in a given project.
Can this be done? I've been combing Eclipse's documentation for a few days and fighting with the source download dying halfway repeatedly.
I am not 100% if that's it but I had an eclipse plugin with spider in it's name in mind, which does what you described.
Maybe it is this one: http://eclipse-plugins.2y.net/eclipse/plugin_details.jsp?id=202
Furthermore when writing Eclipse plugins, it is useful to press ctrl+shift+f1 (eclipse plugin spy) once having worked in the pde this should be possible.
It shows you info about all possible extensionpoints refering to your current view.