Are there any gotchas to using custom application database and resource types? I mean, aside from the obvious thing as far as making them unique (which is difficult, considering there's no real list of them all out there... or is there?).
What I'm doing is designing a plug-in system for CacheMate, my geocaching database, where it will call plugins as applications, passing parameters through the SysUIAppSwitch or SysAppLaunch calls. There are some that will be able to run on their own as applications, and in that case I'll be using the standard 'appl' database type. There are others, though, that won't be able to run independently. For those, I'm thinking about a 'CMEX' database type, but with the resources of a normal application (well, except for space-hogging things like icons). In both cases, there will be a resource (type probably 'CMEX' as well) that will mark it as a CacheMate plugin and contain information for what it needs and what "roles" it can perform as a plugin. My main concern at this point is how safe is it to assume that use of that type will be alright, and not confused with something else. I was thinking about adding a tag inside the marker resource to further confirm that it's a plugin, but I'm wondering if I really need to or not. Thanks in advance. -- ----------------------------------------------------------------------- Brian Smith // avalon73 at arthurian dot nu // http://www.arthurian.nu/ Software Developer // Gamer // Webmaster // System Administrator Frisbeetarianism, n.: The belief that when you die, your soul goes up the on roof and gets stuck. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
