Screenshot of the Week: Markdown Editor

You can edit Markdown, along with other types of wiki markup, directly in Eclipse. Here’s a screenshot of the Markdown editor in action:

Edit Markdown directly in Eclipse

Edit Markdown directly in Eclipse

Note the “Preview” tab which will show you what the page looks when rendered.

This support is provided by the Mylyn Docs project’s WikiText component. You can also edit Confluence, MediaWiki, Textile, TracWiki, and TWiki formats. There’s a patch in the works to add AsciiDoc support as well.

WikiText is included in the Eclipse IDE for Java Developers and other packages.

Posted in Community, Eclipse 101, Mars, Screenshots | Tagged | Leave a comment

Screenshot of the Week: Gradle Tools

We’re pushing hard to make sure that great tools for Gradle are included with the Eclipse Mars release. The following screenshot shows my workspace after importing the Gradle Tooling API using Buildship Eclipse Plug-ins for Gradle.

The Buildship project provides tools for Gradle in Eclipse.

The Buildship project provides tools for Gradle in Eclipse.

The Buildship project is producing builds. Please add them into your Eclipse Mars environment and give them a spin. Report bugs, or contribute!

Great Fixes for Buildship will qualify for the Great Fixes for Mars Skills Competition!

Posted in Community, Eclipse 101, Java, Mars | 1 Comment

Great Fix Winners, Round Two

Sorry, I’m a little bit late with this announcement. We have three more winners in the Great Fixes for Mars Skills Competition. In no particular order:

Snjezana Peco contributed a couple of Great Fixes, but I’ll focus on the patch provided for
Bug 446075: Garbled bold text when used with icons. This patch fixes an annoying little problem that those of us using GTK 3 on Linux have had to put up with. I’ve categorized this as a “stability” bug; it’s clear that Snjezana has detailed knowledge of both SWT and GTK; and there’s no denying the impact.

Next up is Tomasz Zarna who has contributed seven Great Fixes, most of which I’ve categorized as improving stability (including one for a bug report that was filed almost twelve years ago). One example, the more recently created Bug 439041, which fixes a memory leak in progress animations. The code included in this patch itself is only a few lines, but the patch includes new test code.

Our third winner is Dirk Fauth has also contributed seven Great Fixes (there’s actually two other bugs that would qualify that I might have tagged with greatfix myself). Dirk’s fixes are all relatively small fixes that have obviously been provided by an expert. Some of the fixes improve stability in the IDE and RCP applications (Bugs 463043 and 457939). The others provide a variety of improvements that collectively improve the user and developer experiences. Dirk has substantially improved existing and added new test code that accompanies the code fixes.

Congratulations to the winners. Everybody else who has contributed a great fix is still in the competition for our third and final round. All participants will get an Eclipse shirt.

I’m encouraged that we’re starting to see at least some great fixes candidates for projects other than the Eclipse Platform. Keep these coming; fixes for all projects doing things related to improving the Java development experience qualify: Web Tools, EGit, Maven Integration, Buildship, …

Finally, one our first winners was unable to accept the prize, so we have an extra. I’ve decided that we’ll give this prize to the committer who has reviewed and accepted the most greatfix contributions (both Lars and Dani–who are prolific reviewers–have excluded themselves as potential winners).

Posted in Community, Java, Mars | Tagged , , | Leave a comment

Toggle Line Numbers in Eclipse

I’ll admit that I’m dumbfounded by how much people care about whether line numbers are on or off by default in Eclipse. Put the cursor into the gutter area to the left of the editor and right-click to bring up the context menu, select “Toggle Line Numbers” to change the state to match your preference.

Toggle Line Numbers

Most of the standard packages have line numbers turned on by default starting with Luna.

If you’d rather conserve screen space, you can just leave them off and use ctrl+L (cmd+L on the Mac) to jump to a line.

Hit ctrl+L (or cmd+L) to jump to a particular line

Or just use the debugger.

I’d love to hear what you think about everything except whether or not line numbers should be on or off by default (seriously, it’s done: time to move on). I’ll be at Devoxx France in Paris next week. Attend my talk, or visit me at the Eclipse Foundation booth (joined by Obeo and Codenvy).

Posted in Eclipse 101, Java, Mars | Leave a comment

Great Fixes for Mars Winners Part I

A Great Fix is a contribution provides a significant improvement in the Java development experience using Eclipse. Special consideration will be given to performance or stability improvements, and patches that improve the user experience. To qualify, a fix needs to be merged into the project repository by a committer.

For our first round in the Great Fixes for Mars skills competition, we have a total of 29 qualifying fixes, submitted by 9 contributors.

Here are our winners:

