You may have noticed that Pascal Rapicault started a Kickstarter project called EasyEclipse recently. It aims to improve the Eclipse Java IDE in various ways and tries to find its niche between complete open-source and a closed-source licensing model by offering a commercial license for some features only available in EasyEclipse and giving back to the open-source version of Eclipse making Eclipse a better IDE over the time.
I am sure, every user of Eclipse has seen this message before:
As it turns out, it’s surprisingy easy to spare your users this worrying message – at least if you are building an Eclipse project rather than just a project that uses Eclipse. Thanks to Apache Maven, Eclipse Tycho and the Common Build Infrastructure effort of the Eclipse Foundation, properly signed bundles and features are just a few lines of XML away. Of course, as with all things Maven, finding the right XML incantation is not always that easy, so here’s the solution for you – ready to be copied & pasted into your project’s
In the past month, since introducing our usage tracking plugin, we have collected more than 6.000 anonymous code completion events. Thank you, Codetrails community!
This data enables us to see just how developers like you use code completion, where it helps them, and where it still might fall a bit short. Using this information we hope to improve both Code Recommenders as well as Codetrails’ tools.
So let’s answer the question: How long does it take developers to select a proposal?
So, what’s new in 0.7? Aside from several bugfixes you are in for a new
treat taglet: the “Call also” taglet. This latest addition to Livedoc’s collection of taglets (powered by Code Recommenders) provides you with documentation of the form “Developers who called m() also called …”. Have a look at how this looks for Java’s HashMap class:
Today we wish to give you an enhancement to Code Recommenders that improves code completion for constructor calls. Don’t you hate it when Eclipse only gives you an alphabetical list of all constructors it can find, not considering whether they belong to subtypes of the expected class? With the Completion Tweaks addition to Code Recommenders, subtypes of the expected type now receive a boost, pushing them to the top of the list.
Over the years, we have gotten a lot of great feedback for the Code Recommenders project. Even before its first release, this feedback has helped us a lot in adjusting Code Recommenders and later Codetrails Connect to the needs of the community. To further improve our tools and to measure the quality with which our software makes code recommendations we need even more feedback. Thus we go straight to the source of our greatest resource: You!
We want to know how you use code completion so that we can bring code completion to the next level. Learn how you can shape the future of code completion and how to take advantage of subtype-aware completion after the jump.
During the summer of 2013, Google sponsored the Eclipse Code Recommenders project with five Google Summer of Code (GSoC) student projects. Mentored by staff at Codetrails and Fabian Steeg, the students all successfully completed their objectives.
This summer I, Timur Achmetow, participated in the GSoC project “Eclipse Usage Data Collection for Code Completion” in the Eclipse Code Recommenders project. Our goal was to extend Code Recommenders with a dialog that shows users statistics about how they use code completion and Eclipse commands.
There’s been lots of news recently in the Codetrails Connect world – not the least that version 1.2 was released, bootstrapped with a rich repository of sample code.
Since June of this year, we’ve run a pilot program where individuals have contributed their code completion events to the crowd. With 15.000 code completion events in just over two months, they have build quite an extensive repository of knowledge; all implicitly collected without any effort on their part.
To make the pilot more fun, we offered 10 Raspberry Pis for participants who contributed more than 50 recommendations. Let's have a look at what our winners are using their Pis for.
During the summer of 2013, Google sponsored the Eclipse Code Recommenders project with five Google Summer of Code (GSOC) student projects. Mentored by staff at Codetrails and Fabian Steeg, the students all successfully completed their objectives.
In this blog post, I want to present the Snipmatch project, which is organized into two parts: a snippet search and completion plugin by Madhuranga Lakjeewa and a snippet editor by me, Stefan Prisca.