Captain Cooks

cleanupJava online Casino Captain Cooks 2 Platform, Micro Edition, or J2ME, is a collection of java programming language Application Programming Interface targeting embedded consumer products such as Personal Digital Assistant cell phones and other consumer appliances.J2ME has become a popular option for creating games for cell phones, as they can be emulated on a Personal computer during the development stage and easily uploaded to the phone. This contrasts with the difficulty of developing,

testing, and loading games for other special gaming platforms such as those made by Nintendo, Sony, and others, as expensive system-specific hardware and kits are required.Often, introductions of J2ME gloss over areas that the beginning J2ME developer might improve their learning process and hopefully this set of articles will remove that obstacle. What we will cover is the history leading up to J2MEs birth and beyond. We will also cover the complexity of the whole J2ME API ecological system and

hopefully this will help you in your J2ME development projects and applications.Overall, the change from analogue to digital in both devices and infrastructure serving those devices has been the third unseen character in this J2ME evolution. Changes from analogue methods of cellular communication to such standards as CDMA, TDMA,and WCDMA. Also, drastic changes in the vehicle computing and digital TV realm involving new standards such as DVB, MHP, HAVi, MPEG4, OSGi, and etc have

changed how computer languages such as Java and the J2ME platform interact with this Captain Cooks new area. A brief history of Java on mobile devices This history is called pre-platform and occurs before the 1999 Sun event of renaming Java portions as platform editions. In the 1992 time span Sun Microsystems Engineers and Venture Capital funded Startups contributed to a project called Green to bring new Virtual Machine execution framework to embedded devices. The device was called Star7 and was powered by a SPARC CPU.The language which was called OAK at the time and its features were the result of the merge of FirstPerson,

ON, and Sun Microsystems. Although, not mentioned in online this brief history. The first JVM was in fact completed by ON and based on Smalltalk according to The official Wiki version of the history of Java Language. Thus, the having the small foot print of a Virtual Machine not only benefited the birth of Java programming language but its steady climb during this period into browsers and the start of its rebirth into mobile devices.Although Sun Microsystems concluded that Casino some of

its role during this period was to drive the Consumer Device market away from WINTEL to SPARC processors it was the application killer app side that survived this risky startup time period. PersonalJava Suns second exploration of Java on mobile devices Captain Cooks was centered around the idea of deploying a subset of JDK1.1.8 on mobile devices that have a more in depth display as opposed to just a character display. At this time, around 1998, one of the target devices for PersonalJava was set boxes as evidence by press such as McNealy touts Java on set boxes.As the PersonalJava spec was introduced in 1998 it online was nicknamed pJava by Sun

Microsystems. Because pJava uses a subset of JDK1.1.8, SUN Microsystems released a pJava Emulation Environment to assist developers in testing their applets and applications for pJava Compliance. EmbeddedJava EmbeddedJava was based on JDK1.1.6 and was targeted for those mobile devices that only had a character display. JavaPhone The Mobile device OEMs found that the PersonalJava and EmbeddedJava solutions lacked those APIs that would allow access to pure telephony functionality on Mobile Devices. Thus JavaPhone API was designed by Sun Microsystems to be vertical expansion of PersonalJava

to add telephony functionality to deployed Java solutions on Mobile devices. JavaTV JavaTV is designed to provide JAVA APIs for the set box and headless network terminals beyond what PersonalJava provides that are specific to the iTV/DTV platform such as HAVi, DVB-MHP, and etc. AutoJava AutoJava was also a 1998 Sun Microsystems push into telematics and did not get enough traction to survive as a separate API. JavaOS JavaOS targets the underlying RealTimeOS structure of the OS that typically is deployed on Mobile Devices or Embedded Devices. JavaOS was launched by SUN Microsystems

in the fall of 1996 and was based on the JDK1.0. ChorusOS which was bought during JavaOS development by SUN Microsystems was later spun off as ChorusOS. Birth of J2ME As you can see Captain Cooks by this NewsFlash in the spring of 1998 the Mobile Device market was being stormed by Java but not in a very structured fashion. As you can see from an Interview of the Father of KVM Sun was behind the scenes responding

to this fragmentation online in the Mobile Device space by innovating Casino a new JVM for Mobile Devices and the first set of J2ME platform specs and as a project was nicknamed Spotless. J2ME is Alive In the time period of 1998-1999 SUN Microsystems reveals its behind the scenes work in defeating fragmentation in the Mobile Device space by announcing the formation of the Java Community Process and reogranizing these

fragments of Java APIs for mobile devices into the J2ME, Micro Edition Platform. Let us now go over how J2ME is organized against API fragmentation in the Mobile Device space. J2ME Configurations Sun Microsystems came up with the idea that a configuration API would cover the runtime aspects of J2ME deployed on a device. The smallest J2ME configurations Captain Cooks are actually subsets of the largest J2ME configuration. The runtime aspects are covered by having these specific classes in the configuration API:Java programming

language featuresWeb reference titleCLDC1.0 workConnected Limited Device Configuration 1.0 JSR30 URL dateMarch 17 year2005 This Connected Limited Device Configuration 1.0 targets devices with 128k to 512k memory, limited power or battery operation, connectivity Casino to some network at low speeds, and user interface.Web reference titleConnected Device Configuration 1.0 workConnected

