In the Eclipse Neon build from yesterday you have the option to trigger a “Full Screen mode”. We added it simultaneously to saneclipse. saneclipse is a set of plug-ins to improve the user experience of the Eclipse IDE and can be installed into Eclipse Mars.
You can use the “Toggle Visibility of all Toolbars” command (via Quick Access) to hide all currently visible toolbars. Selecting the command again, reveals these toolbars again. This allows the developer to maximize the space available for editors and views. If you minimize a stack after you selected this command, the minimized stack will be visible, until you trigger the command to hide the toolbars again. This allows the developer to decide which minimized stacks are useful for him.
The following is a screenshot of the IDE with a maximized Java editor and several toolbars visible.
The next screenshot shows the same maximized editor but with hidden toolbar.
The shortcut to trigger this is Ctrl+Alt+M on Windows or Linux and Command+Alt+M on Mac.
Please note that we do not hide the main menu, we think that would be to confusing for the user, which accidently trigger this. And this command will soon be available via the Windows menu.
Combined with the upcoming shortcuts for increasing and decreasing the font size of the current editor this should make Eclipse also easier to use for people using Eclipse for presentations.
On behave of the http://www.vogella.com/company/ I’m happy to announce that we joined the Eclipse Foundation. While our employees were already heavily involved with the Eclipse open source framework since several years, this step makes our company commitment official.
We work on almost all Eclipse Platform projects and we are happy to currently be the second strongest contributor to the Eclipse Platform.
We are also leading the Eclipse Platform UI project and it is great to see more and more new people coming in and help with the project. Still we remain very active in this project and it is great for us to see that we are currently doing more than 50 % of the commits in Platform UI.
Many of our customers are using the plug-in development tools, we are also heavily involved in them.
But of course that is not all, we believe that it is important to also help other projects to improve the Eclipse IDE experience, so we contribute to various projects. Our Eclipse vogella GmbH company page lists the projects we are involved in, here is a current snapshot.
We definitely love the Eclipse Platform and are very impressed with the skills in the Platform team, we are looking forward to work closer together with the Eclipse Foundation. We also hope to continue and intensify our efforts in improving the Eclipse IDE and Platform experience and are looking for qualified developers located in Germany, fulltime or part time (students).
Based on the work of Mickael Istria we added shortcuts for increasing and decreasing the editor font size to Saneclipse.
Install the latest version from https://dl.bintray.com/vogellacompany/saneclipse/ and enjoy Ctrl++ or Ctrl+- for changing the font size.
We hope to integrate Mickaels change into Neon.
I would like to welcome Tony McCrary as platform.ui committer.
Tony is the amazing guy behind the new Eclipse icons which look way better on a dark background. He has drawn these svg icons and created a Maven renderer to convert them into png files. I have not counted these icons recently, but the last time I looked he created more than 1500 icons. And Tony stayed in for several years, even though he got little thanks from the projects he contributed the icons to. Certain projects which received hundreds of icons complained about errors in 1-2 icons, instead of saying thank you.
Thanks Tony, for having such a thick skin.
Tony is also a kick-ass developer and maintain his closed source SWT port based on Open GL. Scary stuff if you ask me.
I would like to welcome Jonas Helming as platform.ui committer.
Jonas was the driving force behind the migration of the e4 tools to platform.ui and uses his awesome Eclipse modeling and programming skills to improve the e4 tools and the platform. Jonas is also helping actively with incoming Gerrit reviews.
I found the nice Git repo for the gitdm tool to do Git commit statistics. In addition the mr tool allows to extract logs from multiple repositories.
Combining both let me extract the Git statics of platform UI relatively easy. Here is the command for last August:
mr log -p -M --after="2015-8-1" --before="2015-9-1" | ../gitdm/gitdm -b ../gitdm/
Processed 68 csets from 16 developers
15 employers found
A total of 8722 lines added, 10823 removed (delta -2101)
Developers with the most changesets
Lars Vogel 25 (36.8%)
Simon Scholz 6 (8.8%)
Brian de Alwis 6 (8.8%)
Dirk Fauth 5 (7.4%)
Markus Keller 4 (5.9%)
Stefan Xenos 4 (5.9%)
Matthias Becker 3 (4.4%)
Alexander Kurtakov 3 (4.4%)
Dani Megert 3 (4.4%)
Patrik Suzzi 2 (2.9%)
Sopot Cela 2 (2.9%)
Dariusz Stefanowicz 1 (1.5%)
Christian Radspieler 1 (1.5%)
Christian Georgi 1 (1.5%)
Daniel Haftstein 1 (1.5%)
Jonas Helming 1 (1.5%)
Developers with the most changed lines
Lars Vogel 4295 (34.9%)
Stefan Xenos 3266 (26.6%)
Markus Keller 1662 (13.5%)
Dirk Fauth 1107 (9.0%)
Simon Scholz 714 (5.8%)
Brian de Alwis 439 (3.6%)
Jonas Helming 389 (3.2%)
Alexander Kurtakov 228 (1.9%)
Matthias Becker 139 (1.1%)
Patrik Suzzi 37 (0.3%)
Sopot Cela 8 (0.1%)
Christian Georgi 6 (0.0%)
Dani Megert 5 (0.0%)
Daniel Haftstein 2 (0.0%)
Dariusz Stefanowicz 1 (0.0%)
Christian Radspieler 1 (0.0%)
Developers with the most lines removed
Lars Vogel 2382 (22.0%)
Dirk Fauth 352 (3.3%)
Simon Scholz 236 (2.2%)
Markus Keller 159 (1.5%)
Alexander Kurtakov 80 (0.7%)
Daniel Haftstein 1 (0.0%)
I like these statistics, as they are much more detailed compared to Eclipse Platform UI.
Inspired by the Eclipse start optimisation by Alex Blewitt post, I traced my environment and reworked our Eclipse Tracing tutorial section to enable others to do the same.
On my machine starting the Eclipse IDE (with only the SDK, XML editor and Git installed) takes 4317 ms. Looking at the “bad” guys it looks like Eclipse could start approx. 18 % faster if PDE and JDT would not activating themself. If opened Bug for JDT core and Bug for PDE.
If case you experience long startup time in your setup, I recommend to turn on the tracing option and if you see a slow starting component, to open a bug report or code correction for it. In most cases removing the activator (and moving its logic to another place which is lazy initialized) should speed up the start process.
If you are using the latest Eclipse development build and looking for the correct update site, you can check the following Eclipse Project Update Sites wiki.
Since a little while Eclipse Platform also offers stable links for its update sites which are also listed on this wiki, see Bug.
I’m personally happy that the next Eclipse release will require Java 1.8 to run. See official email to the cross mailing list for the public announcement of this.
Several Eclipse projects like m2e and Jetty have already moved to Java 8. This moves allows us in the Eclipse platform to use the improved Java 8 API to modernize and optimize our code base and will hopefully make the Eclipse project even more interesting for potential Eclipse contributors.
After all, who wants to work in his unpaid time with an outdated Java version?
Some people claim it is relatively hard to contribute code to an Eclipse platform project (without Oomph). But even without additional tooling is actually very easy to setup the necessary configuration to contribute to Eclipse platform UI.
Here are the necessary steps:
Create and configure an Eclipse user
Clone the Eclipse platform UI repo
Configure your Eclipse workspace
Make a change and publish it
If I put these instructions on A4 paper, they take 5 pages, including lots of screenshots.
Based on our experience during Eclipse Hamburg Hackathons, this setup usually takes less then 10 minutes for an unexperienced users, plus the time you need to clone the Git repo.
This setup used to be more complex in the past but we constantly work on making it simpler. Also a big thanks to the Eclipse Git tooling project which makes the configuration as seamless as possible.