Proceed to GeoCommunity Home Page


SpatialNewsGIS Data DepotGeoImaging ChannelGIS and MappingSoftwareGIS JobsGeoBids-RFPsGeoCommunity MarketplaceGIS Event Listings
HomeLoginAccountsAboutContactAdvertiseSearchFAQsForumsCartFree Newsletter

Sponsored by:


TOPICS
Today's News

Submit News

Feature Articles

Product Reviews

Education

News Affiliates

Discussions

Newsletters

Email Lists

Polls

Editor's Corner


SpatialNews Daily Newswire!
Subscribe now!

Latest Industry Headlines
Orbit GT and Geosense, South Africa, sign Reseller Agreement
TC Technology Announces MIMS 2017
Public-Private Partnership to Open Geodata Access for African Resource Development
CoreLogic Launches SkyMeasure Mobile App for Roofing Industry
TCarta Marine to Introduce Gulf of Mexico Streaming Basemap Service at Esri Petroleum Conference

Latest GeoBids-RFPs
Cartography Training-VA
A & E Services-OR
Remote Sensing-UT
Surveying and Mapping-WA
GPS Locators-MN

Recent Job Opportunities

Recent Discussions
DEM to DTM in Inroads
GZ File
LiDAR-derived DEM
space syntax
DEM data for Israel
INDEX
* Introduction
* Building Clients For Multiple Platforms
* Implementation and Lessons Learned

Serious Java Programming For The Wireless World

by Shiuh-Lin Lee

In this article, I assume that readers are already familiar with the Java KVM (K Virtual Machine), and I wonít spend time discussing the benefits of KVM applications in the wireless world. If readers are interested on those missing topics, there are several good articles that can be found in the reference section. In this article, I will mainly address the experience gained from a port of my full-featured GIS (Geographic Information System) program from the Java SE (Standard Edition) to the Java ME (Micro Edition) KVM environment.

In 1997, I implemented an Internet Java GIS applet program, JShape, which allows users to load GIS, CAD or image data from the web server and display them on the userís web browser screen. After Sun introduced KVM, in the latter portion of 1999, I ported JShape to the Java Micro Edition CLDC (Connected Limited Device Configuration) Palm KVM environment as KShape. Also, in the early months of 2000, I implemented a new MShape GIS program, which can run on a Java Micro Edition MIDP (Mobile Information Device Profile) Motorola iDEN phone environment. Due to the different computing environment, the resulted programs have several different features. The following table explains the major differences between Java SE and Java ME (CLDC and MIDP).

Details Java SE Java ME - CLDC (Palm) Java ME - MIDP
Hardware Type PC, Workstation Handheld device, PDA Cellular Phone, Pager
CPU Speed 100+ MHz 16-20 MHz (slow) Very Slow
Program Memory Size 16+ MB 128-256 KB Less Than 128 KB
Storage Size 1+ GB 2-8 MB Less than 256 KB
Display Size 640x480 pixels + 160x160 pixels 100x100 pixels
Internet Connection Speed 56.6 KBps + 19.2-33.6 KBps for regular modems; 14.4 KBps for some wireless modems 9600 KBps
Java Class Library Full Subset Subset
GUI Class Library AWT, Swing N/A N/A
Internet Connection Class Library HTTP, Socket, Datagram Socket Datagram
Math Class Library Yes N/A N/A
Float/Double Data Types Supported N/A N/A
Implemented GIS Program JShape KShape MShape

Next: Building Clients For Multiple Platforms


Sponsored by:

For information
regarding
advertising rates
Click Here!

Copyright© 1995-2014 MindSites Group / Privacy Policy

GeoCommunity™, Wireless Developer Network™, GIS Data Depot®, and Spatial News™
including all logos and other service marks
are registered trademarks and trade communities of
MindSites Group