> Are there any things that a replacement launcher app has to do that may not > be obvious?
These may be obvious, but I'll let you decide... Register for and handle incoming beamed databases. You'll need to register for extensions prc, pdb, pqa, and oprc, as well as MIME types application/x-pilot and application/vnd.palm. Or you can let the built-in launcher handle these. If you decide to take over this responsibility, you should set your launcher as the default for all these extensions and MIME types. (This is only possible on Palm OS 4.0 and later.) If a database already exists with the same name, ask the user if it's okay to delete it. Ideally, avoid losing the original if the user cancels an overwrite. Expect to receive multiple databases in a single session on Palm OS 4.0 and later. The first will be the app; the rest will be the overlay and bundled databases. Don't ask the user if they want to accept each of these individually. Handle the subsequent goto launch, switching categories and scrolling if necessary to make the received app's icon visible. Support beaming apps. Beam overlays and bundled databases in the same session on Palm OS 4.0 and later. Don't beam copy-protected databases (apps, overlays, or bundled databases). Support beaming apps directly from a card. If the user's preference for the Ronamatic stroke is beaming, this stroke should bring up the Beam dialog in your launcher. Support Send, as well as Beam, on Palm OS 4.0 and later. On a Palm VII, handle the "antenna raised" launch command and switch to the wireless category. Register for and handle "card inserted" and "card removed" events. Support launching "from a card". Delete the app from main memory when it quits, but keep its databases and preferences around in case the user runs it again. Rotate through the categories when the silk-screen Home button is tapped repeatedly. -- Danny @ PalmSource -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
