SDK Tools Guides

Home

MoSync Glossary

MoSync introduces a few new terms, and uses some others in a new way. Here we briefly explain these terms and how we interpret them.

API

A set of syscalls and other low-level functions that provide access to one or more basic features of a device. We sometimes use this term rather broadly. Examples include the Sockets API and the Map API.

Connection

A serial connection to a remote machine, identified by a Handle. There are different types of connections, including TCP, HTTP and Bluetooth.

Device

A model of machine that can execute arbitrary programs, typically a mobile phone (cell phone).

Event

MoSync Events deliver notification of keypresses, stylus movements and the results of asynchronous operations like networking and Bluetooth scans.

Handle

An identifier to a resource (e.g. binary file) or object (e.g. a connection) managed by the runtime. There are different types of handles, not interchangable.

Panic

A notification sent when an unrecoverable error occurs in a MoSync runtime, library, or user application. See the Panics Reference Guide.

Pipe-tool

Pipe-tool is our powerful code transformation engine. It takes the output of the GCC compiler, links it with the MoSync libraries, and outputs binary code and/or Java source code depending on the target platforms and devices. Pipe-tool combines the functions of a resource compiler, linker, and code optimizer. It is configured through build configurations.

Placeholder

A resource handle that doesn't identify any resource. It is used in the creation of new resources. The concept of a "placeholder" is used in two contexts. The first is in resource files, to specify "markers" to identify ranges of resources. The second is to create handles for dynamically allocated data objects (using maCreatePlaceholder/maDestoryPlaceholder).

Platform

An operating system, or version thereof, that is used by one or more devices. Examples include J2ME, Symbian Series 60, Android, and Windows Mobile.

Resource

A piece of data managed by the runtime, for example an image, an audio file, or a binary data file. Each resource is identified by a handle. Resources are compiled with the rest of the program and loaded at startup. They can also be created and destroyed when the program is executing.

Runtime

Libraries or programs that execute MoSync programs on a given target device. They also provide a uniform interface to low-level system APIs, including graphics, audio, event handling and communications.  Platforms supported by MoSync have different runtimes.

Syscall

System Call - a function that is implemented by a MoSync runtime in code native to a platform.

MoSync SDK 3.3
Copyright © 2013 MoSync AB
www.mosync.com