Nokia 9000 User manual

Nokia 9000/9110 Development
Environment (N9kDE)
User Guide

© 1999 NOKIA MOBILE PHONES. This manual and the software described
herein are protected by the copyright laws of the United States of America (Title
17 U.S.C.) and international copyright treaties, as well as other intellectual
property laws and treaties, with all rights reserved. The software, which includes
the computer software, associated media, printed materials, and any online or
electronic documentation, is licensed, not sold. Neither the manual nor software
may be copied in whole or in part, by any means whatsoever, except for the
purposes of making a backup copy of the software for the licensee’s own use,
without the prior written consent of NOKIA MOBILE PHONES.
Nokia is a registered trademark of Nokia Corporation.
The models 9000 and 9110, the 9000il Communicator, and other Nokia products
referenced herein are either trademarks or registered trademarks of Nokia
Corporation and/or its affiliates.
Geoworks and GEOS are registered trademarks of Geoworks Corporation.
Borland C++ is a registered trademark of Inprise Corporation.
Intel is a registered trademark of Intel Corporation.
Paint Shop Pro is a trademark of JASC Software, Inc.
Microsoft, Windows, Visual C++, and Visual Basic are registered trademarks of
Microsoft Corporation.
All other product names mentioned in this documentation may be trademarks, and
if so, are trademarks or registered trademarks of their respective holders and are
used in this documentation for identification purposes only.
Last Modified: June 10, 1999

Table of Contents
1 PRODUCT OVERVIEW.....................................................................................................................5
2 ABOUT THE NOKIA 9000/9110 DEVELOPMENT ENVIRONMENT.........................................6
3 PARTS OF THE NOKIA 9000/9110 DEVELOPMENT ENVIRONMENT...................................7
3.1 INTERACTIVE DEVELOPMENT ENVIRONMENT ..................................................................................7
3.2 EDITOR ............................................................................................................................................8
3.3 EMULATOR ......................................................................................................................................8
3.4 COMPILER AND LINKER ...................................................................................................................9
4 CREATING A PROJECT..................................................................................................................11
4.1 BASELINE FILES.............................................................................................................................12
4.1.1 PRJ File ................................................................................................................................12
4.1.2 GOH File ..............................................................................................................................13
4.1.3 Baseline GOC File................................................................................................................14
4.1.4 Baseline GP File...................................................................................................................18
5 OPENING A PROJECT ....................................................................................................................20
5.1 CLOSING A PROJECT ......................................................................................................................21
5.2 SAVING A PROJECT........................................................................................................................21
6 PROJECT SAVE AS..........................................................................................................................22
7 FIND FAST DROP BOX....................................................................................................................23
8 OPTIONS DIALOG ...........................................................................................................................24
9 GRAPHICAL FILE INFORMATION (.NGX FILES) ...................................................................25
10 TOOLBOX (ADD-IN MANAGER) ..............................................................................................26
11 GEOS HELP BROWSER..............................................................................................................28
12 BUILDING THE PROJECT ........................................................................................................30
12.1 MAKEFILE......................................................................................................................................30
12.2 COMPILE AND LINK .......................................................................................................................30
12.3 COPY GEO FILE ............................................................................................................................31
12.4 LAUNCH EMULATOR......................................................................................................................31
12.5 BUILD SHORTCUTS ........................................................................................................................31
12.6 SWAT.............................................................................................................................................32
13 FORMS AND PROCEDURES......................................................................................................35
13.1 MAIN FORM...................................................................................................................................35
13.2 ADDING A FORM............................................................................................................................35
13.3 GRAPHIC FORMS............................................................................................................................36
13.4 ADDING A PROCEDURE..................................................................................................................36
13.5 DELETING FORMS AND PROCEDURES ............................................................................................37
13.6 EDITING GRAPHICS........................................................................................................................37
13.7 LINE AND FILL COLOR...................................................................................................................38
14 INSERTING ICONS ......................................................................................................................40

