Old Java Mobile Games

[Edward]

Javafor Mobile Devices is a set of technologies that let developers deliver applications and services to all types of mobile handsets, ranging from price efficient feature-phones to the latest smartphones.

CLDC is a Java Community Process effort that has standardized a portable, minimum-footprint Java building block for small, resource-constrained devices. CLDC runs on top of Sun's K Virtual Machine (KVM) that is provided as part of this release.

The platform uses the object-oriented Java programming language, and is part of the Java software-platform family. It was designed by Sun Microsystems (now Oracle Corporation) and replaced a similar technology, PersonalJava.

The platform used to be popular in feature phones, such as Nokia's Series 40 models. It was also supported on the Bada operating system and on Symbian OS along with native software. Users of Windows CE, Windows Mobile, Maemo, MeeGo and Android could download Java ME for their respective environments ("proof-of-concept" for Android).[4][5]

Originally developed under the Java Community Process as JSR 68, the different flavors of Java ME have evolved in separate JSRs. Java ME devices implement a profile. The most common of these are the Mobile Information Device Profile aimed at mobile devices such as cell phones, and the Personal Profile aimed at consumer products and embedded devices like set-top boxes and PDAs. Profiles are subsets of configurations, of which there are currently two: the Connected Limited Device Configuration (CLDC) and the Connected Device Configuration (CDC).[6]

Oracle provides a reference implementation of the specification, and some configurations and profiles for MIDP and CDC. Starting with the JavaME 3.0 SDK, a NetBeans-based IDE supported them in a single IDE.

In contrast to the numerous binary implementations of the Java Platform built by Sun for servers and workstations, Sun tended not to provide binaries for the platforms of Java ME targets, and instead relied on third parties to provide their own.

The exception was an MIDP 1.0 JRE (JVM) for Palm OS.[7] Sun provides no J2ME JRE for the Microsoft Windows Mobile (Pocket PC) based devices, despite an open-letter campaign to Sun to release a rumored internal implementation of PersonalJava known by the code name "Captain America".[8] Third party implementations are widely used by Windows Mobile vendors.

Operating systems targeting Java ME have been implemented by DoCoMo in the form of DoJa, and by SavaJe as SavaJe OS. The latter company was purchased by Sun in April 2007 and now forms the basis of Sun's JavaFX Mobile.

The open-source Mika VM aims to implement JavaME CDC/FP, but is not certified as such (certified implementations are required to charge royalties, which is impractical for an open-source project). Consequently, devices which use this implementation are not allowed to claim JavaME CDC compatibility.

The Connected Limited Device Configuration (CLDC) contains a strict subset of the Java-class libraries, and is the minimum amount needed for a Java virtual machine to operate. CLDC is basically used for classifying myriad devices into a fixed configuration.

A configuration provides the most basic set of libraries and virtual-machine features that must be present in each implementation of a J2ME environment. When coupled with one or more profiles, the Connected Limited Device Configuration gives developers a solid Java platform for creating applications for consumer and embedded devices.The configuration is designed for devices with 160KB to 512KB total memory, which has a minimum of 160KB of ROM and 32KB of RAM available for the Java platform.

Designed for mobile phones, the Mobile Information Device Profile includes a GUI, and a data storage API, and MIDP 2.0 includes a basic 2D gaming API. Applications written for this profile are called MIDlets.

JSR 271: Mobile Information Device Profile 3 (Final release on Dec 9, 2009) specified the 3rd generation Mobile Information Device Profile (MIDP3), expanding upon the functionality in all areas as well as improving interoperability across devices. A key design goal of MIDP3 is backward compatibility with MIDP2 content.

The Information Module Profile (IMP) is a profile for embedded, "headless" devices such as vending machines, industrial embedded applications, security systems, and similar devices with either simple or no display and with some limited network connectivity.

The Foundation Profile is a Java ME Connected Device Configuration (CDC) profile. This profile is intended to be used by devices requiring a complete implementation of the Java virtual machine up to and including the entire Java Platform, Standard Edition API. Typical implementations will use some subset of that API set depending on the additional profiles supported. This specification was developed under the Java Community Process.

