pdbs changes can easily be backed up to the desktop or sunc with a conduit. Changing prcs would be akin to a self modifying program - lots of fun, but generally a bad idea.
For purely constant data (big piles of read only data that your program uses) you might chose prcs or pdbs. Again, it probably comes down to how you want to access it. If the type/id thing works, a prc might be easier. In general the simple index model of a pdb, commonly combined with an overlayed application specific index, will be best. That is, unless you have a good reson not to, use a pdb.
For code, bitmaps, or any other widget that will ends up being directly passed to a PalmOS routine, a prc is the obvious choice.
hope that helps,
djw
On Sun, 16 May 2004 19:00, Eric Allen wrote:
Is there some whitepaper or article out there detailing the respective advantages and disadvantages of prc and pdb formats? I'm trying to decided which format I want to use for my application and the best documentation I can find is at http://www.palmsource.com/developers/newsletter/20030818.html#dev_insights. Is there a better comparison out there?
--
For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
