What is New & Noteworthy for an Eclipse Release is the topic of most of the talks we see at conferences. We see all the new features, we may talk about fixed bugs in the last release and about that the project team could do in the future. But what happens behind the scenes? How does the Eclipse community - with the help of the Foundation, the committers, contributors, and users - build a highly sophisticated software platform? What are the obstacles (from technical ones to legal)?
Nowadays more than 2,2 billion users worldwide use Internet, daily, from any kind of device and most of the business relies on the Internet as an “all-in-one” infrastructure spanning from data management to computational system. This means that the Internet as it was conceived more than 30 years ago may not be any longer suitable for today and future foreseen expectations and new ideas must be conceived and substantiated. These new ideas are embraced and materialized under the Future Internet concept.
The ability to build effective and efficient development studios is a major challenge for large companies nowadays.
For several decades, IFP Energies nouvelles (or IFPEN) has been developping scientific softwares in the field of geosciences. This old generation of monolithic softwares is progressively being replaced by a new generation of full-featured, geoscience software solution which is used by the oil and gas industry. The innovative nature of this scientific software solution comes from the fact that the desktop part is entirely based on Java and the Eclipse RCP framework.
On UNIX/Linux based platforms, SWT (Standard Widget Toolkit) currently supports the GTK+ 2.x
release stream as its underlying native widget toolkit. Modern distributions have however,
started adopting the GTK+ 3.x release stream which brings in many improvements viz. use of Cairo
vector graphics library throughout, upgraded input device handling with XInput2, CSS based theme
APIs, experimental Wayland and HTML 5 backends, and support for touch devices, apart from a bunch
of new fun and useful widgets as well. In order to take full advantage of these new features and to
With the new dependency injection framework provided with Eclipse 4 you can inject services anywhere you need them. Context Functions can be used for providing the specific implementation to the interface. The special thing about them is that this relation can be a function of the Eclipse Context's state rather than a predefined, hard-wired Interface-Implementation connection.
By design the framework makes it possible to customize the way this wiring is made. This ability opens up a wide range of dynamics which can be performed in the process of selecting the service implementation.
Building a product is hard, building a platform is even harder. In this session, we will have a look at the technical and organizational challenges that Service2Media faces while developing an Eclipse-based IDE that supports their cross-mobile solution called M2Active. With M2Active, a developer can create applications for mobile platforms (iOS, Android, Blackbery, J2ME, Windows Phone) using the 'define once, deploy anywhere' principle.