14.1 CREATING THE PCX FILE ..............................................................................................................40
14.2 PCX TO GOH MANUAL CONVERSION...........................................................................................40
14.3 SDK AUTOMATED PROCEDURE FOR INSERTING ICONS .................................................................41
14.4 STATUS PANE LABEL.....................................................................................................................41
15 SOURCE CODE EDITOR.............................................................................................................42
15.1 NOKIA 9000/9110 DEVELOPMENT ENVIRONMENT CODE EDITOR FEATURE SET...........................42
15.2 RECORD MACRO DIALOG ..............................................................................................................44
15.3 SAVE MACRO DIALOG...................................................................................................................44
15.4 GOTO LINE DIALOG.......................................................................................................................44
15.5 FIND DIALOG.................................................................................................................................45
15.6 FIND & REPLACE DIALOG .............................................................................................................45
15.7 WINDOW PROPERTIES DIALOG ......................................................................................................45
15.8 USING THE MOUSE.........................................................................................................................48
15.11 DEFAULT KEYBOARD MAPPINGS...............................................................................................48
15.12 THE SOURCE CODE EDITOR RIGHT-CLICK MENU......................................................................50
15.13 NOKIA 9000/9110 DEVELOPMENT ENVIRONMENT OUTPUT WINDOW.......................................50
15.14 DOCKING ...................................................................................................................................51
16 CREATING A PACKAGE............................................................................................................52
17 TROUBLESHOOTING .................................................................................................................56
17.1 HOW DO I COMPILE MY PROJECT?..................................................................................................56
17.2 WHAT HAPPENS IF MY PROGRAM HAS A COMPILATION ERROR?.....................................................56
17.3 WHAT HAPPENS IF MY PROGRAM HAS A RUN-TIME ERROR?...........................................................56
17.4 HOW DOES THE SDK HANDLE MULTIPLE GOC FILES? ..................................................................56
17.5 HOW DO I START THE EMULATOR? ................................................................................................56
17.6 WHERE IS MY PROGRAM IN THE EMULATOR?.................................................................................56
17.7 WHAT HAPPENED TO MY OUTPUT WINDOW? .................................................................................57
17.8 DO I HAVE TO BE LOGGED IN AS ADMINISTRATOR TO RUN THE SDK?...........................................57
17.9 WILL MY PROJECTS BE DELETED IF I UN-INSTALL? ........................................................................57
17.10 WHERE ARE MY PROJECTS SAVED?............................................................................................57
17.11 HOW DO I REMOVE APPLICATIONS FROM MY EMULATOR?.........................................................57
17.12 HOW TO I DEBUG IN THE SDK?..................................................................................................57
17.13 WHERE CAN I GET GEOS PROGRAMMING HELP? ......................................................................58
17.14 HOW DO I DOWNLOAD MY PROJECT TO THE HANDSET?.............................................................58
17.15 WHERE CAN I GET PAINT SHOP PRO? ........................................................................................58
18 TOOLBAR QUICK REFERENCE...............................................................................................59
19 GLOSSARY.....................................................................................................................................60

1Product Overview
The Nokia 9000/9110 Development Environment improves application development for the Nokia 9000
Communicator class of mobile phones. It includes the following features:
•Broad-featured interactive development environment
•Simplified interaction with the Borland C++ compiler and the Geoworks SDK
•Intuitive, highly-integrated create-edit-build-test development cycle
•Convenient access to the N9000 emulator
•Automated application shell development with forms and procedures
•Simplified application packaging with graphical packager tool
•Automated code generation
•Rich text edit control
•Capability to extend the N9KS with the Toolbox API
•Eliminates redundant programming tasks.
•Provides rapid access to GEOS documentation and help.
The Nokia 9000/9110 Development Environment is designed to operate as an extension of the existing
GEOS SDK. This extension is provided through the use of executable files developed by Geoworks. The
Nokia 9000/9110 Development Environment makes use of GEOS SDK.
The Nokia 9000/9110 Development Environment is designed to permit technological evolution and service
extensions. The SDK is designed to allow for quick deployment of complete applications. This is achieved
by automating the complexities associated with packaging an application for delivery to the Nokia 9000
Communicator through a specialized packaging utility.
The SDK is designed to allow for quick compilation and debugging of applications. This is achieved by an
intuitive integration into the N9KS IDE of the GEOS compiler, emulator and debugger.
In summary, the SDK is an extensible development environment providing simplified extensions to the
GEOS SDK. The SDK provides compatible support to existing applications and moreover, is designed to
gracefully evolve through the adoption and provision of future enhancements to the GEOS language.