The ESR consortium is devoted to Standards for embedded Java. Especially cost effective Standards.Typical applications domains are industrial control, machine-to-machine, medical, e-metering, home automation, consumer, human-to-machine-interface, ...

I was wondering if there is an Integer class that will allow you to store such a number starting with 0417254482. Perhaps using a string be a more appropriate?At present when I'm trying to use represent a phone number with ints, doubles longs I seem to store random numbers and not the numbers I meant to store.

Use String. Aside from anything else, you won't be able to store leading zeroes if you use integers. You definitely shouldn't use int (too small) float or double (too much risk of data loss - see below); long or BigInteger could be appropriate (aside from the leading zeroes problem), but frankly I'd go with String. That way you can also store whatever dashes or spaces the user has entered to make it easier to remember the number, if you want to.

In terms of the "data loss" mentioned above for float and double - float definitely doesn't have enough precision; double could work if you're happy that you'll never need more than 16 digits (a couple fewer than you get with long) but you would need to be very, very careful that anywhere you convert the value back from double to string, you got the exact value. Many formatting conversions will give you an approximation which may be accurate to, say, 10 significant digits - but you'd want an exact integer. Basically, using floating point for phone numbers is a fundamentally bad idea. If you have to use a fixed-width numeric type, use a long, but ideally, avoid it entirely.

Think about this: Is a phone number really a number? Does it make sense adding (or make another arithmetic operation) with phone numbers? Phone numbers are codes, they're usually represented with numbers, but that's just a convention and, maybe, in another country the use letters too (I've just realized, what about international phone numbers? they have a + at the beginning.You have to think about the nature of the things you want to represent, and then, find the most suitable representation.

The main reason is that the operations that you can do on phone numbers are lexicographic, and not arithmetic.e.g. You can say that phone numbers for France start with +33, but you cannot assume they are in a numerical range.

In the constructor, the number is string but when you call the constructor you used an int for phone number. There must have been a compile error here in java I think. Is this the same code you compiled?

Java applications are run on a java virtual machine, which is what allows them to work on multiple platforms. However, android sdks have quite a few additional libraries and features pertaining exclusively to an android-compatible application that would make direct porting to windows impossible without adaptation.

That said, there are libraries which when used will allow an application for android to work on windows, with the exception to features of the android phone which obviously absent when run on windows. My guess is these libraries would provide a means to distinguish, but ideally you would want to distinguish as little as feasibly possible.

So in short no, not without some adaptations. If you're considering creating a program which will work on both, I would recommend you first find one such library, as it will be far more difficult to change later.

This is a framework written by Facebook that allows you to write mobile applications that work on both platforms using javascript. If you wish to learn about React Native I would recommend using the website Udemy and searching for React Native. The courses are cheap and they are packed with information.

Yes, prior to Android Lollipop, You can run JVM application with some efforts. After Android Lollipop, there were some changes in Android Core system like it now uses ART(Android RunTime) instead of Dalvik. So, this divided the apps which can safely run JVM programs on Android into two parts, one which supported Android versions prior to Lollipop and others which supported versions past that.If you are using Android lollipop or later, you can try: Java-N-Ide. But it supports only upto Java 1.7

LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.

The desktop platform, or thick client, is not as important of a platform as it was several years ago, and it seems to be getting less and less important everyday. Although, like a pendulum, development seems to swing back and forth between thin and think client experiences. It seems as though the current trend is thick client functionality in a thin client package. (The browser as the OS). For this post we will assume the development of a true thick client application, which is one that runs natively on the client computer and is installed or executed from the client computer.

There isn't much choice here. Really, it comes to two options. Swing or SWT. I'll confess my ignorance here. I tried to do a bit of research here, but I am not coming up with a large amount of information. Probably because not many people are actually doing thick client development in Java anymore. I asked one of the best Java developers to help me, and he was able to give me some information.

3a8082e126