by Scott » Thu Apr 13, 2017 2:56 pm
There are a number of ways to do this. SaM, for instance, uses satellite projects for the settings that are copied from the app to a temp directory, but the saved make files are stored in simple text files that store the settings, afterwhich the temp projects are discarded. Opening a make file copies a new temp project that loads the make file's settings.
For more data-centric duties, SQLite is another way of storing and recalling data. Our in house databases use a cantModified project with a single card that contains fields that are essentially placeholders for data that is searched/recalled based on typical SQL arguments, with changes being written out to that SQLite file.
For more graphic/multimedia needs, a satellite project that can create/store/modify graphics and other media is stored in the app's package, and copied to user's drive (as a document or Application Support file) that can then be referenced and acted upon each time the app is opened.
As to what method is best really depends on what data is to be manipulated, and how it needs to be recalled. For instance, graphics' picturedata can be stored in SQLite as binary data, but if it doesn't need to be cataloged and recalled by searchable metadata, a sat project would be a simpler method.