It has been a while since my last post entry. We had a lot of work to do to move our project to an acceptable state. In this post, I would like to give you an overview of the project and introduce you to the new changes.
Eclipse Mars will make access to the structured selection of a StructuredViewer easier. So instead of:
ISelection selection = combo.getSelection();
IStructuredSelection sel = (IStructuredSelection) selection;
You can write
IStructuredSelection sel = combo.getStructuredSelection();
Not a big one, but one of the little annoying things. See the rest of the Eclipse papercut series
As the end of GSoC 2014 approaches, I can now say that Eclipse successfully starts in Weston. Some things look a little bit strange and I’m sure there are more bugs to work out, but for now the majority of Eclipse seems to run properly in a Wayland environment.
Every programmer knows that the Eclipse Rich Client Platform has been designed to build the popular Java IDE that can be enhanced for many more programming languages and is often used internally in business software to manage customers and products. So it boils down to just integrated development environments and enterprise resource planning. Scientists all over the world discovered: that may not be so true after all!
Approx. 3 years ago, I opened a bug report to increase the Java code formatter to 120. This is now implemented, and will be the new Eclipse JDT default for Mars.
I think that is a good sign, the Eclipse project is less and less restricted by its past.
I’m happy to announce that the final version of the “Contributing to the Eclipse Project” book has been released as paper version.
To purchase it, see for example Amazon.com or Amazon.de or see Contributing to the Eclipse Project book page for all possible sources.
A huge thanks to my reviewers: Dirk Fauth, Matthias Sohn, Sopot Çela, Hendrik Still, Thanh Ha, Wim Jongmann, Aurélien Pupier, Holger Voormann and Steven Spungin for their detailed feedback on the content of this book. I’m also very grateful to John Arthone for writing the foreword.
I triggered also the update of the Kindle version, the new version should be available soon to new and existing readers of the ebook version.
The SWT ControlExample running in Weston.
Yes that’s correct, as of this week, newly built programs using the Standard Widget Toolkit will now display in Weston, the reference Wayland compositor. Continue reading
For my new book I wanted to check how many people contributed to the platform.ui repository during the last three months:
git log –since=’last 3 month’ –raw | grep “^Author: ” | sort | uniq -c
seem to be doing the job fine.
git log –since=’last 3 month’ –raw | grep “^Author: ” | sort | uniq -c | wc -l
gives a a count for this period.
27 is the answer in case someone else is interested.
Just for reference, the PyDev developer Fabio Zadrozny just posted a nice snippet with allows you to style your SWT table headers via CSS (with your register the snippet as CSS property handler).
See the comments in Liclipse released and directly the snippet Gist snippet.
Posted in Eclipse, Lars Vogel
The JNI (Java Native Interface) is a way to link a Java program, running in the JVM (Java Virtual Machine) with a native program. This can have many uses, one of which is the ability to utilize platform-optimized code in performance critical components of an application. SWT uses this to access platform dependent GUI libraries in a platform independent way. This interface allows a user of SWT to write an application in a standardized, Java-based API, while the resulting product will have the Look and Feel of a native app. Because of this usage, SWT can be conceptually divided into two different sets of code; a standardized, developer-facing Java API, and the native code that makes it work. Continue reading