I'm needing to work on a feature that needs about 3K of constant global
data, and needs to work on devices back to OS 2.0 1Meg devices. Further, I'd
like to build a .lib with this feature so that I can link it into other
programs.
The Palm OS Programmer's Companion has Table 6.1 on page 158. This table
indicates that my worst case situation is having 64K for the dynamic heap,
but it has to contain a bunch of stuff. If I understand this table
correctly, it shows that I have no more than 12K of memory for my globals
and allocations on that device. Thus, if I use static data to solve my
problem, I've burned 25% of my useable memory on that device. That doesn't
sound very appealing.
So, what are my alternatives?
1. Change my requirements. If I require an OS 3 device, I get up to 36K of
useable memory. 3K doesn't seem so bad in that case.
2. Store the data in a database, and require that the database be installed
with my app. I'd like to avoid this becaue I'm lazy and it introduces
additional problems: designing the data architecture, creating the database,
bundling it with the app, then getting data from it.
3. I've seen programs that are "huge" (256K) that contain entire electronic
books built into the .prc file. I assume that the data is being embedded in
the resources somehow. I haven't found any kb articles on using an app's
resource as a data repository. If this can be done, can you point me to
additional information?
Thanks in advance for any advice...
Jeff
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