2About the Nokia 9000/9110 Development Environment
The Nokia 9000/9110 Development Environment works in harmony with the Geoworks GEOS SDK for
the N9000. The Nokia 9000/9110 Development Environment is different from the Geoworks GEOS SDK,
and it provides more user-oriented and productivity-based features for the N9000 developer.
The Nokia 9000/9110 Development Environment integrates an intuitive edit-build-test environment
through an easy to use interface.
Through the Nokia 9000/9110 Development Environment, the user creates, edits, compiles, and executes
programs in the N9000 emulator.
The Nokia 9000/9110 Development Environment supports packaging of N9000 applications for
convenient download to the handset.
The Nokia 9000/9110 Development Environment is based on the notion of a project. A project is the group
of GEOS files and support information that are required to compile and execute a GEOS application. A
project in the Nokia 9000/9110 Development Environment includes one PRJ file, one GOC file, one GP
file, one GOH file, and a number of NGX files.

3Parts of the Nokia 9000/9110 Development Environment
The Nokia 9000/9110 Development Environment itself is divided into several components.
•Interactive Development Envrionment
•GEOS SDK (emulator, libraries, *.h, swat)
•GEOS Help Files (*.htm)
•HTML Help Viewer
•Borland C++ (mkmf, pmake, bc4)
•Packaging Tool – (including tar and Nserver)
•Templates for GP, GOH, GOC, PRJ, NGX
•Active-X Tool(s) (add-ins called “Components”)
•Help Files
3.1 Interactive development Environment
The Nokia 9000/9110 Development Environment is a multi-featured workspace that includes a rich editor
capability, project creation, compilation, and emulation, form and procedure creation and deletion, and
online help support.

3.2 Editor
The Nokia 9000/9110 Development Environment Source Code Editor is used for viewing and editing
project files.
3.3 Emulator
The Nokia 9000 Geos emulator may be launched from the Nokia 9000/9110 Development Environment. It
may be used in conjunction with Swat to provide debugging support.
Line Tool

3.4 Compiler and Linker
The Nokia 9000/9110 Development Environment provides a good integration to the GEOS compiler and
linker. During the development cycle, the Build menu supports step-by-step compilation as well as a
shortcut <F5> to make the makefiles, compile, and launch the emulator.

4Creating a Project
To create a new project, click “New” from the File menu. You are presented with a dialog box to enter
project specific information including project name, project long name, and project directory. After
entering this information the project files are created based on the user settings using the provided template
files.
Creating a new project in the SDK gives the user a default application that includes a main form
with a close button. The default application is code-generated from the Nokia 9000/9110
Development Environment baseline files. The five baseline (template) files that are core to the
Nokia 9000/9110 Development Environment include:
Filename
Baseline.goh
Baseline.gp
Baseling.goc
Baseline.ngx
Baseline.prj
Once a project is created, a copy of the baseline files are transferred to the new project’s target
directory. The baseline files are also renamed using the project’s name.

