Posted by brunogh
on November 20, 2009 at 7:55 AM PST
Is LWUIT going to the problem that it solved?
LWUIT was created in the Java ME world to solve an old problem related to the different UI components rendering by different mobiles. This introduction to MIDP UI can help you to understand.
From the LWUIT project:
Writing appealing cross device applications today in Java ME is challenging. Due to implementation differences in fonts, layout, menus, etc. the same application may look and behave very differently on different devices. In addition much of the advanced UI functionality is not accessible in LCDUI and requires the developer to write very low level "paint" type code. The Lightweight UI Toolkit was developed to address these issues
LWUIT offers the same high level UI components provided in LCDUI, but it does guarantee how it is renderized. But what is the problem? Why this post?! LWUIT in Java DTV is part of the specification, available through com.sun.dtv.lwuit package.
com.sun.dtv.lwuit from Java DTV specification:
Main widget package containing the component/container "composite" similar both in terminology and design to Swing/AWT. Unlike Swing/AWT a full windowing system is not applicable in this case and forms are placed using a DTVContainer passed into Plane and Screen abstractions.
So, how the industry will implement LWUIT components in Ginga?! Are we going to have a new LWUIT project to solve future LWUIT problems in DTV brazilian context? Is Java DTV LWUIT a real spec or just marketing?
Have a nice week!