Andrey Loskutov

Andrey contributed twelve qualifying fixes (it’s a query, so the results may have changed since I posted this) for the Great Fix competition. Some of these contributions are significant in their own right, but together they represent a staggeringly large contribution including a broad range of performance, stability and user experience improvements. Andrey—who currently holds the #2 spot in terms of contributions made to the project in the last three months—has been invited to join the Platform UI project as a committer.

Mateusz Matela

Mateusz made a huge contribution which basically reimplemented and improved the JDT’s Java code formatter. The contribution includes 240 files changed, 8,422 insertions, 17,295 deletions. This fix improves performance and stability in the formatter, with a significant impact on the Java development community.

John Glassmyer

John contributed patches (core, ui) that fix issues with how imports are organized and sorted. His two commits change 28 files, with 3,007 net new lines of code including comprehensive changes to the JUnit tests, that fix seven separate bugs from JDT Core and UI. Some of these are long time bugs, dating back to 2004.

John, Mateusz, and Andrey all win fancy new Nexus 9 Android tablets graciously donated by Google. We’ll be contacting you shortly to confirm your co-ordinates.

All runners up will receive an Eclipse T-Shirt. All runners up are still in the competition!

The next deadline is April 1st. No fooling.

  • Deadline: April 1/2015; the three top-prize winners will be announced on April 3/2015 (Mars M6)
  • Deadline: May 6/2015; the four top-prize winners will be announced on May 8/2015 (Mars M7)

Fame and glory await!

Posted in Announcements, Community, Java | Tagged , , , , | 3 Comments

Nested/Hierarchical view of projects

From the Eclipse 4.5M5 New and Noteworthy documentation:

The Project Explorer now provides the ability to view the projects in a hierarchical (a.k.a. nested) form. For modular projects, this allows to have your Project Explorer mapping more closely the organization of your modules as they are on the file system. This hierarchical view of projects often makes easier to navigate modular projects.

Hierarchical view of projects can be triggered from the Project Explorer view menu, under the Projects Presentation item.

Hierarchical view of projects can be triggered from the Project Explorer view menu, under the Projects Presentation item

Then it makes the folders that are at the same location as a project replaced by the project, and the projects that are nested under other projects will not be shown as root elements.

This implementation relies on the Common Navigator Framework.

Posted in Java | Leave a comment

Eclipse N!

The Eclipse Planning Council—with help from the community—is trying to sort out the name for our eleventh named simultaneous release in 2016. We had some trouble with the first set of names that we selected, and so we’re into the second round.

The Lynn Lobby has significant momentum.

The “Eclipse Lynn” Lobby has significant momentum.

We started following the alphabet a few years ago, naming our fifth release “Helios“, and now we’re up to the letter N. We’ve been bouncing around some N names on Twitter; I quite like the idea of just going with “N”, and stated as much.

I originally put in the exclamation mark to make it seem more exciting, but then it occurred to me that the exclamation mark has special meaning in Lisp. In a functional programming language like Lisp, you generally avoid changing state, so Lisp functions that make changes are marked with a cautionary exclamation point (spoken as “bang”). When you invoke a bang function, things are going to change:

It seems appropriate. Change is in the air. I’m excited by the prospect of having an actual installer. I’m excited by our vision of the future of the developer’s platform.

With Mars, our June 2015 release, we’re making a subtle shift to put more focus on the user experience. This takes the form of our Every Detail Matters for Mars effort which aims to tackle a handful of “little things” like getting more of the default preferences right in our packages, standardizing naming conventions, providing reasonable and useful package-specific new and noteworthy documentation, improving the story for adding simultaneous release plug-ins into an Eclipse-based IDE, and more. I’m pretty excited about some bits of the “and more” part, but I’ll save that discussion for another day.

Of course, we’re also trying to tackle some pretty big things. We’ve come a long way towards having a proper installer for Eclipse. I’m also optimistic that we’ll be including Gradle support in Eclipse (more on this later).

We need your help and so we’ve started the Great Fixes for Mars skills competition. To enter, all you need to do is take responsibility for a bug, mark it as “greatfix”, and submit a patch. We’ve even provided a list of great suggestions where you can make the biggest impact. There’s prizes. Cool prizes.

Enter the Great Fixes for Mars skills competition; there'll be prizes!

Enter the Great Fixes for Mars skills competition; there’ll be prizes!

This shift in momentum will build through Mars and into the 2016 release. I’m certain that N-bang will usher in even bigger changes.

But what do I know? I’m just an Old Dude Who Knows Smalltalk (and Lisp).

EclipseCon 2015

Posted in Other | Tagged , , | 4 Comments