4.1 Baseline Files
The baseline files are used by the Nokia 9000/9110 Development Environment to provide enough
information to the GEOS compiler to successfully compile and execute a Nokia 9000 application.
This minimum information is described as the baseline project. Within each file are special tags
that are replaced with the information provided by the user.
Tag Replaced With
$SHORT NAME$ Short project name, referenced as <project name> (user
provided)
$SHORT FILE NAME$ <project name>.prj
$PROJECT NAME$ Long project name (user provided)
$AUTHOR$ “Nokia 9000/9110 Development Environment”, the user
can modify this text
$INCLUDE PROJECT GOH$ @include < project name >.goh
$PROCESS CLASS DECLARATION$ @classdecl <project name>ProcessClass, neverSaved
$FULL SHORT NAME$ <project name>.app
$GEODE TYPE$ “appl, process, single”
$PROCESS CLASS NAME$ <project name>ProcessClass
$APPLICATION OBJECT$ <project name>App
$TOKEN CHARS$ First 4 characters of short project name (upper case)
$TOKEN ID$
$LIBRARIES$ library geos
library ui
library foam
Within the baseline files are special code blocks that the SDK uses for code generation. If these
code blocks are removed or altered in any way, the project will be corrupted. The code that is
generated within each of these blocks is dependent on the user. For example, the user can add
forms, add procedures, edit graphics, inset icons, and insert status pane labels. Each one of
these user actions will generate or modify code within the code blocks.
The code blocks are shown as:
//{{START BLOCK
//}}END BLOCK
Editing code between the code blocks may render the file or project useless in the SDK.
4.1.1 PRJ File
The “prj” file is used by the Nokia 9000/9110 Development Environment to maintain the state of
the files, build settings, last modified times, available procedures, and available forms. When the
project is loaded, the project file time stamps are compared to the last modified time. If the
times are different then the user is notified so corrective action can be taken.
[VERSION]
1.0

[TYPE]
Nokia 9000/9110 Development Environment
[PROPERTIES]
[PROJECT INFO]
Project Name:
Project Description:
Build Directory: 0
Build Type: 0
[CHECKSUM INFO]
GP Last Modified:
GP Checksum:
GOC Last Modified:
GOC Checksum:
GOH Last Modified:
GOH Checksum:
[FORMS]
[PROCEDURES]
4.1.2 GOH File
The Nokia 9000/9110 Development Environment baseline GOH file is the Goc header file. This file
provides definitions used by the .goc files (in the same relation as between standard C source
and header files). Unlike standard C header files, these are included using the @include Goc
keyword.
// MODULE: $SHORT NAME$
// FILE: $SHORT NAME$.goh
//
// AUTHOR: $AUTHOR$
//
// REVISION HISTORY:
// Name Date Description
// ---- ---- -----------
//
// DESCRIPTION:
//
//
// RCS STAMP:
//
//
/////////////////////////////////////////////////////////////////////////
/********************************************************************
* Constants
*******************************************************************/
//{{CONSTANTS-GOH
//}}CONSTANTS-GOH
/********************************************************************

* Data Types
*******************************************************************/
//{{DATATYPES-GOH
//}}DATATYPES-GOH
/********************************************************************
* Icons
*******************************************************************/
@start iconMonikerResource, data;
/* {{FILE LIST ICON BLOCK}} */
/* {{END FILE LIST ICON BLOCK}} */
/* {{STATUS PANE ICON BLOCK}} */
/* {{END STATUS PANE ICON BLOCK}} */
@end iconMonikerResource;
/********************************************************************
* Class Definitions
*******************************************************************/
@class $SHORT NAME$VisContentClass, VisContentClass;
@endc;
//{{CLASSDEFN-GOH
@class $SHORT NAME$ProcessClass, GenProcessClass;
/* {{Class Definitions Block}} */
@endc;
//}}CLASSDEFN-GOH
4.1.3 Baseline GOC File
The GOC file contains both standard C code and GEOS constructs (such as objects and
messages). This file contains the methods that are generated after a procedure is added. It is an
empty method that exists for the Nokia developer to provide his custom implementation.
/////////////////////////////////////////////////////////////////////////
//
// PROJECT: $PROJECT NAME$
// MODULE: $SHORT NAME$
// FILE: $SHORT FILE NAME$
//
// AUTHOR: $AUTHOR$
//
// REVISION HISTORY:
// Name Date Description
// ---- ---- -----------
//
// DESCRIPTION:
//
//
// RCS STAMP:
//
//
/////////////////////////////////////////////////////////////////////////
/////////////////////////////////////////////////////////////////////////
// Include Files
/////////////////////////////////////////////////////////////////////////

