| Home : Java : J2ME |
| Click "Subscribe" if you want to be notified of new or updated links in this category. | Subscribe |
|
|
J2ME Listings
|
|
Total:
48 | Displaying: 21 - 30 | Pages: << 1 2 3 4 5 >> |
|
|
|
This article provides an overview of the CLDC Generic Connection Framework and examines the new support for sockets and datagrams. The article: Discusses the new support for low-level networkingDescribes how to run the networking demos in the J2ME Wireless Toolkit 2.0 Demonstrates how to use the new low-level networking support Provides sample code listings for a time MIDlet and an email MIDlet
Updated: 05/04/2005
|
|
|
This article describes the role that code optimization plays in writing fast games for mobile devices. Using examples I will show how, when and why to optimize your code to squeeze every last drop of performance out of MIDP-compliant handsets. We will discuss why optimization is necessary and why it is often best NOT to optimize. I explain the difference between high-level and low-level optimization and we will see how to use the Profiler utility that ships with the J2ME Wireless Toolkit to discover where to optimize your code. Finally this article reveals lots of techniques for making your MIDlets move.
Updated: 05/04/2005
|
|
|
This article describes the role that code optimization plays in writing fast games for mobile devices. Using examples I will show how, when and why to optimize your code to squeeze every last drop of performance out of MIDP-compliant handsets. We will discuss why optimization is necessary and why it is often best NOT to optimize. I explain the difference between high-level and low-level optimization and we will see how to use the Profiler utility that ships with the J2ME Wireless Toolkit to discover where to optimize your code. Finally this article reveals lots of techniques for making your MIDlets move.
Updated: 05/04/2005
|
|
|
In honor of JavaOne several new JSR\'s were submitted dealing with new versions of JDBC, XML Binding and XML-RPC. An important specification dealing with adding scripting language support to Java also was proposed during JavaOne. Further, the executive committee for J2ME overturned the earlier rejection ballot for updating the J2ME core specifications with Java 1.4 support.
Updated: 05/04/2005
|
|
|
The major players in the handheld market have put their weight behind Java (Nokia, Ericsson, Motorola), the 2.5-3.0G networks are coming online, and you\'ve been sweating over a MIDlet for the past few weeks, rearing to get it up and running on the latest device.It should work -- after all, it works well on your desktop emulator connecting to your back-end service. Two weeks before launch you get a MIDP device and are hit by some real-world wireless realities.
Updated: 05/04/2005
|
|
|
This two-part series of articles will show you how to use J2ME and Bluetooth to develop next-generation wireless applications for tomorrow\'s market. This first article covers the basics of Bluetooth; the next one will concentrate on using the Java APIs for Bluetooth Wireless Technology (JSR 82) to develop Java technology-enabled applications for Bluetooth-enabled devices. This article starts by presenting a brief overview of the technology.
Updated: 05/04/2005
|
|
|
For a long while, all the excitement in the Java 2 Platform, Micro Edition (J2ME) was centered on the Connected Limited Device Configuration (CLDC), released in final form in May, 2000. The first CLDC-based profile, the Mobile Information Device Profile (MIDP), followed two months later. MIDP garnered much interest in the Java community because it defined a new application model, as well as classes for user interface and persistence. In other words, it provided a complete environment for deploying and running interactive applications.
Updated: 05/04/2005
|
|
|
This is the final excerpt in a series from J2ME in a Nutshell, focusing on the delivery and installation of MIDlets.The MIDP specification creates the concept of a MIDlet, defines its lifecycle and its execution environment, and specifies the programming interfaces that a MIDlet can expect to be present on any conforming device. However, it currently does not address in any detail how the user should locate MIDlet suites, how MIDlet suites will be installed on a cell phone or a PDA, and what facilities are to be provided to allow the user to select and launch an installed MIDlet or to remove MIDlet suites from the device.
Updated: 05/04/2005
|
|
|
Wireless Java applications are, by their nature, network-centric. The devices that these applications run on are, however, less predictable. Most notably, the precise nature of the network connection depends both on the device and on the services provided by the network to which it is connected. Some wireless devices may be directly connected to the Internet, while others are only able to access it through a gateway.
Updated: 05/04/2005
|
|
|
J2ME MIDP 1.0 is widely regarded as an industry success story with over 75 million Java-enabled handsets currently deployed worldwide. As a direct result, we have seen operators increasing their data revenues and subscribers downloading a new generation of cool games onto their handsets. However, MIDP 1.0 is somewhat restricted in its functionality and the advent of MIDP 2.0 brings with it not only new features, but a new security model that will allow Java to reach its full potential in a carefully managed environment. As with all good technological evolutions, MIDP 2.0 opens up a host of new functionalities that will power the next generation of gaming, business and consumer applications.
Updated: 05/04/2005
|
|
|
J2ME Listings
|
|
Total:
48 | Displaying: 21 - 30 | Pages: << 1 2 3 4 5 >> |
|
|
