"John Marshall" <[EMAIL PROTECTED]> wrote in message
news:44941@palm-dev-forum...
> Did I cover the bases, Danny?
Indeed! The only thing that I would add is to mention the convention of
appending the creator ID on the end of the database name to ensure
uniqueness. For example, Memo Pad's database would be called "MemoDB-memo"
(except we don't have to follow our own rules because we live in a separate
lowercase space). If you're going to use a single creator ID and vary the
type instead, you'll probably want to append both the type and creator:
"MyPlugin-Type-Crid".
Alexandre Duret-Lutz asked a similar question on this forum about a week
ago. We discussed it offline and came to similar conclusions. If you use a
fixed creator ID, then you have to deal with registering types via your own
type registry scheme, similar to Palm's creator ID registry. Your app has to
deal with deleting, and possibly beaming, plugins. The plugins won't clutter
the Launcher. Deleting the app will automatically delete all the plugins.
If, on the other hand, you use a fixed type, then you can rely on Palm's
creator ID registry to ensure uniqueness, and you can rely on Launcher to
manage the plugins. But deleting the app won't delete the plugins. That's as
far as we got. You came up with an interesting third alternative: fixing
both type and creator ID and avoiding SysLibLoad. Then there's always the
fourth alternative: not using shared libraries. You can always roll your own
mechanism - just be sure to document the process for building plugins using
both CW and GCC.
--
Danny Epstein
OS Engineer, Palm Inc.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
