This page discusses on the targetted hardware by OtherTuningSoftware/JTune
These Java devices compete with non-Java devices, particularly
OtherTuningSoftware/NintendoGameBoy.
The advantage of Java is portability and lower cost of development. It might justify the slightly higher cost of devices (often with smaller display).
PDA
- Palm (most all models with RS-232)
- iPaq / PocketPC / Windows CE devices (many CPUs here)
Cellular phones
For example:
- Nokia Ngage (Nokia started using Java late and started with MDIP 2.0)
- Sony-Ericsson (Ericsson had Java enabled phones a long time ago and only recently went from MDIP 1.0 to 2.0)
- Motorola V550
- Most other manufacturers still seem to be limited to MDIP1.0.
I guess that J2ME (J2 Micro Edition) and MDIP 1.0 is our minumum requirement. However, MDIP 1.0 is limited in it's connectivity. Some MDIP 1.0 devices have custom support classes for IO, but it's standardised in MDIP 2.0. J2ME seems to exclude many older PDAs. SuberWaba has a comparison page against other competitors: http://www.superwaba.com.br/en/swxj2me.asp
It might make sense to use a common middle-layer for MDIP (likely cellphones for logging / basic tuning) and SuperWaba or J2ME PDAs for tuning. Either way, we have to stop hacking and start engineering for this to be reliable. ;)
This seem like a very good start:
http://www.ericgiguere.com/j2me/index.html I don't understand the concept yet only spend a few minutes searching for information.
What are the JAVA API-s that all these support?
Related link: http://www.ericgiguere.com/articles/j2me-core-concepts.html
GUI API links please
- SuperWaba UI JavaDoc. See waba.ui http://www.superwaba.org/doc/
Communication API links please
- RXTX JavaDoc http://users.frii.com/jarvi/rxtx/doc/index.html
- SuperWaba IO JavaDoc. See waba.io http://www.superwaba.org/doc/
Hardware Emulators
- J2ME Emulator http://www.isk.kth.se/~petit/j2me/me/tutorial/index.shtml
- Palm Emulator http://www.palmos.com/dev/dl/dl_tools/dl_emulator/
See also