Latest messages

In our case MIDlet A was KuixMIDlet  and Midlet B was JavaME midlet.

MIDlet A and B are KuixMIDlet or simply a javaME MIDlet ?

Else There's no other UI hierarchy than the Desktop is the root widget and can contains only Screens. Other widget are completly flexibles. You can refer to the Widget Reference the see some specific internal widget hirarchy.

A Frame DOESN'T concerne the display. A Frame is only a sort of controler that permit to catch some specific action. A frame is called a frame because it could be organized into a stack (the framehandler).

By convention it could be good to associate a frame to a Screen but it's NOT the only one way to use frames.

listitem {

bg-image: url(<normal picture>);

}

listitem:disabled {

bg-image: url(<disabled picture>);

}

Everywhere Kuix invoke Graphics.drawString(...) and Font.stringWidth(...) and Font.charWidth(...) methods.

No, it isn't. Because in this case dictionnary wouldn't be available, key mapping could be wrong on some phone (look at the space character on a Nokia phone and on a SonyErricson phone ...)

Is there any plan to implement inline text input, so that it may look much better for small inputs from user.

If we were to add this feature, any inputs on which classes may have this impact..

Any plans for its support in future..

This may be nessary even to have a uniform english fonts on every devices. Currently the each phone has different rendering of the standard j2me specified fonts.

Apart from Active and Inactive back ground for the list item, we have the need for active and invactive icon for the list item.

Current we use picture to specify this icon. Would it be possible to specify the active and inactive icons to this item using style sheet. If yes, any example pl.l

Regards,
Nagendra

What is the significance of frame as compared to screen.

Below the Destop, is there a default frame or there is default screen.

Any good document on UI higherachy of containers and layouts each container supports

Regards,

Nagendra

If the application has two midlets

Midlet A and Midlet B both inherit from MIDlet.

On innovoation of Midlet A, we wanted to created Mildet B in startApp of Midlet A. This was failing in nokia.

We did this as we had Midlet B, and wanted to integrate KUIX with in its midlet. The code works fine on SonyEricson and Emualtor but not on Nokia phones.

Now that 1.0.1 has KuixInitializer, things are smooth now.

Regards,
Nagendra

All available widgets are listed in the Kuix Widget reference.

I'm not sure to understand what you mean by "..nokia phones does not allow creating a midlet class in the code" !?