This section indicates how to get a J2ME development environment on Eclipse:
(Draft)
Topics: Eclipse (Getting started, Eclipse Platform, Dowloading Eclipse, Setting up Eclipse)- Sony Ericsson J2ME SDK - EclipseME (Setting up EclipseME , Creating a MIDlet) |
||
| Eclipse | ||
Eclipse is an open platform for tool integration built by an open community of tool providers. Operating under an open source paradigm, with a common public license that provides royalty free source code and world wide redistribution rights, the eclipse platform provides tool developers with ultimate flexibility and control over their software technology. The most popular of the Java IDEs, but harder to set up and configure than the commercial ones. Eclipse is the base IDE, but there are many Java-related plugins for Eclipse, and several commercial IDEs built on top of Eclipse. |
||
When you first start working with Eclipse, you might find the user interface somewhat intimidating, with a limited set of options. How do you get started? The Eclipse user interface, or workbench, is based on the concept of a perspective, and you'll first need to understand this concept before you can use Eclipse effectively. Eclipse builds on this basic concept by allowing multiple arrangements of windows. As you perform different tasks, such as coding, debugging, or merging your code changes with those in a centralized code repository, you can use an arrangement of windows chosen specifically for that task. These task-specific arrangements of windows are called perspectives. In addition to views, each perspective can have different tool buttons and menu selections as appropriate. The Resource perspective has a tree-oriented window at the top left that lets you navigate and manage resources, called the Navigator. This window, like most windows in Eclipse, is called a view. Initially, there are two other views in the Resource perspective -- an Outline view below the Navigator, and a Task view below the main editor area. Eclipse distinguishes between views and editors. A perspective can have many views, but it can have only one editor, which is the focal point of the workbench. Generally speaking, if you have a file open in the editor, the other views reflect different aspects of that file. If it's a Java file, and you're in the Java perspective, one view, the Package Explorer, shows where it is physically located in the file and package hierarchy, and another, the Outline view, shows (among other things) the class's methods and attributes. If you have multiple Java files, these views change as you switch between the different files in the editor. Although it's easy to open new perspectives and switch between them, it isn't generally necessary because as you work, the perspective changes automatically when it's appropriate. (Eclipse politely asks your permission first, of course.) You'll see this in a minute, when we create a Java project, and later, when we debug a Java program. Once you get used to perspectives, you'll probably find that they are a smooth and natural way to work because they eliminate buttons, menus, and views from the UI tool that are not appropriate for the job at hand. This makes it much easier to find the relevant tools. We will use Eclipse IDE for J2ME development. An outline for acquiring, installing and using Eclipse is listed in the following sections. We will attempt a comparison/short listing of J2ME toolkits soon and choose the one we would want to use. |
||
| Eclipse Platform | ||
The Eclipse platform itself is structured as subsystems which are implemented in one or more plug-ins. The subsystems are built on top of a small runtime engine. The figure below depicts a simplified view.
Workbench The term Workbench refers to the desktop development environment. The Workbench aims to achieve seamless tool integration and controlled openness by providing a common paradigm for the creation, management, and navigation of workspace resources. Each Workbench window contains one or more perspectives. Perspectives contain views and editors and control what appears in certain menus and tool bars. More than one Workbench window can exist on the desktop at any given time. More information on how to work with eclipse can be obtained here. New projects, folders, and files can be created using several different approaches. In this section resources will be created using three different approaches:
A project can be created using the File menu. Once the project has been created a folder and file can be created as well. |
||
| Downloading Eclipse | ||
The current version (at the time of writing this document) is eclipse-SDK-3.2.1. It can be obtained here. |
||
| Setting up Eclipse | ||
If you're not familiar with Eclipse, you can get more information here. To install Eclipse, simply extract the contents of the downloaded zip file to your preferred location. (If you use WinZip Classic to extract the zip file, be sure that Use folder names is checked to preserve Eclipse's directory structure.) The installation is completed when Eclipse is run for the first time. The "standard" way to install Eclipse is by extracting the zip to the root of your C: drive, thus having Eclipse's working directory be "C:\eclipse". Notes:
|
||
| Setting up the Sony Ericsson J2ME SDK | ||
Next, you'll need to set up the Sony-Ericsson SDK. Install this SDK to your windows system in the default directory (makes later steps much easier!). |
||
| EclipseME | ||
EclipseME is an Eclipse plugin to help develop J2ME MIDlets. EclipseME does the "grunt work" of connecting Wireless Toolkits to the Eclipse development environment, allowing you to focus on developing your application, rather than worrying about the special needs of J2ME development. |
||
Next, you need to set up the J2ME plugin that will tie the Sony Ericsson SDK into the Eclipse environment. Install EclipseME with these instructions. Configure EclipseME with these instructions. |
||
| Creating a New Midlet | ||
| How to create a simple MIDlet is indicated here. | ||
Disclaimer: The information provided on this page comes without any warranty whatsoever and the author is not responsible for the content of external websites. Use it at your own risk. Just because a program, book or service is listed here or has a good review does not mean that we endorse or approve of the program or of any of its contents. All the other standard disclaimers also apply. |
||