Palm OS Programming
The Developer's Guide
Published on 22. October 2001
704 pages
978-1-4493-6908-8 (ISBN)
Description
With more than 16 million PDAs shipped to date, Palm has defined the market for handhelds, having dominated this class of computing devices ever since it began to outpace competitors six years ago. The company's strength is the Palm OS, and developers loyal to this powerful and versatile operating system have created more than 10,000 applications for it. Devices from Handspring, Sony, Symbol, HandEra, Kyocera, and Samsung now use Palm OS, and the number of registered Palm Developers has jumped to 130,000.If you know C or C++, and want to join those who are satisfying the demand for wireless applications, then Palm OS Programming: The Developer's Guide, Second Edition is the book for you. With expanded coverage of the Palm OS--up to and including the latest version, 4.0--this new edition shows intermediate to experienced C programmers how to build a Palm application from the ground up. There is even useful information for beginners.Everything you need to write a Palm OS application is here, from user interface design, to coding a handheld application, to writing an associated desktop conduit. All the major development environments are discussed, including commercial products such as Metroworks CodeWarrior, Java-based environments such as Sun KVM and IBM VisualAge Micro Edition, and the Free Software Foundation's PRC-Tools or GCC. The focus, however, is C programming with CodeWarrior and PRC-Tools. New additions to the second edition include:A tutorial that takes a C programmer through the installation of necessary tools and the creation of a small handheld application.A new chapter on memory, with a comprehensive discussion of the Memory Manager APIs.Greatly expanded discussions of forms, forms objects, and new APIs for the Palm OS.Updated chapters on conduits that reflect the newer Conduit Development Kit.The best-selling first edition of this book is still considered the definitive guide for serious Palm programmers; it's used as the basis of Palm's own developer training materials. Our expanded second edition promises to set the standard for the next generation of Palm developers.
More details
Other editions
Additional editions
Software
11/2001
2nd Edition
O'Reilly
€60.50
Shipment within 3-4 weeks
Content
- Intro
- Table of Contents
- Preface
- What's New in This Edition
- The Source Code Web Site
- Using Code Examples
- Whom This Book Is for: C/C++ Programmers
- What This Book Is About and How to Read It
- How to Read This Book
- The Skip-Through Approach
- The Cover-to-Cover Approach
- The In-Front-of-a-Computer Approach
- Conventions Used in This Book
- How to Contact Us
- Versions of Tools
- Whom We Need to Thank
- Part I
- The Palm Solution
- How Palm Succeeded
- The Magic Formula
- Why Palm Succeeded Where So Many Failed
- No One Would Make a Good Enough Device
- Elements in the Magic Formula
- Easy to Carry
- Inexpensive
- Expandable
- Hardware Expandability
- Software Expandability
- Developing for the Platform
- Expandability and the future
- Expandability allows users to accomplish different tasks
- Effortlessly Connects to a Desktop Computer
- What Palm OS Devices Don't Have and Why
- A Keyboard
- Text-Recognition Software
- A Powerful Processor
- Works Great and Is Simple to Use
- Battery Life
- Common Handheld Tasks Are Simple and Fast
- Designing Applications for Palm Devices
- Essential Design Elements
- Designing for a small screen size
- Limiting text input on the handheld
- Seamless syncing
- Making the application small
- Making the application fast
- User Interface Guidelines
- Elements in a Palm Application
- The two-part solution
- HotSync Overview
- In Conclusion
- Technical Overview and Development Environments
- Palm OS Overview
- Interaction Between an Application and the OS
- Memory
- Events
- Resources
- Forms and Controls
- Communications
- Miscellaneous
- Conduit Overview
- Handheld Development Environments
- CodeWarrior for Palm OS
- Developing on the Macintosh
- Developing on Windows
- PRC-Tools
- What's in PRC-Tools?
- Extras
- Tools Directly from Palm
- Alternative Development Environments
- Java
- Sun KVM
- IBM VisualAge Micro Edition
- Jump
- Waba
- PocketStudio
- Pocket C
- Assembler SDK (ASDK)
- Pocket Smalltalk
- High-Level Forms Development
- Satellite Forms
- AppForge
- Pendragon Forms
- NS Basic
- Handheld Development Recommendations
- Developing Using Mac OS
- Developing Using Unix
- Developing Using Windows
- Switching Platforms
- Switching development environments
- Conduit Development
- What Is a Conduit?
- Using C/C++
- Using Java
- In Conclusion
- Designing a Solution
- User Interface Elements in the Palm OS
- Alerts
- Forms
- Menus, Menu Items, and Menu Bars
- Placement
- Tables and Lists
- Placement
- Buttons
- Placement
- Checkboxes
- Command Toolbar
- Fields
- Placement
- Form Bitmap
- Gadgets
- Graffiti Shift Indicator
- Graffiti Shift Indicator placement
- Label
- Pop-up Trigger
- Push Button
- Placement
- Repeating Button
- Scrollbar
- Placement
- Selector Trigger
- Sliders
- Designing with a Particular User in Mind
- Comparing Date Book, Datebook+, and DateBk4
- DateBk4's Extra Features
- Menu icon
- Split display and time information
- Buttons and their views
- Buttons unique to DateBk4
- Why the Designs of Date Book, Datebook+, and DateBk4 Differ
- Who is the user?
- The 80/20 Rule
- Date Book: The Most Important Aspects of an Application
- Date Book tasks and times
- How the 80/20 rule was implemented within Date Book's design
- Datebook+: The Most Important Aspects of an Application
- The "p" for P.M.
- Extra calendar views
- Datebook+ tasks and times
- How the 80/20 rule was implemented within Datebook+'s design
- DateBk4: The Most Important Aspects of an Application
- DateBk4 tasks and times
- How the 80/20 rule was implemented within DateBk4's design
- What Should Be Sacrificed?
- DateBk4's pop-up common task list
- The split display
- Button action and common activity
- Abbreviating button names-hitting the screen-size wall
- Buttons that don't look like buttons
- Preference dialog boxes
- Who Is Your User?
- The Well-Designed Form
- The To Do List-A Well-Designed Main Form
- The Security Application-A Not-So-Well-Designed Form
- The Date Book-A Well-Designed Dialog Box
- WordSmith-A Well-Designed Dialog Box
- The Address Application-A Well-Designed Alert
- Bejeweled-A Really Well-Designed Alert
- Taking Advantage of the Unique Elements in an Application
- Great hinting
- Anticipating the user's needs
- Hidden tricks that save time
- How to enter an odd appointment time
- Other Design Issues
- Gotchas from the Desktop
- Handling passwords on a handheld
- Hey, where's the Exit button?
- Design Issues
- How the Sample Applications Are Useful
- User Interface of the Sales Application
- The Sales Application Customer List
- The Customer list
- New Customer
- Beam All Customers/Send All Customers
- The Order Form
- Creating items
- Another way to add items to an order
- Modifying an item in an order
- Adding duplicate items to an order
- Deleting an item in an order
- Changing Customer Information
- Customer details
- Order details
- Deleting the Customer
- Beaming the Customer
- Edit and Options Menus
- Designing the Sales Application
- Clarify the Tasks
- The Start Screen
- Design Trade-offs in the Sample Application
- Adding items to an order
- Where to put customer information
- Creating a new customer
- Beaming or sending a list of customers
- Deleting a customer
- Designing for a Small Screen
- Designing the Databases
- Customers
- Products
- Orders
- Categories
- Designing the Conduit
- Processor-Intensive Tasks
- Design of the Sales Application Conduit
- Design Summary
- Part II
- Tutorial
- POSE
- Getting and Installing POSE
- Emulator Skins
- POSE and ROM Images
- Retrieving ROM from a Handheld
- Creating a New POSE Session
- CodeWarrior
- What CodeWarrior Includes
- Installing 4.0 SDK
- Installing additional examples
- Installing PilRC Plug-in
- Installing OReilly Stationery
- CodeWarrior Setup
- Launching POSE automatically
- Multifile searching
- Creating a New Project
- Making a PRC
- CodeWarrior IDE
- The Project window
- The Project Settings dialog box
- Constructor for Palm OS
- PRC-Tools
- What PRC-Tools Includes
- Installing on Windows
- Installing Cygwin shell and utilities
- Installing PRC-Tools
- Installing the 4.0 SDK
- Installing PilRC
- Installing on Unix
- Installing PRC-Tools
- Installing the 4.0 SDK
- Installing PilRC
- Installing OReilly Sample project
- Cloning the Sample Project
- Customizing the Output File
- A Non-Debug Build
- Installing a PRC on the Handheld
- Using Windows
- Using Mac OS
- Using Unix
- Installing PRC on POSE
- Get Your ROM Image
- Installing the Sample Application
- Modifying the Sample Application
- Change the Application Name
- Change the Location of a Button
- Register the Creator ID and Set It Appropriately
- Changing the creator ID in CodeWarrior
- Changing the creator ID in PRC-Tools
- Add a Second Button That Beeps
- Structure of an Application
- Terminology
- Palm OS Conventions
- Types
- Function and Manager Naming Conventions
- C Library Conventions
- The Palm OS and an Application
- The Main Routine: PilotMain
- A quick look at PilotMain
- The Startup Routine: AppStart
- The Closing Routine: AppStop
- The Main Event Loop
- Handling events with EvtGetEvent
- The Event Queue and Application Event Loop
- The Four Routines of the Main Event Loop
- SysHandleEvent
- MenuHandleEvent
- AppHandleEvent
- FrmDispatchEvent
- A Simple Application-OReilly Starter
- What the Application Does-Its User Interface
- An Overview of the Source Files
- The Source File of Main.c
- The Form Files of the Application
- The EventType data structure
- The Utility and Resource Files
- Header Files
- OReilly Starter Summary
- Other Times Your Application Is Called
- Launch Codes
- Launch Flags
- Scenarios
- Normal launch
- Find when another application is active
- Find when your application is active
- Examples
- Handling a Pen-Down Event
- Handling a Graffiti Character
- Overriding Hard-Button Behavior
- Controlling the Exiting of an Application
- What to Remember
- Memory Manager
- Types of Memory
- Read-Only Memory (ROM)
- Random-Access Memory (RAM)
- Maintaining state
- Writing to the RAM memory
- Amount of dynamic memory available
- Dynamic Memory Allocation
- Using Memory Handles
- Memory Chunk Size Limitations
- Dynamic Memory APIs
- Allocation
- Locking memory chunks
- Memory size information
- Heap information
- Example
- Writing to a block using a structure
- Strings in a block
- Stack Space
- APIs
- Example
- Setting stack size
- Determining stack size
- Determining how much stack has been used
- Determining the amount of stack remaining
- Handling Large Amounts of Data
- Relocatable Chunks in the Storage Area
- Feature Memory
- Allocating feature memory
- Retrieving feature memory
- Freeing feature memory
- File Streaming
- Owner IDs
- Persistent Memory and Owner IDs
- APIs
- Owner ID Example
- Cards and Local IDs
- APIs
- Using Memory Effectively
- Deciding Whether to Use Pointers or Handles
- Check Allocations and Resizes
- Our Philosophy on Using Memory Efficiently
- MemoryTestAPIs Example
- The Code
- Handle > MemHandleNew
- Handle > MemHandleFree
- Handle > MemHandleLock
- Handle > MemHandleUnlock
- Handle > Write
- Handle > Read
- Handle > FreeSpace
- Handle > DmNewHandle
- FeatureMem > FtrPtrNew and write
- FeatureMem > FtrPtrGet and read
- FeatureMem > FtrPtrFree
- Stack > Total
- Stack > Remaining
- Stack > Used
- Testing the Application
- What to Remember
- Debugging Palm Applications
- POSE
- POSE Sessions
- Installing Applications and PDBs on POSE
- Communications
- Emulating serial
- Emulating TCP/IP
- Error Checking with POSE
- Logging
- Profiling
- Remote Scripting
- Major Advantages of POSE
- Minor Disadvantages of POSE
- Graffiti Debugging Shortcuts
- Source-Level Debugging
- Source-Level Debugging with CodeWarrior
- Choosing a target
- Debugging commands
- Console window
- Source-Level Debugging with PRC-Tools
- Gremlins
- Gremlin ranges
- Saved Gremlin state
- Gremlins and Gadgets
- Using Gremlins Repeatedly
- Optimizing Gremlin Debugging
- Error Manager
- Palm OS Sources
- Low-Level Debugging with PalmDebugger
- Device Reset
- Using Simulator on Mac OS
- Release/Debug Targets
- Releasing and debugging builds in CodeWarrior
- Releasing and debugging builds in PRC-Tools
- Resources and Forms
- Resources
- Creating Resources in PilRC
- The pretty points of PilRC
- PilRC example
- Aligning form objects with PilRC
- Using constants for your resources
- Reading Resources
- Writing Resources
- Form Characteristics
- Form Events
- Form-Level APIs
- Modeless Forms
- Alerts
- Customizing an Alert
- Alert APIs
- Alert Example
- Tips on Creating Alerts
- Modal Dialog Boxes
- Dialog Box APIs
- Flexible Modal Dialog Boxes
- A Tip for Modal Forms
- Modal Form Sizes
- Help for Modal Forms
- Forms in the Sales Application
- Alerts
- Defining the alerts
- Calling FrmAlert in our application
- Calling FrmCustomAlert
- Delete Customer
- Form Objects
- Form Object Characteristics
- What We Talk About Next
- Form Object Events
- Events Generated by a Successful Tap
- Events Generated by Maintaining a Press
- Events Generated by the Start of a Tap
- Events Generated by the End of an Unsuccessful Tap
- Form Object APIs
- Converting Between IDs and Indexes
- Hiding and Showing Objects
- Form Object Pointers
- Error Checking
- Types of Form Objects
- Labels
- Example
- Bitmaps
- Application icons
- Graffiti Shift Indicator
- Lists
- A sample that displays a specific list item
- Custom versus noncustom lists
- Creating a runtime list with LstSetListChoices
- Creating a runtime list with LstSetDrawFunction
- Controls
- Control APIs
- Using graphical labels rather than text labels for controls
- Buttons
- Push buttons
- Checkboxes
- Selector triggers
- Repeating buttons
- Pop-up trigger objects
- Sliders
- Gadgets
- Gadget APIs
- Gadget responsibilities
- A simple gadget
- A sample using extended gadgets
- Gadget tip
- Fields
- Setting text in a field
- Field utility routines
- Modifying text in a field
- Getting text from a field
- Setting the focus of a field
- Field gotchas
- Scrollbars
- Scrollbar coding requirements
- Updating the scrollbar based on the insertion point
- Updating the scrollbar when the number of lines changes
- Updating the display when the scrollbar moves
- Updating the display when the scroll buttons are used
- Scrolling a full page
- Tables
- Display-only data types
- Edit and display data types
- Display-only data types
- Editable data types
- Initializing tables
- Resource
- Initialization of the records in the database
- Initialization of the simple table sample
- Column 0: handling numbers
- Column 1: a checkbox
- Column 2: a label
- Column 3: a date
- Column 4: a pop-up trigger
- Column 5: handling text
- Column 6: handling custom content
- Displaying the columns
- Custom load routines
- Custom save routine
- Releasing the records
- Custom draw routine
- Handling a table event
- Sales Application Forms and Form Objects
- Edit Customer
- Creating the Customer Information form
- Event handler for the form
- Initialization code
- Utility routines
- Item Details
- Item details display code
- Event handler code
- Handling the pop-up trigger and list
- Customers Form
- Initialization routines
- Event handler
- Order Form
- Initialization routine
- Global variables
- Setting pop-up triggers and fields
- Hiding and showing objects
- Initializing the data
- Handling keystrokes
- Handling events
- Scrolling
- Deselecting a row
- Switching Forms
- Databases
- Overview of Databases and Records
- Record Databases
- Resource Databases
- Write-Protected Memory
- Palm 3.0 OS Heap Changes
- Where Databases Are Stored
- How Records Are Stored Versus How They Are Referenced
- Opening, Creating, and Closing Databases
- Opening a Database
- Opening by type and creator
- Opening by name
- Closing a Database
- Creating a Database
- Create your database in your AppStart routine
- Creating a database from an image
- Creating the Application Info Block in a Database
- Iterating Through Databases
- Working with Records
- Reading from a Record
- Modifying a Record
- Creating a New Record
- Adding at the beginning of the database
- Adding at the end of the database
- Deleting a Record
- Deleting a brand new record
- Deleting a record that exists also on the desktop
- Deleting a record that the user wants archived
- Where to put archived and deleted records
- Handling Secret Records
- Determining the Number of Records
- Iterating Through the Records in a Database
- Finding a Record
- Finding a record given a unique ID
- Sorted Databases
- Comparison function
- Adding in sort order
- Finding a record given a key
- Sorting the records in a database
- Sorting after a sync
- Modifying a record in a sorted database
- Dealing with Large Records
- File streaming
- Multiple chunks in a separate database
- Editing a Record in Place
- Initialize the field with the handle
- Cleanup once the editing is finished
- Examining Databases in the Sales Sample
- Defining the Sales Databases
- Reading and Writing the Customer
- Reading and Writing Products
- Working with Orders
- Creating or Opening the Databases
- Closing the Sales Databases
- Initializing the Sales Databases
- Initializing the customer database
- Initializing the product database
- Comparison routine for sorting
- Initializing the Orders database
- The Customers Form
- Editing Customers
- The Order Form
- Editing an item
- Deleting an item
- Adding a new item
- Finishing an Order record
- The Item Form
- Summary
- Menus
- Menu User Interface
- Arranging Menus
- Standard Menu Items
- Edit menu
- About application
- Applications Can Have Multiple Sets of Menus
- Applications Can Have Dynamic Menus
- Common Menu Shortcuts
- Accessing the Command toolbar with a menu shortcut
- Menu Resources
- Associating Menu Bars with Forms
- Application Code for Menus
- MenuHandleEvent
- MyFormHandleEvent
- Handling Items in the Edit Menu
- Handling Cut and Paste correctly
- The About Menu
- Menu Erase Status
- Handling Unusable Menu Items
- A good time to remove a menu item
- Adding a menu item dynamically
- Using a separate menu bar
- Adding to the Command Bar
- Adding Menus to the Sample Application
- The Menu Bars
- Menu Definitions
- Handling Common Menus
- The Customers Form
- The Order Form
- Summary
- Extras
- Find
- Overview of Find
- The objectives of Find
- Find minimizes memory use
- A Walkthrough of Finding Items
- The application's response to a Find request
- Handling a Find request with multiple databases
- Navigating to a found item
- Displaying a found item from a running application
- Displaying a found item from a closed application
- Find in the Sales Application
- Handling the Find request
- Searching for matching strings
- Displaying the found item
- Exchange
- The Exchange Manager
- Overview of Sending
- A Programming Walkthrough of Sending and Receiving
- Implementing Exchange
- Optimization tips
- Debugging tips
- General tips
- Step-by-Step Implementation Checklist
- Determine data interchange format
- Add user interface
- Send an entry
- Receive an entry
- Display received item
- Send an entire category
- Receive an entire category
- Test all possibilities
- Sales Application
- Sending a single customer
- Receiving a record
- Sending all customers
- Receiving all customers
- Communications
- Serial Communications
- Serial APIs
- Connection Manager
- Tips for Using the Serial Manager
- Sample Serial Application
- Features of the sample application
- The GPS device
- The NMEA protocol
- Opening the serial port
- Closing the serial port
- Routines that work with the old and new Serial Managers
- Allowing the user to choose a port
- Opening the port
- The Main form
- Setting the receive buffer to hold data
- The event loop
- The event handler
- Updating the display with new GPS data
- Alerting the user if GPS hasn't been heard from lately
- Reading the GPS data
- Updating the display
- Sample Asynchronous Receive
- The application's resource and global variable
- The wakeup handler
- The event handler
- Reading the data
- TCP/IP Communications
- Network API
- Berkeley Sockets API
- Palm OS NetLib API
- Net library and the Berkeley Sockets API
- Tips for Using TCP/IP
- Sample Network Application
- Creating the sample application on Linux
- The Linux main program
- Linux include files and global definitions
- Sending the mail
- Connecting to the server
- Getting a port
- Reading data character by character
- Sending data character by character
- Testing the Linux application
- Porting the Linux application to Palm OS
- Part III
- Getting Started with Conduits
- Overview of Conduits
- What Does a Conduit Do?
- Conduit Development on Windows
- CDK versions and Palm Desktop
- Using C++
- Using Java
- Using Visual Basic or other COM-creating environments
- Conduit Development on Macintosh
- Required Elements in a Minimal Conduit
- Using the Backup Conduit
- Applications That Might Use the Backup Conduit
- Using System Prefs Instead
- Setting the Backup Bit for a Database
- Set the Backup Bit for Every Application
- Registering and Unregistering
- The Old, Ugly Way
- The New, Sleek Way
- Conduit Entry Information Needed to Register
- Required conduit entries
- Optional entries
- JSync Suite entries
- COM Sync Suite entries
- Registering and Unregistering Manually Using CondCfg
- Using Desktop APIs
- Registering/Unregistering Conduit Manager APIs
- Installing the conduit
- ConduitInstall.exe
- Automatically uninstalling a conduit
- The HotSync APIs
- Retrieving Users and Installing Application APIs
- A Complicated Wrinkle-Finding the Correct DLL
- The solution to finding the correct DLL
- Implementing the solution
- The elements in our solution
- Modifying the application
- The code for PalmDLLShim
- Important Issues for Creating an Installer
- What the installer needs to do
- How the installer will work
- Conduit Entry Points
- Required Entry Points
- Optional Entry Points
- Optional File Linking entry points
- The HotSync Log
- long LogAddEntry(LPCTSTR logString, Activity act, BOOL timestamp)
- long LogAddFormattedEntry(Activity act, BOOL timestamp, const char* dataString, ...)
- When the HotSync Button Is Pressed
- Using Conduit Inspector to Verify Your Conduit
- Running the Conduit Inspector Manually
- Running the Conduit Inspector from the HotSync Application
- Syncing from POSE
- If You Are Using Palm OS 3.3 or Later
- If You Are Using Palm OS 3.0 to 3.2
- Creating a Minimal Sales Conduit
- Code for the Sales Conduit
- Registering the Conduit
- Source-Level Debugging
- Testing
- Proving that CfgConduit works
- Seeing the conduit in the HotSync log
- Setting the conduit to Do nothing
- Moving Data to and from the Handheld with a Conduit
- Conduit Requirements
- Where to Store Data
- Creating, Opening, and Closing Databases
- Creating a Database
- Opening a Database
- Closing the Database
- Moving Data to the Handheld
- Deleting Existing Records
- Writing Records
- Writing the AppInfo Block
- Moving Data to the Desktop
- Finding the Number of Records
- Reading Records
- Iterating through each record, stopping only for altered ones
- Looking up exact records via unique record ID
- Iterating through the records of a database from beginning to end
- The CRawRecordInfo class
- Reading the AppInfo Block
- Deleted/Archived Records
- Archiving records
- Deleting records
- Keeping the HotSync Progress Dialog Box Alive
- When the HotSync Button Is Pressed
- Portability Issues
- Byte Ordering
- Structure Packing
- The Sales Conduit
- Format Used to Store Data on the Desktop
- Modifying OpenConduit
- General Code
- Database defines
- Globals
- Data structures
- Moving Data to the Handheld
- Moving customers to the handheld
- Moving products to the handheld
- Moving Data to the Desktop
- Moving orders to the desktop
- Moving customers to the desktop
- Two-Way Syncing
- The Logic of Syncing
- Thorny Comparisons-Changes to the Same Records on Both Platforms
- The rule-first, do no harm
- A record is deleted on one database and modified on the other
- A record is archived on one database and changed on the other
- A record is archived on one database and deleted on the other
- A record is changed on one database and changed differently on the other
- A record is changed on one database and changed identically on the other
- Fast Sync
- Examine the handheld data
- Examine the local desktop data
- Dispose of the old data
- Save a backup file
- Slow Sync
- Comparing the backup record to the current records
- MFC Conduit Framework
- Generic Conduit Framework
- Advantages of Using Generic Conduit
- Generic Conduit Classes
- CPalmRecord
- CPCategory
- CPCategoryMgr
- CPDbBaseMgr
- CHHMgr
- CPcMgr
- CPLogging
- CSynchronizer
- Using the Wizard to Create a Minimal Generic Conduit
- Registering the Conduit
- What the Conduit Does
- Custom File Formats
- The StoreDB Routine
- The RetrieveDB Routine
- Handling Categories
- Sales Conduit Based on Generic Conduit
- CSalesGenPCMgr
- CSalesGenPCMgr constructor
- CSalesGenPCMgr destructor
- StoreDB function
- Retrieving a database
- Reading customer information
- Customizing resources
- Registering the conduit
- Testing the conduit
- CSalesGenSynchronizer
- Class definition
- Modifying Perform to add uploading and downloading products and orders
- Testing the Conduit
- Part IV
- Where to Go from Here
- Palm Programming Book Web Site
- The Official Palm Developer Site
- Getting Your Application Creator ID
- Knowledge Base
- Resource Pavilion
- Palm-Powered Compatible Solution
- Palm Programming Mailing Lists
- Palm OS Developer Exchange
- Third-Party Palm Programming Resources
- Newsgroups
- Palm Programming FAQ
- Sales Source Code
- Source Code
- Customer.c
- Customers.c
- Data.c
- Exchange.c
- Item.c
- Order.c
- Sales.c
- Utils.c
- Headers
- Common.h
- Customer.h
- Customers.h
- CWDebugDefines.h
- Data.h
- Exchange.h
- Item.h
- Order.h
- SalesRsc.h
- Utils.h
- Resources
- Sales.rcp
- PRC-Tools Build Files
- Makefile
- Sales.def
- PilRC Manual
- Usage
- Examples
- Understanding the Manual
- Syntax
- Types
- Comments
- Include Files
- Resource Language Reference
- FORM (tFRM)
- MENU (MBAR)
- ALERT (Talt)
- VERSION
- STRING (tSTR)
- STRINGTABLE (tSTL)
- CATEGORIES (tAIS)
- APPLICATIONICONNAME (tAIN)
- APPLICATION (APPL)
- LAUNCHERCATEGORY (taic)
- ICON (tAIB)
- SMALLICON (tAIB)
- BITMAP (Tbmp) (tbsb)
- TRAP (TRAP)
- FONT (NFNT)
- FONTINDEX
- HEX
- DATA
- INTEGER (tint)
- BYTELIST (BLST)
- WORDLIST (wrdl)
- LONGWORDLIST (DLST)
- PALETTETABLE (tclt)
- FEATURE (tfea)
- GRAFFITIINPUTAREA (silk)
- COUNTRYLOCALISATION (cnty)
- KEYBOARD (tkbd)
- MIDI (MIDI)
- International Support
- Example
- TRANSLATION
- Notes:
- Example
- Known Bugs
- Index
