Eclipse Ugly (from vim recovery user)

Question

So, I finally plunged into using eclipse from vim ... but I was having serious problems with an incredibly cluttered interface and menu system. Example: right-clicking in the main text area gives a submenu with ~ 30 elements ... The whole eclipse environment seems bulky and rather ugly.

I painstakingly changed the fonts and colors, and it bothers me that the settings are full in the entire settings window. I would like to have quick color scheme settings, such as emacs and vim, that have been around for decades. Through stackoverflow, I found:

http://blog.codefront.net/2006/09/28/vibrant-ink-textmate-theme-for-eclipse/

But I would like some more examples! Something like a skull or slate.

Does anyone have a secret to making eclipse a more useful tool with a more aesthetic interface?

Answer 1

Well, if you miss vim so much and just want to get extra Eclipse features, have you considered eclim ?

The main goal of eclim is to provide Eclipse functionality to the Vim editor. The initial goal was to provide the Java functionality of Eclipses in vim, but support was added for various other languages ​​(c / c ++, php, python, css, html, xml, etc.) and several more are planned.

Eclim is not so much an application as an integration of two great projects. The first, Vim, is arguably one of the best existing text editors. The second, Eclipse, provides many great development tools in different languages. Each of them provides many features that can enhance developer productivity, but both still leave much to be desired. Vim does not have native Java support and many advanced features available in Eclipse. Eclipse, on the other hand, still requires the use of a mouse for many purposes, and compared to Vim, it provides by no means an ideal interface for editing text.

This is where eclim comes into play. Instead of trying to write an IDE in Vim or a Vim editor in Eclipse, eclim provides an Eclipse plug-in that provides Eclipse features through a server interface, and a set of Vim plug-ins that communicate with Eclipse through that interface. This functionality can be used in three main ways, as shown below.

1. The first scenario is for those for whom vim is their main editing interface. In this scenario, you run a headless eclipse instance with which all vim instances can exchange data to provide various eclipse functions.
2. The second scenario is for those who prefer to use vim as their primary interface, but often end up returning to eclipse for any functions not provided by eclim. In this case, you can start the eclim server inside the eclipse GUI and then interact with it through external vim instances, as in the first scenario.
3. The last scenario is for those who want to use the eclipse interface all the time, but want to use gvim as the built-in eclipse editor. As in the previous use case, the eclim server starts inside the eclipse GUI and the built-in gvim will interact with it in the same way as external vim instances do.

Answer 2

If you think the Eclipse context menu is large, you don’t see that Eric xD

Color schemes are not so bad, I think you can save your combinations, so there should not be a serious problem to pack your favorites to keep them from one system to another.

And in the end, think that most "normal people" (not geeks grown with Unices). Vim is just awful ... and Emacs can make your fingers dislocate.

Answer 3

Do not forget to "maximize" the option on the editors tab : it is very useful if you want to highlight the entire "clutter" graphical interface, presented by all other opinions.
These views are still accessible through the icons on the side, but you can only work in one (or several) editors and focus only on them:

alt text http://blogs.infosupport.com/photos/peterhe/images/12528/original.aspx

A huge victory for me is how now you can maximize and minimize work.
Previously, maximizing an editor filled one editor all over the screen.
If you work on a widescreen monitor, for example, on my laptop, this leads to a lot of spaces, which is not very useful.
In Eclipse 3.3, tiling editors are saved when maximized. This makes it easy to place my unit test editor and code next to each other, so when I type tests, I can very easily check the code I'm testing

In addition, submissions are minimized and not completely hidden.
Many people don’t even know that you can minimize the idea, because prior to Eclipse 3.3, minimization didn’t make much sense. It was completely horizontally oriented, which means that it usually just looked weird and empty.
When minimized in Eclipse 3.3, views now behave more like “fast views” and always really minimize. All this works very well, because much less need to switch maximization / recovery to look at the view, especially in combination with quick access .

Answer 4

You can change a lot through plugins ... btw, what language do you code in? JAVA? Then try Netbeans.