C H A P T E R 1 2
Special-Purpose Objects for Data Storage and Retrieval
12-4
About Special-Purpose Storage Objects
Except for
soup
parts, all the parts listed in Table 12-1 are called frame parts
because they include a part frame which holds the items comprising the frame part.
Such items may include icons, scripts, other parts, binary data and so on. A
Such items may include icons, scripts, other parts, binary data and so on. A
soup
part, on the other hand, does not have a part frame and is composed of soup data only.
When a frame part is loaded, the system disperses the contents of its part frame to
the appropriate subsystems. For example, in addition to the application itself,
which is a
the appropriate subsystems. For example, in addition to the application itself,
which is a
form
part used by the Extras Drawer, the part frame in an application
package might include a custom icon used by the Extras Drawer, a custom dictionary
used by the recognition subsystem, a soup part that provides application data, and
an
used by the recognition subsystem, a soup part that provides application data, and
an
InstallScript
function that performs application-specific setup tasks.
Store Parts
12
A store part is a part that encapsulates a read-only store. Because you can build
store parts into application packages, the store part is sometimes referred to as a
package store.
store parts into application packages, the store part is sometimes referred to as a
package store.
Soups can reside on package stores, just as they do on normal stores; however,
because package stores are read-only, soups residing on package stores must also
be read-only. Store parts can be used to provide soup-like access to read-only data
residing in an application package.
because package stores are read-only, soups residing on package stores must also
be read-only. Store parts can be used to provide soup-like access to read-only data
residing in an application package.
For more information about the characteristics of soups, see "Soups" on page 11-7
and "Using Soups" on page 11-32.
and "Using Soups" on page 11-32.
Mock Entries
12
A mock entry is a NewtonScript object that mimics the behavior of a soup entry.
The mock entry is a foundation object you can use to build up a suite of objects
that acts like the system-supplied store, soup, cursor, and entry objects. For
example, you could create a mock entry object that uses a serial communications
link to retrieve a record from a remote database; additional objects could implement
methods to provide cursor-like access to these mock entries, just as if they resided
The mock entry is a foundation object you can use to build up a suite of objects
that acts like the system-supplied store, soup, cursor, and entry objects. For
example, you could create a mock entry object that uses a serial communications
link to retrieve a record from a remote database; additional objects could implement
methods to provide cursor-like access to these mock entries, just as if they resided
Table 12-1
Parts and type identifiers
Part
Type
Description
Application
form
Application.
Book
book
Book created by Newton Book Maker or Newton Press.
Auto part
auto
Background application/extension.
Store part
soup
Read-only soup.
Dictionary
dict
Custom dictionary for Newton recognition subsystem.
Font
font
Additional font.