Your response sheds a little more light on your question: > the concepts of movable vs fixed chunks on the heap and a strange data > store force me to rethink the way I do things.
What environment might you be coming from that has not introduced fixed vs moveable chunks? I'll give you the 'strange data store'. Palm databases seem primitive and specific. As a matter of fact, they are minimal and very specific to the early needs of the Palm PIM applications. Over the years, they've been bandaided, but poorly adapted to anything that even remotely resembles earth-based storage concepts. However wierd, they're not that hard to use, and most intents and purposes, classical data handling procedures still apply. On 2/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I'm going to assume your sarcasm was intended as good-natured fun-poking > without malice, though that was not how it read to me. I'm well aware of > the changes in memory vs. persistent store that have occurred since I got my > first computer in 1984 with 16k RAM and a tape drive. > > With that said, I don't think my question was unreasonable. The Palm OS > is new to me, and the concepts of movable vs fixed chunks on the heap and a > strange data store force me to rethink the way I do things. Is it not ok to > ask of those who have walked before me what they've learned along the way? > > > > On Feb 5, 2007, at 4:58 PM, Pinus Alba wrote: > > Hi dmw, > > Are you serious? > > Twenty years ago 32K of RAM was more than enough. Palm's have much more > than that. > > If you have problems with persistent memory sizes vis a vis RAM size you > must have had the same problem on a desktop PC 5 years ago. > > Regards, > > On 06/02/07, dmw <[EMAIL PROTECTED]> wrote: > > > > I'm new to Palm OS development, and I'm trying to get a handle on how to > > manage program data. In the scenario of a simplistic desktop application, > > one would store persistent data in a file, load that data in when the > > program starts, work with the data in memory, and save it periodically and > > at application shut-down. > > > > Since the Palm is a memory limited device, do you palm developers always > > keep your persistent data in the database, without ever working with copies > > of said data on the heap? Seems it would be difficult to manage, with every > > operation being an opportunity for database corruption. What are the best > > practices here? > > -- > > For information on using the PalmSource Developer Forums, or to > > unsubscribe, please see http://www.palmos.com/dev/support/forums/ > > > > -- For information on using the PalmSource Developer Forums, or to > unsubscribe, please see http://www.palmos.com/dev/support/forums/ > > > > > -- > For information on using the PalmSource Developer Forums, or to > unsubscribe, please see http://www.palmos.com/dev/support/forums/ > -- yisdersomenimororsisasisdenderisorsis? Jeff Loucks -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