Device Configuration 1.0 JSR36 URL dateMarch 17 year2005 This Connected Device Configuration 1.0 targets devices with 512k minimum ROM/128k minimum RAM, connectivity to some network, supports a complete installation of a complete JVM, and more full featured user interfaces compared to CLDC.Web reference titleMIDP1.0 workMobile Information Device Profile 1.0 JSR37 URL dateMarch 17 year2005 This Mobile Information Device Profile 1.0 extends the CLDC1.0 Java environment in a vertical way to support MIDlet application

development on devices targeted in the CLDC1.0 spec by providing a GUI toolkit, persistent data storage, messaging, networking components, and security. Although, attributes of JavaPhone and Java Telephony are mentioned in the spec; JavaPhone telephony attributes are not included as classes in MIDP1.0 but Captain Cooks later on completed as a separate JSR and API package.Web reference titleMIDP3.0 workMobile Information Device Profile 3.0 JSR271 URL dateMarch 17 year2005 This Mobile Information Device Profie 3.0 extends MIDP2.0 to allow MIDlets to be auto-launched, run in background within the

same VM, and enable inter-MIDlet communication. Extended functionality includes secure record stores/removeable record Captain Cooks Casino stores, IPv6, multiple network interfaces per device, and additional MIDlet provisioning in addition to OTA. Foundation Profile The Foundation Profile is what can be called a vertical specification online profile. A vertical specification profile specifies the targeted family of devices by memory size and the optional profiles that may plugin more functionality in addition to this online profile. The GUI APIs are often Profiles

plugged in on top of this Profile. Typical rich network devices include set top boxes , auto-computing , and etc. The JSRs for this profile are:Web reference titleFoundation Profile 1.1 workFoundation Profile 1.1 JSR219 URL dateMarch 17 year2005 This Foundation Profile 1.1 is on top of the CDC1.1 which supports J2SE 1.4 Casino APIs. Targeted devices memory is increased to 256k minimum ROM/512k minimum RAM. Captain Cooks Some APIS included to specify functionality for IPv6, security, and more math support. Personal Profile This Personal Profile provides high web fidelity to device with a rich network connection and online can use the heavy weight applet

classes that were part of the PersonalJava spec. While Personal Casino Profile, JSR62, supports PersonalJava1.1.x and PersonalJava1.2.x of the PersonalJava Application Environment; Personal Profile 1.1 supports the adoption of the subset of J2SE1.4 APIs as Personal Profile 1.0 was based on the subset of J2SE1.3 APIs. The JSRs for this profile are:Web reference titlePersonal Profile 1.1 workPersonal Profile 1.1 JSR216 URL dateMarch 17 year2005 This Personal Profile 1.1 extends the Personal Profile 1.0 to update APIs to J2SE 1.4 and to make sure optional Graphics

Packgaes derived from J2SE 1.4 APIs can be deployed on top of this profile. Devices targeted now are of minimum memory size of 3.5 MB ROM/3.5 MB RAM. Personal Basis Profile This Personal Basis Profile provides a basic graphical user interface, ie the AWT lightweight APIs, on top of the CDC and Foundation Profile and is considered as a subset to the Personal Profiles. This profile also provides the xlet classes required for JavaTV. The JSRs for this profile are:Web reference titlePersonal Basis Profile 1.1 workPersonal Basis Profile 1.1 JSR217 URL dateMarch 17 year2005

This Personal Casino Basis Profile 1.1 extends the Personal Basis Profile 1.0 by updating all APIs to derived from J2SE 1.4 APIs to be compatible with optional graphics APIs such as AGUI. Information Module Profile This Information Module Profile supports embedded network connected devices without a graphical user interface. This profile is a subset of the Casino Captain Cooks MIDP1.0 profile without the LCDUI classes of MIDP1.0. The typical devices target are modems, household devices,

and industrial metering devices. While IMP is a subset of MIDP1.0, IMP-NG is a subset of MIDP2.0. The JSRs for this profile are:Web reference titleIMP-NG workInformation Module Profile-Next Generation JSR228 URL dateMarch 17 year2005 This Information Module Profile-Next Generation is a subset of mIDP2.0 without the LCDUI classes. Digital Set Top Box Profile This Digital Set Top Box Profile is a subset of JavaTV and is targeted for the smaller set top boxes that deploy OCAP.

online Thus, this profile differs from the javaTV setup in that Casino its on top of CLDC not CDC to support a smaller device memory foot print. However, several concepts are borrowed from the JavaTV items in Personal Basis Profile such as the xlet lifecycle. The JSR for this profile is:Web reference titleRMI workRMI Optional Package JSR66 URL dateMarch 17 year2005

The RMI Optional Package provides interoperable J2SE RMI support on top of the CDC and Foundation Profile.Web reference titleWireless Messaging Captain Cooks API workWireless Messaging API JSR120 URL dateMarch 17 year2005 The Wireless Messaging API provides classes to support messaging application development on the J2ME Platform.Web reference titleMobile Telephony API workMobile Telephony JSR253 URL dateMarch 17 year2005 The Mobile Telephony API provides the classes to control the calls on both CLDC and CDC devices. As we

head Captain Cooks into the future of Mobile Devices, the Java Community Process Contributors to the J2ME Platform have been busy creating new JSRs to cover new advances Mobile Technology. For example:Web reference titleContactless Communication API workContactless Communication API JSR257 URL dateMarch 17 year2005 Specifies the API for contactless communication such as through RFID tags and etc. References Web reference titleContactless Communication API workContactless Communication API JSR257 URL dateMarch 17 year2005( Trademark Notices J2ME, Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.Java platform

online casinos