GUI Design in J2ME

I recently delved into Mobile Programming, I practically tried the J2ME Polish GUI ,

Although the GUI with the Polish language looked pretty decent, I realized that the user interface was not what I was looking for.

I started scourging the Web most of all for Qaru and formulated certain rules:

  • Java ME is ubiquitous, so it would be a good runtime to start programming.
  • The GUI frame should be such that it gives me full control over drawing on the screen at a lower level a la Flash for desktop computers.
  • The application must be portable in accordance with WORA and work on various phones, regardless of resolution, screen size, etc.
  • Animation support.

In my search for a finite GUI based on the above rules, I found some more Polish ones, such as LWUIT, MiniME, Nemo. Although I could not try them.

What GUI framework would you recommend in accordance with the rules stated above ?.

+4
source share
4 answers

I think that it is best to write your own GUI in j2me, with all the necessary functions, nothing more. Thus, you save a space that does not have what you do not need.

+4
source

I used LWUIT a while ago. It provides many useful widgets and allows you to place content on the screen using layout managers similar to those used in Swing. In addition, it provides a tool for tezing your GUI in a rather complicated way. It is worth a try! I could understand almost every graphic idea that I had in mind. Almost ... that was a problem for me. I guess which of the GUI tools you use, if you have specific ideas about how your GUI should look and look, you will end up losing some features and probably get better at writing your own little structure, as Lucas said.

+1
source

Using your criteria, I would like to compare the library that we are currently using, called the J2ME GUI, which you can read at http://www.garcer.com/ .

  • It is in Java and is intended for MIDP2.0 / CLDC1.0 devices.
  • Its predefined components can be extended, and then you can override their Paint events to create any component of your choice.
  • Compatibility is one of its main functions, ensuring the smooth and compact operation of low-cost phones.
  • Animation is not directly supported in the version that I am currently using. It can be implemented by creating an animation component and using the built-in timer events. This is how we are currently planning to implement an animated download icon in one of our new projects.

Hope this helps.

+1
source

Although this is an old post, if you eventually built your own infrastructure, I still think you should try LWUIT. The developers are not idle at all - LWUIT in 2009 is not the same as LWUIT 2011, and they promise that LWUIT in 2012 will be much better! Among the features of LWUIT are the following:

  • The ability to develop once, and the port is everywhere [almost - iphone porting is one of the gifts we receive in 2012]. This is trully Java!
  • Animated, animated, and other animations are possible in LWUIT
  • Low-level devices are also serviced.
  • IOs (file system, storage, and network connections) were abstracted to allow easy porting without the need to edit code for each platform. Connections are buffered, XML and JSON parsing can be performed without problems.
  • The theme creator (resource editor) is so awesome - the developer just needs to finish creating the GUI, and all that remains to be done is to insert the functionality codes! He also creates a Netbeans project for you that already contains 4 ports [Desktop, MIDP, RIM, and RIM Touch].

For anyone who comes across this Q, or even the original question (is that a word?), I think you should try LWUIT

+1
source

All Articles