 | |
|
Java ME Technology — Powering your Devices Everywhere
» Learn more about the CLDC and CDC platforms
» Sun Product offerings in the Java ME technology space |
JSR 75 - PDA Optional PackagesJSR 75 specifies two packages for the Java ME platform, both of which are mandatory. The PIM package enables developers to access PIM data, such as the calendar, address book, and to-do lists, that is resident on most mobile devices. The File Connection package enables developers to access various forms of data, such as images, sounds, videos, and more, on mobile device file systems. This includes removable storage devices, such as memory cards, that may be supported. Access to both PIM and file data enables applications to ne tightly integrated with information on the device, allowing for more intelligent applications with easy-to-use interfaces. Packages
System Properties
ArticlesAn Overview of the File Connection Optional Package - Describes how the basic scaffolding for file I/O is supported. Getting Started with the FileConnection APIs - This tutorial provides a code-intensive introduction to the FileConnection APIs. This optional package enables J2ME-based applications to create, read, and write files and directories located on mobile devices and external memory cards. An Overview of the PIM Optional Package - Describes the J2ME interfaces for personal information management data. Getting Started With the PIM APIs - This article provides a code-intensive introductory tutorial to Personal information management (PIM) APIs, JSR 75. PIM refers to the ability to manage in electronic form the kinds of personal data that broad classes of users want handy, such as appointment books, contact directories, and to-do lists. Having this information literally at your fingertips, wherever you go, is a strong motive to buy a mobile device. An Introduction to the PIM API for Java ME - The SDN Mobile Java site is presenting a six part series on the Personal Information Management API (JSR 75). Java ME expert and JCP member Enrique Ortiz provides the definitive text on the PIM API. Jump on Part 1 now and be prepared for the rest of the series in the coming weeks. Using the PIM API for Java ME, Part 2 - Portability Considerations - In this installment Enrique explores how to test for PIM API presence on your device and test for presence of the various databases and fields. Learn how to navigate the API and build robust applications. Using the PIM API for Java ME, Part 3 - Security Considerations - Will your application protect the user's address book, calendar and to-do list? In part 3 learn how PIM is designed to work in conjunction with the MIDP 2.0 security framework. Design Consideration for Using the PIM API for Java ME - Welcome to Part 4 of the PIM API series. Now it's time to explore design issues that will affect how your application is developed. Read this, then start your application design. Managing Personal Information - Using the PIM API for Java ME - In the penultimate article in the PIM API series Enrique presents sample source. Small examples of how to do everything from retrieving the names of PIM databases through PIM create/read/update/delete operations to exception handling. Now it's time to play. Managing Personal Information - Summary of PIM Fields - In the final installment, Enrique Ortiz provides an extensive reference on the PIM fields and pointers to related on-line resources. Now you have it all. |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Oracle is reviewing the Sun product roadmap and will provide guidance to customers in accordance with Oracle's standard product communication policies. Any resulting features and timing of release of such features as determined by Oracle's review of roadmaps, are at the sole discretion of Oracle. All product roadmap information, whether communicated by Sun Microsystems or by Oracle, does not represent a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. It is intended for information purposes only, and may not be incorporated into any contract.
| ||||||||||||