//{{INCLUDE-GOC
@include <stdapp.goh>
@include <foam.goh>
$INCLUDE PROJECT GOH$
//}}INCLUDE-GOC
/////////////////////////////////////////////////////////////////////////
// Constants
/////////////////////////////////////////////////////////////////////////
Color drawColor = C_BLACK;
#define DOC_WIDTH FOAM_DEFAULT_COMPONENT_WIDTH
#define DOC_HEIGHT 480
char chartName[] = "Nokia 9000/9110 Development Environment SDK";
/////////////////////////////////////////////////////////////////////////
// Data Types
/////////////////////////////////////////////////////////////////////////
/////////////////////////////////////////////////////////////////////////
// Class Definitions
/////////////////////////////////////////////////////////////////////////
//Look in GOH File
/////////////////////////////////////////////////////////////////////////
// Class Declarations
/////////////////////////////////////////////////////////////////////////
//{{CLASSDECL-GOC
$PROCESS CLASS DECLARATION$
@classdecl $SHORT NAME$VisContentClass;
//}}CLASSDECL-GOC
/////////////////////////////////////////////////////////////////////////
// Global Variables
/////////////////////////////////////////////////////////////////////////
//{{GLOBALS-GOC
//}}GLOBALS-GOC
/////////////////////////////////////////////////////////////////////////
// Graphic Function Prototypes
/////////////////////////////////////////////////////////////////////////
void $SHORT NAME$ViewDraw( GStateHandle gstate );
/* {{BEGIN GRAPHIC FUNCTION PROTOTYPES}} -- DO NOT ERASE */
/* {{END GRAPHIC FUNCTION PROTOTYPES}} -- DO NOT ERASE */
/////////////////////////////////////////////////////////////////////////
// UI Object Resources
/////////////////////////////////////////////////////////////////////////
@start AppResource;
@object FoamSubApplicationClass $SHORT NAME$App = {
GI_visMoniker = list
{/* {{FILE LIST ICON BLOCK}} -- DO NOT ERASE */
/* {{END FILE LIST ICON BLOCK}} -- DO NOT ERASE */
/* {{STATUS PANE ICON BLOCK}} -- DO NOT ERASE */
/* {{END STATUS PANE ICON BLOCK}} -- DO NOT ERASE */
//{{DISPLAYNAME-GOC
@$SHORT NAME$TextMoniker
//}}DISPLAYNAME-GOC
};
GI_comp = @$SHORT NAME$Primary;
FSAI_launcherApp = FA_EXTRAS_APP;
gcnList( MANUFACTURER_ID_GEOWORKS, GAGCNLT_WINDOWS ) = @$SHORT NAME$Primary;
}
/* {{ICON LABEL BLOCK}} -- DO NOT ERASE */
@visMoniker $SHORT NAME$TextMoniker = "$PROGRAM NAME$";

