|
CLDC
The Connected Limited Device Configuration (CLDC) is a specification of a framework for Java ME applications describing the basic set of libraries and virtual-machine features that must be present in an implementation. The CLDC is combined with one or more profiles to give developers a platform for building applications on embedded devices with very limited resources such as pagers and mobile phones.CLDC Overview http://java.sun.com/javame/technology/cldc/overview.jsp The CLDC was developed under the Java Community Process as JSR 30JSR 30, CLDC 1.0 http://www.jcp.org/en/jsr/detail?id=30 (CLDC 1.0) and JSR 139JSR 139, CLDC 1.1 http://www.jcp.org/en/jsr/detail?id=139 (CLDC 1.1). Typical requirements CLDC is designed for devices that have limited processing power, memory, and graphical capability. Devices typically have the following features: * 16-bit or 32-bit CPU with a clock speed of 16 MHz or higher * At least 160 KB ROM allocated for the CLDC libraries and virtual mac ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Java ME
Java Platform, Micro Edition or Java ME is a computing platform for development and deployment of portable code for embedded and mobile devices (micro-controllers, sensors, gateways, mobile phones, personal digital assistants, TV set-top boxes, printers). Java ME was formerly known as Java 2 Platform, Micro Edition or J2ME. As of December 22, 2006, the Java ME source code is licensed under the GNU General Public License, and is released under the project name phoneME. The platform uses the object-oriented Java programming language. It is part of the Java software-platform family. Java ME was designed by Sun Microsystems, acquired by Oracle Corporation in 2010; the platform replaced a similar technology, PersonalJava. Originally developed under the Java Community Process as JSR 68, the different flavors of Java ME have evolved in separate JSRs. Oracle provides a reference implementation of the specification, but has tended not to provide free binary i ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
DoJa
DoJa profile is a Java application environment specification for DoCoMo's i-mode mobile phone. DoJa is based on the Java ME CLDC API that is defined in the Java Community Process (JCP). DoJa is a profile defined by NTT DoCoMo to provide communications and other input-output processing, user interface (GUI) and other application features/functions unique to i-mode, and extension libraries defined by individual phone terminal makers to add original functions. However, in contrast with other Java ME profiles like Mobile Information Device Profile (MIDP) or Information Module Profile (IMP), DoJa is not defined as a Java Specification Request (JSR), hence it is often called a "proprietary" Java ME profile. DoJa allows i-mode to offer more dynamic and interactive content than conventional HTML-based i-mode content. Java for i-mode consists of support for a version of CLDC and a version of the DoJa profile. CLDC support can be 1.0 or 1.1 depending on the handset. The DoJa profile was o ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Java Community Process
The Java Community Process (JCP), established in 1998, is a formalized mechanism that allows interested parties to develop standard technical specifications for Java technology. Anyone can become a JCP Member by filling a form available at thJCP website JCP membership for organizations and commercial entities requires annual fees – but is free for individuals. The JCP involves the use of Java Specification Requests (JSRs) – the formal documents that describe proposed specifications and technologies for adding to the Java platform. Formal public reviews of JSRs take place before a JSR becomes ''final'' and the JCP Executive Committee votes on it. A final JSR provides a ''reference implementation'' that is a free implementation of the technology in source code form and a ''Technology Compatibility Kit'' to verify the API specification. A JSR describes the JCP itself. , JSR 387 describes the current version (2.11) of the JCP. List of JSRs There are hundreds of JSRs. Some ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Java Specification Request
The Java Community Process (JCP), established in 1998, is a formalized mechanism that allows interested parties to develop standard technical specifications for Java technology. Anyone can become a JCP Member by filling a form available at thJCP website JCP membership for organizations and commercial entities requires annual fees – but is free for individuals. The JCP involves the use of Java Specification Requests (JSRs) – the formal documents that describe proposed specifications and technologies for adding to the Java platform. Formal public reviews of JSRs take place before a JSR becomes ''final'' and the JCP Executive Committee votes on it. A final JSR provides a ''reference implementation'' that is a free implementation of the technology in source code form and a ''Technology Compatibility Kit'' to verify the API specification. A JSR describes the JCP itself. , JSR 387 describes the current version (2.11) of the JCP. List of JSRs There are hundreds of JSRs. Some ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Midlet
A MIDlet is an application that uses the Mobile Information Device Profile (MIDP) of the Connected Limited Device Configuration (CLDC) for the Java ME environment. Typical applications include games running on mobile devices and cell phones which have small graphical displays, simple numeric keypad interfaces and limited network access over HTTP. MIDlet can run on Android devices via the J2ME Loader emulator application. The .jad file describing a MIDlet suite is used to deploy the applications in one of two ways. Over the air (OTA) deployment involves uploading the .jad and .jar files to a Web server which is accessible by the device over HTTP. The user downloads the .jad file and installs the MIDlets they require. Local deployment requires that the MIDlet files be transferred to the device over a non-network connection (such as through Bluetooth or IrDa, and may involve device-specific software). Phones that support microSD cards can sometimes install .jar or .jad files that have ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
MIDP 2
Mobile Information Device Profile (MIDP) is a specification published for the use of Java on embedded devices such as mobile phones and PDAs. MIDP is part of the Java Platform, Micro Edition (Java ME) framework and sits on top of Connected Limited Device Configuration (CLDC), a set of lower level programming interfaces. MIDP was developed under the Java Community Process. The first MIDP devices were launched in April 2001. General APIs The core application programming interfaces are defined by the underlying Connected Limited Device Configuration system. javax.microedition.io Contains the Java ME-specific classes used for I/O operations. javax.microedition.lcdui Contains the Java ME-specific classes used for the GUI. LCDUI has a simple screen based approach where a single Displayable is always active at anyone time in the application user interface. LCDUI API provides a small set of displayables common in mobile device user interfaces: List, Alert, TextBox, Form and C ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
JSR-75
PDA Optional Packages for the J2ME Platform JSR 75 is a specification that standardizes access in the Java on embedded devices such as mobile phones and PDAs to data that resides natively on mobile devices. JSR 75 is part of the Java ME framework and sits on top of CLDC, a set of lower level programming interfaces. It has 2 main components. Not all devices that claim to implement JSR 75 will implement both components. See also * MIDlet A MIDlet is an application that uses the Mobile Information Device Profile (MIDP) of the Connected Limited Device Configuration (CLDC) for the Java ME environment. Typical applications include games running on mobile devices and cell phones which h ... External links The JSR 75 SpecificationSuns overview of the File Connection Optional PackageSuns Overview of the PIM Optional Package {{prog-lang-stub Java device platform Java specification requests ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Mobile Information Device Profile
Mobile Information Device Profile (MIDP) is a specification published for the use of Java on embedded devices such as mobile phones and PDAs. MIDP is part of the Java Platform, Micro Edition (Java ME) framework and sits on top of Connected Limited Device Configuration (CLDC), a set of lower level programming interfaces. MIDP was developed under the Java Community Process. The first MIDP devices were launched in April 2001. General APIs The core application programming interfaces are defined by the underlying Connected Limited Device Configuration system. javax.microedition.io Contains the Java ME-specific classes used for I/O operations. javax.microedition.lcdui Contains the Java ME-specific classes used for the GUI. LCDUI has a simple screen based approach where a single Displayable is always active at anyone time in the application user interface. LCDUI API provides a small set of displayables common in mobile device user interfaces: List, Alert, TextBox, Form and Canv ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
MIDP
Mobile Information Device Profile (MIDP) is a specification published for the use of Java on embedded devices such as mobile phones and PDAs. MIDP is part of the Java Platform, Micro Edition (Java ME) framework and sits on top of Connected Limited Device Configuration (CLDC), a set of lower level programming interfaces. MIDP was developed under the Java Community Process. The first MIDP devices were launched in April 2001. General APIs The core application programming interfaces are defined by the underlying Connected Limited Device Configuration system. javax.microedition.io Contains the Java ME-specific classes used for I/O operations. javax.microedition.lcdui Contains the Java ME-specific classes used for the GUI. LCDUI has a simple screen based approach where a single Displayable is always active at anyone time in the application user interface. LCDUI API provides a small set of displayables common in mobile device user interfaces: List, Alert, TextBox, Form and Canv ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Connected Device Configuration
The Connected Device Configuration (CDC) is a specification of a framework for Java ME applications describing the basic set of libraries and virtual-machine features that must be present in an implementation. The CDC is combined with one or more profiles to give developers a platform for building applications on embedded devices ranging from pagers up to set-top boxes.CDC Overview http://java.sun.com/javame/technology/cdc/overview.jsp The CDC was developed under the Java Community Process as JSR 36JSR 36, CDC 1.0.2 http://www.jcp.org/en/jsr/detail?id=36 (CDC 1.0.2) and JSR 218JSR 218, CDC 1.1.2 http://www.jcp.org/en/jsr/detail?id=218 (CDC 1.1.2). Typical requirements Devices that support CDC typically include a 32-bit CPU with about 2 MB of RAM, and 2.5 MB of ROM available for the Java application environment. The reference implementations for CDC profiles are based on Linux running on an Intel-compatible PC, and optimized implementations are available for a variety of ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Abstract Window Toolkit
The Abstract Window Toolkit (AWT) is Java's original platform-dependent windowing, graphics, and user-interface widget toolkit, preceding Swing. The AWT is part of the Java Foundation Classes (JFC) — the standard API for providing a graphical user interface (GUI) for a Java program. AWT is also the GUI toolkit for a number of Java ME profiles. For example, Connected Device Configuration profiles require Java runtimes on mobile telephones to support the Abstract Window Toolkit. History When Sun Microsystems first released Java in 1995, AWT widgets provided a thin level of abstraction over the underlying native user-interface. For example, creating an AWT check box would cause AWT directly to call the underlying native subroutine that created a check box. However, a check box on Microsoft Windows is not exactly the same as a check box on Mac OS or on the various types of Unix. Some application developers prefer this model because it provides a high degree of fidelity to the ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
