Skip to main content

LWUIT released at JavaOne

Posted by terrencebarr on May 7, 2008 at 3:53 AM PDT

Picture 2.pngUpdate:

  • For more information on LWUIT, also see my previous post
  • Shai Almog, one of LWUIT's architects, has done some blog posts on technical details of LWUIT as well as a his experience doing a quick port of LWUIT to Google's Android. A must read if you're interested in LWUIT.

The Lightweight UI Toolkit was officially announced to the developer community during yesterday's JavaOne mobility keynote by Jeet Kaul (video and audio archive). An early access binary release of the LWUIT library is available immediately and the full source code will be available by summer of this year.

LWUIT is a project on and can be found here. It features screen shots, a LWUIT demo application, the early access binary download, a LWUIT tutorial, developer guide, and the API javadocs. You can start using LWUIT right away simply by adding the library to your application.

I am personally very excited about LWUIT as it offers a great new option for vastly improved rich UI development and deployment for today's mass-market devices. I have spoken to a number of developers here at JavaOne and they are all eager to try it out and see lots of potential. And once LWUIT is be available for CDC/PBP (in the near future) this finally gives the CDC platform a good option for GUI development that it has been lacking up to now.

What's more, the open source model using GPLv2 + classpath exception enables wide adoption and allows developers to port and customize LWUIT to many platforms that have previously been underserved in the UI area. And finally, the forthcoming NetBeans Matisse support for LWUIT will take drag-and-drop UI creation for mobile and embedded platforms to a new level.

So, please check out the LWUIT project. More information and sample code will be coming soon.

-- Terrence


I've just posted a more elaborate FAQ on LWUIT vs. JavaFX Mobile:

-- Terrence


netomarin is correct. The classpath exception basically means that as long as you merely *use* the functionality of the binary library for your own independent modules or applications the calling code (your app) is not subject to the GPL and don't have to open source it. For more information see:

-- Terrence

He said: "the open source model using GPLv2 + classpath exception" If we have classpath exception, so you can use it in your closed application if you just "import". If you do any change, so you have to keep it open.

If my previous assumption is correct, will LWUIT be available under a commercial license?

IANAL but the license means that you can't embed the library in a closed source app, just use it if it is available on the handset, right?


Please see my comment on FX Mobile on the FAQ of my previous blog entry.

-- Terrence

What's the advantage and/or relationship to JavaFX mobile?

LGPL doesn't allow linking for a proprietary MIDlet which GPL+classpath exception allows so you are correct the GPL+CE is less restrictive and more appropriate for mobile applications.

In that case what are the reasons to choose GPLv2 + classpath exception and not LGPL?

After going through both of them, I think that GPLv2 + CE is actually less restrictive than LGPL and more appropriate for mobile applications because of the way they are packaged. But again IANAL...

It will be good to clarify it because GPL is usually connected with dual open source / commercial licensing and LGPL is viewed as the commercial-friendly copyleft license.