Setting Workbench Preferences

Before starting your development work, you may want to start by reviewing the default Workbench preferences. Select Window > Preferences and click Workbench to view the Workbench preferences, as shown in Figure 2.2.
    Build automaticallyBy default, the option Build automatically is selected, which means that every time you save a source file or a resource file, the build system is automatically invoked to build the project. If you like to save your files frequently and do not want the build system invoked every time you save, you may prefer to turn this setting off.Save automatically before build
    In most cases, you want to turn this setting on. The build system builds the most recently saved versions of the source. If you have this setting turned off and invoke the build system without saving your source files, then the build system does not include the changes you have made since the last save.

Using Workspaces

By default, the Eclipse Workbench stores project files (projects, folders, and files) in a subdirectory of the location of where you installed the Workbench. This sub-directory is called the "workspace" subdirectory.

When you create a project, you can select a different directory. However, the Eclipse Workbench assumes that the directory you specify is an Eclipse-generated directory. It is recommended that you use the default location as your workspace. Specifically, it is recommended that you do not create projects on the desktop.

Rather than changing the project's workspace directory, you should accept the default location and import your files into the project, which moves them to the workspace location.

Select an Application Type

Before you create a project, you first consider which type of application you want to create.

Palm OS 68K Application

If your goal is to create applications that run on all Palm OS devices and on all supported Palm OS versions, then you want to create Palm OS 68K applications.

The 68K API is the set of functions that spans all Palm OS releases. The 68K functions allow application code compiled for Dragonball processors to access the capabilities of Palm OS. The 68K API is the native API for Palm OS 4 and earlier Palm OS versions. The 68K API operates in PACE (the Palm OS Application Compatibility Environment) on Palm OS Garnet and Palm OS Cobalt.

Palm OS 68K Application with PACE Native Objects

If you are an experienced developer accustomed to working with the 68K API but you want to take advantage of the ARM CPUs that power Palm OS Garnet and Palm OS Cobalt handhelds, then you can create PACE native objects.

A PACE native object (PNO) is an ARM-native subroutine that your 68K application calls using the PceNativeCall() function.

Palm OS Protein Application

If you want to take advantage of the Palm OS Protein API functions and the features emerging on new Palm OS Cobalt handhelds, you want to create Palm OS Protein applications.

Palm OS Protein applications can be multithreaded, can access schema and extended databases, and can employ Palm OS Cobalt's multimedia framework. However, Palm OS Protein applications only run on Palm OS Cobalt and later.