O:

A text file which is input to ROMBUILD, the ROM building tool. It describes what files go to make up the ROM, and how they are laid out, among other things.

In the context of client-server architecture, an object represents a single resource managed by a server. Clients refer to it using a handle.

See also: handle  

A home for a set of related reference counting objects. Adding an object to an object container ensures that it gets assigned a unique id.

See also: object  reference counting object  

This is used to create an object container. It ensures that the object containers it produces generate unique ids within the server.

See also: object container  

An object that generates handle numbers for reference counting objects. Used to store objects. Adding an object to an object index returns its id.

See also: object  reference counting object  

An object container which owns the subsession objects it contains; it is responsible for their deletion.

See also: object container  subsession object  

Receives notification from an agenda model's observer controller whenever an entry or to-do list is added, updated or deleted in the agenda model.

See also: observer controller  

Notifies all observers that have been registered with the agenda model when an entry or to-do list is added, updated or deleted.

See also: observer  

Acronym for the One Definition Rule.

See also: One Definition Rule  

One Definition Rule: No translation unit (in an application including all its DLLs, statically linked or dynamically loaded) shall contain more than one definition of any variable, function, class type, enumeration type or template. A consequence of the One Definition Rule, is that all objects (including variables and functions) that semantically refer to the same C++ object map onto the same address in object code. For example, say we have the function, inline int getCounter { static int iCounter = 0; return iCounter++ ; }. If the One Definition Rule holds, all instances of this in-lined function in an application, including all its dependant binaries (statically linked or dynamically loaded) will access the same static variable iCounter. Note that in Symbian OS as in Microsoft Windows, the One Definition Rule does not hold; whereas on Unix and Linux the One Definition Rule does hold.

An event generated by the window server when the machine is switched on.

Online certification status protocol. A communication protocol to determine whether a particular certificate has been revoked. Described in RFC2560.

A system to allow plug-in support for different font types.

An open source toolkit implementing the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols as well as a full-strength general purpose cryptography library.

An identifier that identifies the type of request being sent from a client to a server.

An active object that is responsible for an asynchronous request to the Message Server.

A concrete control that may be used to toggle an application state. A group of option buttons may be used to toggle mutually exclusive application states.

See also: check box  

Organiser Programming Language. An open source BASIC-like language that can be used for rapid application development.

An OPL extension DLL providing language extension procedures.

See also: language extension procedure  OXH  OPL  

A number which identifies a column in a particular column set or rowset.

See also: column  column set  rowset  

A build which produces a DLL export table that indexes functions by ordinal.

See also: DLL  export  DLL export table  name build  

The position of a window in the z-order, i.e. from front to back on the screen. The front-most window (the window in the foreground) has an ordinal position of 0.

Whether page is vertically or horizontally aligned.

See also: portrait  landscape  

The top-left corner of a control.

(1) an object which cannot be accessed either as a local automatic variable, a global variable, via a pointer or as the result of any function call; (2) to create such an object Orphaned objects are undesirable as they use unrecoverable system resources. There are two types of orphaned object: objects orphaned on the stack and objects orphaned on the heap. Orphans can be created through program errors, or by a function leaving. It does not matter if T objects are orphaned on the stack. All other orphans are undesirable and, in the case of leave processing, it is essential to ensure that cleanup code handles objects that would otherwise be orphaned.

See also: leave  cleanup  

When a session with the alarm server closes the connection it can orphan the alarm. This alarm will be serviced after the session closes. An orphan alarm has no session owner and no session is notified when the alarm is due.

See also: Timed alarm  untimed alarm  clock alarm  snoozed alarm  session alarm  

An agenda entry may be stored inline or out of line. Out of line means that the entry's rich text object is stored in an embedded store in the entry's stream. An agenda entry is set to be stored out of line if its rich text object is large.

See also: inline  

A contact item containing information about the device's owner. This can be sent to another compatible electronic device as a vCard.

See also: contact item  

The messaging service that is the ultimate parent of an entry.

If a window group is closed while it has the keyboard focus, its owning window group receives the focus. This will be the default owning window group, unless the window group has called SetOwningWindowGroup().

See also: default owning window group  

An OPL header file for inclusion in OPL source code, specifying the public interface to an OPX. Published by the OPX provider.

See also: OPX  language extension procedure