Open paulirotta opened 11 years ago
@vivainio The main reason to create TantalumJME-LWUIT is LWUIT has it's own Image class and some parts of Tantalum Mobile assume the platform native Image. For example, the LWUIT BBC Reader includes the adapter method we could bring into be treated as a first class platform, but we have not elevated that to be a first class package, more a special case at this point.
We can also consider TantalumAndroid-LWUIT to encourage this as one valid cross-platform path with cross-platform UI
Right now LWUIT is treated as a special case of JME in PlatformUtils, but as a result some functionality does not work out of the box. Most notable is creating a StaticWebCache of com.sun.lwuit.Image objects.
If LWUIT-JME and LWUIT-Android were promoted as "platforms" we can make some of the JME support like StringUtils work out of the box for LWUIT developers.
For example StringUtils and LWUITImageTypeHandler are currently copy-paste and modified in TantalumeLWUITBBCReaderExample were moved into the library. Each LWUIT developer creating an Image cache would need to either find or re-invent these changes. There may be a LWUIT replacement for StringUtils- not sure.
LWUIT has own Font and Image classes that hide the JME Font and Image. There may be other touch points, these are the ones I'm aware of.