Things like this are what databases on the Palm are for in its use. Remember
"It's all in RAM!" both your code and "storage". The reference lag isn't as bad
as accessing a disk drive. Plus there are plenty of database calls for sorting,
inserting, expanding, searching and making julian fries. :) I try to make it a
rule of thumb to keep any "big stuff" in databases and bring it up in
application code space when needed.
To present the data, just access the records of the database where it can be
displayed in the application and do database calls as the UI demands. To me,
this is part of breaking away from "desktop mindset" that a lot of us are
comming from to write on this platform. Also, having this in a database makes
it accessable to other apps and a conduit!
Steve Sabram
"Fawcett, Mitch" wrote:
> I have an application where I am doing a lot of manipulation of a list
> resource. The items in the list are character strings that are 20
> characters long. Right now I'm storing the strings in an array and using
> the array to populate the list. My test program has about 25 items but I'm
> thinking now it could eventually have up to 500 items. Is using a list the
> wrong approach in this situation? I like the look of a list, but I'll use a
> table if I have to. The list is alphabetized and I have zoom keys to find
> items quickly even though the list might be long.