/* {{END ICON LABEL BLOCK}} -- DO NOT ERASE */
@end AppResource;
@start Interface;
@object GenPrimaryClass $SHORT NAME$Primary = {
GI_comp = @$SHORT NAME$Box,
/* {{$SHORT NAME$ INTERFACE RESOURCE BLOCK}} -- DO NOT ERASE -- */
/* {{END $SHORT NAME$ INTERFACE RESOURCE BLOCK}} -- DO NOT ERASE -- */
@$SHORT NAME$CloseTrigger;
}
/*
* Main Form
*/
@chunk TCHAR $SHORT NAME$Title[] = "$SHORT NAME$ Main Form";
@object ComplexMonikerClass $SHORT NAME$Box = {
ComplexMoniker = GenInteractionClass;
CMI_topText = @$SHORT NAME$Title;
CMI_fontSize = FOAM_NORMAL_FONT_SIZE;
GI_comp = @$SHORT NAME$ViewInteraction;
HINT_DRAW_IN_BOX;
HINT_DRAW_SHADOW;
HINT_PLACE_MONIKER_ABOVE;
HINT_EXPAND_WIDTH_TO_FIT_PARENT;
HINT_EXPAND_HEIGHT_TO_FIT_PARENT;
HINT_COMPLEX_MONIKER_DRAW_SEPARATOR;
}
@object GenInteractionClass $SHORT NAME$ViewInteraction = {
GI_comp = @$SHORT NAME$View;
}
@object GenViewClass $SHORT NAME$View = {
GVI_docBounds = {0,0,480, 150};
GVI_color = {C_WHITE, 0, 0, 0};
GVI_horizAttrs = @default | GVDA_NO_LARGER_THAN_CONTENT
| GVDA_NO_SMALLER_THAN_CONTENT;
GVI_vertAttrs = @default | GVDA_NO_LARGER_THAN_CONTENT
| GVDA_NO_SMALLER_THAN_CONTENT
| GVDA_KEEP_ASPECT_RATIO;
GVI_attrs=(@default & ~GVA_FOCUSABLE);
GVI_content = $SHORT NAME$ViewContent;
ATTR_GEN_WINDOW_KBD_OVERRIDE = (KO_KEYBOARD_REQUIRED);
}
@object $SHORT NAME$VisContentClass $SHORT NAME$ViewContent = {
VI_bounds = {0,0,480, 150};
VCI_geoAttrs = VCGA_CUSTOM_MANAGE_CHILDREN;
}
/*
* Command Triggers
*/
@object ComplexMonikerClass $SHORT NAME$CloseTrigger = {
ComplexMoniker = GenTriggerClass;
CMI_topText = CMT_CLOSE;
GTI_actionMsg = MSG_FSA_RETURN_TO_LAUNCHER;
GTI_destination = @$SHORT NAME$App;
HINT_SEEK_MENU_BAR;
HINT_SEEK_REPLY_BAR;
HINT_SEEK_SLOT = 3;
}
/* {{$SHORT NAME$ INTERFACE BLOCK}} -- DO NOT ERASE -- */
/* {{$SHORT NAME$ END INTERFACE BLOCK}} -- DO NOT ERASE -- */
@end Interface;

