EoS: Eclipse on Swing

EoS: Eclipse on Swing

Summary: In what has to be one of the most cleverly named projects of all time, EoS (named after Eos, the Greek goddess of the dawn) promises to bring Eclipse to Sun's Swing platform. A proof of concept download is available now.

TOPICS: Oracle

In what has to be one of the most cleverly named projects of all time, EoS (named after Eos, the Greek goddess of the dawn) promises to bring Eclipse to Sun's Swing platform.

Eclipse on Swing

EoS is the result of a collaboration between Dieter Krachtus and SWTSwing developer Chris Deckers. A download is available, but it's currently more a proof of concept than a usable system. "The most important point in my opinion was to show, that EoS is possible and will be usable," writes Dieter. "Bugs can be fixed."

With EoS, it should be possible to make Eclipse (or perhaps more importantly, Eclipse RCP applications) run on a standard JRE with no additional native code other than what's already supplied with Java. It also opens up the possibility of non-native look-and-feels, such as everyone's favorite, Napkin:

Napkin look and feel

If you haven't been following the whole story of Swing vs. SWT, and Sun vs. Eclipse, this whimsical history from Dieter should clear things up for you:

In ancient times, a GUI toolkit named Swing was crafted to outshine all its predecessors, as it was a child of Sun. However, in its infancy, like every child, Swing did crawl slowly on all fours, and few believed in it's promised future strength.

To make things worse - Swing's father Java, king and notorious philanderer hits the scene of our drama, and spawns another child: SWT, unlike his half-brother Swing, is born with native speed and beauty, sometimes compared with his half-sister AWT.

Bitter sadness took hold of Sun as her only son and heir's bright future was eclipsed by the - in her eyes - illegitimate child.

Many wars were fought over the question of the righteous successor of GUI shire. As a result, the kingdom grew weak, it's noblemen in constant quarrel and it's borders unguarded, when hostile neighbors came to pillage.

Today, as we speak, EoS brings a new "dawn" to end this war and unite the fallen out half-brothers in friendship.

Follow us and together we provide a happy ending to this story as only celluloid can deliver.

So far there has been no official response from either Sun or Eclipse. See the EoS site for more screenshots.

Topic: Oracle

Ed Burnette

About Ed Burnette

Ed Burnette is a software industry veteran with more than 25 years of experience as a programmer, author, and speaker. He has written numerous technical articles and books, most recently "Hello, Android: Introducing Google's Mobile Development Platform" from the Pragmatic Programmers.

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • why?

    I've read this article and the developer's web site a couple times now and I don't understand why they are doing this. Eclipse works fine as is. It isn't going to run better because one guy did a half-arse conversion to Swing. What next- someone converting Netbeans to SWT? I just don't get it. To each his own but this seems like an awful way to spend your free coding time.
    • Just for once...

      ... instead of "forking" a language, somebody is trying to ensure that common code is available and workable.

      This means that if I move to Eclipse I don't need to learn SWT as I know that Swing will be present and I don't need to load anything or add additional modules. It also means that if I send a project to someone else, they don't need to change their configuration just because I'm using Swing.

      This is great news. It will hopefully heal the rift between Swing and SWT and let developers concentrate on development instead of worrying which IDE is the right one to use.

      I see this move as being in line with the whole spirit of Open Source where collaboration is as important as competition.