Comet Mobile Usage
From CometWiki
(→Programming the App) |
(→Mobile Programs) |
||
| Line 38: | Line 38: | ||
== Mobile Programming Concepts == | == Mobile Programming Concepts == | ||
| + | |||
| + | === View Types === | ||
=== Sub Programs (Enter/Exit) === | === Sub Programs (Enter/Exit) === | ||
Revision as of 23:33, 7 January 2013
Contents |
Welcome
Here we will discuss how to use and program for the Comet Mobile app.
Using the App
In order to use Comet Mobile, you will need to be able to connect (via wireless or cellular network) to a Comet Anywhere Host. The host must be running Comet 32 with the latest version of the REL folder (or at least the MMONITOR program). This program is the interface between your mobile device and the Comet system. In the same fashion as QMONITOR, MMONITOR determines your security access, DAB access, as well as provides a method for you to run your mobile programs.
Connecting
Once you launch the app, the first screen to appear should be the connection screen. Here you can enter a server ip address (or host name), then press the connect button. The app will then connect you to your Comet Anywhere Host and run the MMONITOR program.
Running a Program
Once connected, you will be presented with the MMONITOR run screen. Here you can enter the name of a mobile program you have compiled and loaded onto the host system. These programs must have been compiled for mobile use, using the mobile procs.
Disconnecting
Hit the "Disconnect" button at any time to disconnect your Comet session and return to the connect screen.
Mobile Programs
Comet Mobile programs must be designed, programmed, and compiled using the Comet Mobile library (mobile.inc). You cannot run your normal Comet Anywhere programs through the Comet Mobile system.
First, we will discuss the basic Comet Mobile program structure you should use, then follow up with some programming concepts that can be used to make mobile programs.
Program Structure
Event Handling
Comet Mobile relies heavily upon the event handling structure built into Comet 32 - in fact, most of the program logic you write will be inside the event handler. In general, you should preload and present all views and controls at the start of the program. Then once loaded, let the event handler intercept user actions and show/hide/edit your views and controls in response to user input.
You can think of your program as a controller that moderates interactions between the user and your data.
