Built-in Applications and System Data

System Data

2. Add a frame called

soupervisor

to your application's base view. Note that

this means you cannot add a

soupervisor

frame to an autopart unless

GetRoot.(kAppSymbol)

exists. This frame must have a slot called

type

.

The possible values for the

type

slot are

'moveOnly

Allows a user to move all soup entries to a different store.

'fileOnly

Allows a user to file all soup entries to a different folder.

'all

Allows a user to move and file all soup entries.

3. Create a soup icon whose

ownerApp

slot is your application's application

symbol; see "Adding a Soup Icon" beginning on page 19-40.

If you wish to gain control over this process (or some part of it), you may define
one or more of the following optional methods in your soupervisor frame:

FileSoup

,

FileEntry

, and

MoveEntry

. These three methods are described in

"The Soupervisor Frame" (page 16-86) in Newton Programmer's Reference.

System Data

19

This section describes the API to system stored data and how to store application
preferences in the system soup.

About System Data

19

The system stores user preferences and other system information in a soup called
"System," which you should reference with the constant

ROM_SystemSoupName

.

This soup holds information such as the user's address and phone number, the
currently selected printer, and handwriting recognition settings.

Your application can use this data to customize itself to the user's current situation,
and save the user some writing or tapping. Your application can be registered to be
notified when changes are made to this data.

You may also store a single entry in this soup with application-specific preferences.

Using System Data

19

This section describes

The functions used to access user configuration data, and to register an
application to be notified of changes to this data.

How to create an entry in the system soup for your application's preferences.