Your browser does not support JavaScript
Exit Print View

Lightweight UI Toolkit Developer’s Guide

Get PDF Book Print View

Document Information


1.  Introducing the Lightweight UI Toolkit Library

2.  Using Lightweight UI Toolkit Widgets

3.  Using Lists

4.  Table and Tree

5.  Using Dialogs

6.  Using Layout Managers

7.  Painters

8.  Using the Style Object

9.  LWUIT Implementation

10.  HTMLComponent

11.  Theming

12.  Resources

13.  Using Transitions and Animations

14.  M3G

15.  Logging

16.  Authoring Components

17.  Portability and Performance




This document describes how to work with the Lightweight User Interface toolkit.

Before You Read This Document

This guide is intended for developers creating Mobile Information Device Profile (MIDP) applications. This book is a tutorial in Lightweight UI Toolkit programming over MIDP. You should already have basic knowledge about Java™ UI libraries (for example, AWT and SWING) and understand how to use the Mobile Information Device Profile (MIDP) and the Connected Limited Device Configuration (CLDC).

For current discussion of LWUIT issues, see these online resources:

If you need help getting started with the Java programming language, try the New to Java Center:

For a quick start with MIDP programming, read Learning Path: Getting Started with MIDP 2.0:

The following sites provide technical documentation related to Java technology:

How This Document Is Organized

This guide contains the following chapters and appendices:

link iconChapter 1, Introducing the Lightweight UI Toolkit Library introduces the Lightweight UI Toolkit library.

link iconChapter 2, Using Lightweight UI Toolkit Widgets describes how to use Lightweight UI Toolkit widgets.

link iconChapter 3, Using Lists explains how to use Lists.

link iconChapter 4, Table and Tree descries the Table and Tree components.

link iconChapter 5, Using Dialogs describes how to use Dialogs.

link iconChapter 6, Using Layout Managers shows how you can use Layouts.

link iconChapter 7, Painters explains how to use Painters.

link iconChapter 8, Using the Style Object explains how to use the Style object.

link iconChapter 9, LWUIT Implementation describes the LWUIT implementation,

link iconChapter 10, HTMLComponent describes the HTMLComponent class.

link iconChapter 11, Theming describes theme elements.

link iconChapter 12, Resources describes the Theme Creator utility.

link iconChapter 13, Using Transitions and Animations describes how to use Transitions and Animations.

link iconChapter 14, M3G covers 3D integration.

link iconChapter 15, Logging details how to use logging.

link iconChapter 16, Authoring Components describes how to author a new component from scratch.

link iconChapter 17, Portability and Performance discusses general and device-specific portability issues.

link iconAppendix A, LWUIT Mini FAQ summarizes frequently asked questions about LWUIT.

Shell Prompts

C shell
C shell superuser
Bourne shell and Korn shell
Bourne shell and Korn shell superuser

Typographic Conventions

The names of commands, files, and directories; on-screen computer output
Edit your.login file.

Use ls -a to list all files.

% You have mail.

What you type, when contrasted with on-screen computer output
% su


Book titles, new words or terms, words to be emphasized. Replace command-line variables with real names or values.
Read Chapter 6 in the User’s Guide.

These are called class options.

You must be superuser to do this.

To delete a file, type rm filename.

Note - Characters display differently depending on browser settings. If characters do not display correctly, change the character encoding in your browser to Unicode UTF-8.

Related Documentation

link iconRecommended Documentation lists documentation related to this product.

Recommended Documentation
Title and URL
JSR 118, MIDP 2.0
Mobile Information Device Profile

JSR 139, CLDC 1.1
Connected Limited Device Configuration

JSR 184, 3D Graphics
Mobile 3D Graphics API for J2ME

AWT docs
Swing docs

We Welcome Your Comments

We are interested in improving our documentation and welcomes your comments and suggestions. Email your feedback to: