If that is your only goal, store the images as a binary BLOB entry in a local SQLite database, then load them as you need them.
It's pretty simple to write the images to a binary string, and storing them in a DB is very easy. This also allows you to package all of you resources into a single file. - Tom On 17/05/2007, at 10:10 AM, Eric Richards wrote: >> >> >> One idea that I like is similar to the usage of the aforementioned >> PSD >> files. By which I mean you take a regular image file, then pack it >> into >> another file which also contains settings and whatever else you like. >> Then you could open that file with a different copy of the >> application >> and have your UI customizations, tool settings, and assorted >> whatnot all >> ready to go automagically. >> >> Aside from that, which is almost no work at all, I don't think I'd >> have >> the patience to build my own format for much of anything. =) >> >> >> > Another would if you make an app that uses images in some, say a game, > and you store the images externuly, if you use your own format you > could > prevent users from messing with them. That is, if its a format that > your > apps > could only understand. > > Yeah the whole time and energy thing come into play. > > _______________________________________________ > Unsubscribe or switch delivery mode: > <http://www.realsoftware.com/support/listmanager/> > > Search the archives: > <http://support.realsoftware.com/listarchives/lists.html> _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