/* {{RESOURCE BLOCK}} -- DO NOT ERASE -- */
/* {{END RESOURCE BLOCK}} -- DO NOT ERASE -- */
/********************************************************************
* Code for BaselineProcessClass
*******************************************************************/
/********************************************************************
* MSG_GEN_PROCESS_OPEN_APPLICATION
********************************************************************
* SYNOPSIS: Here is where we can intercept the starting of our
* GEOS application. It is a handy place to initialize
* any global variables and set up various user interface
* components.
* CALLED BY: GEOS Kernel
* PARAMETERS: AppAttachFlags attachFlags
* MemHandle launchBlock
* MemHandle extraState
* RETURNS: void
* SIDE EFFECTS: none
* STRATEGY: In this baseline application there is nothing to do,
* so we just call @callsuper to execute the standard
* behavior.
* REVISION HISTORY:
* Name Date Description
* ---- ---- -----------
*
*******************************************************************/
@method $SHORT NAME$ProcessClass, MSG_GEN_PROCESS_OPEN_APPLICATION
{@callsuper();
@call $SHORT NAME$App::MSG_GEN_APPLICATION_INSTALL_TOKEN();
} /* MSG_GEN_PROCESS_OPEN_APPLICATION */
/********************************************************************
* MSG_GEN_PROCESS_CLOSE_APPLICATION
********************************************************************
* SYNOPSIS: Here is where we can intercept the ending of our
* GEOS application. It is a handy place to free resorces
* allocated by the application or to close files.
* CALLED BY: GEOS Kernel
* PARAMETERS: void
* RETURNS: MemHandle
* SIDE EFFECTS: none
* STRATEGY: In this baseline application there is nothing to do,
* so we just call @callsuper to execute the standard
* behavior.
* REVISION HISTORY:
* Name Date Description
* ---- ---- -----------
*
*******************************************************************/
@method $SHORT NAME$ProcessClass, MSG_GEN_PROCESS_CLOSE_APPLICATION
{@callsuper ();
return(NullHandle);
} /* MSG_GEN_PROCESS_CLOSE_APPLICATION */
//Each graphic form will have a custom method generated along with a
//MSG_META_EXPOSED for redrawing the window
/* {{CUSTOM GRAPHICS STATE METHOD}} -- DO NOT ERASE -- */
@method $SHORT NAME$VisContentClass, MSG_VIS_DRAW
{@callsuper();
if ( oself == @$SHORT NAME$ViewContent )
$SHORT NAME$ViewDraw( gstate );

/* {{BEGIN VIS DRAW CONTENT}} */
/* {{END VIS DRAW CONTENT}} */
} /* End of MSG_VIS_DRAW */
void $SHORT NAME$ViewDraw( GStateHandle gstate )
{
/* {{$SHORT NAME$ DRAW BLOCK}} -- DO NOT ERASE -- */
/* {{END $SHORT NAME$ DRAW BLOCK}} -- DO NOT ERASE -- */
} /* End of $SHORT NAME$ViewDraw */
/* {{USER-DEFINED METHOD BLOCK}} -- DO NOT ERASE -- */
4.1.4 Baseline GP File
The GP file provides the geode parameters for the GEOS linker (Glue). These parameters will give
the Glue linker the necessary information when linking a geode.
#####################################################################
#
#
# PROJECT: $PROJECT NAME$
# MODULE: $SHORT NAME$
# FILE: $SHORT FILE NAME$
#
# AUTHOR: $AUTHOR$
#
# REVISION HISTORY:
# Name Date Description
# ---- ---- -----------
#
# DESCRIPTION:
#
#
# RCS STAMP:
#
#
#####################################################################
#
# Permanent name: This is required by Glue to set the permanent name
# and extension of the geode. The permanent name of a library is what
# goes in the imported library table of a client geode (along with the
# protocol number). It is also what Swat uses to name the patient.
#
name $FULL SHORT NAME$
#
# Long filename: this name can displayed by GeoManager. "EC " is prepended to
# this when the error-checking version is linked by Glue.
#
longname "$PROJECT NAME$"
#
# Specify geode type: This geode is an application, and will have its
# own process (thread).
#
#//{{TYPE-GP
type $GEODE TYPE$
#//}}TYPE-GP
#

# Specify class name for application thread. Messages sent to the application
# thread (aka "process" when specified as the output of a UI object) will be
# handled by the process class.
#
class $PROCESS CLASS NAME$
#
# Specify application object. This is the object that serves as the top-level
# UI object in the application.
#
appobj $APPLICATION OBJECT$
#
# Token: The four-letter name is used by GeoManager to locate the
# icon for this application in the token database. The tokenid
# number corresponds to the manufacturer ID of the program's author
# for uniqueness of the token. Since this is a sample application, we
# use the manufacturer ID for the SDK, which is 8.
#
tokenchars "$TOKEN CHARS$"
tokenid $TOKEN ID$
#
# Heapspace: This is roughly the non-discardable memory usage
# of the application and any transient libraries that it depends on,
# plus an additional amount for thread activity. To find the heapspace
# for an application, use the Swat "heapspace" command.
#
heapspace 8k
#
# Libraries: list which libraries are used by the application.
#
#//{{LIBRARIES-GP
$LIBRARIES$
#//}}LIBRARIES-GP
#
# Resources: list all resource blocks which are used by the application whose
# allocation flags can't be inferred by Glue. Usually this is needed only for
# object blocks, fixed code resources, or data resources that are read-only.
# Standard discardable code resources do not need to be mentioned.
#
#//{{EXPORT-GP
export $SHORT NAME$VisContentClass
#//}}EXPORT-GP
#//{{RESOURCES-GP
resource APPRESOURCE ui-object
resource INTERFACE ui-object
#//{{RESOURCES BLOCK}} -- DO NOT ERASE --
#//{{END RESOURCES BLOCK}} -- DO NOT ERASE --
#//}}RESOURCES-GP

5Opening a project
To open an existing project, go to the File menu and choose Open…
Navigate to your project directory from the File selection dialog, and choose your PRJ file.