MikeKerner at roadrunner.com
Wed Dec 7 16:40:38 CET 2016
I put everything in a db, and I have default settings coded into the app to
populate the db. You don't need Andre's library to use DB's with LC (and I
do not). db access in LC is very easy (but that is not to say that his
library won't make it easier). In fact, db access in LC is so easy that I
don't use files or extra stacks for anything. The only time I do use
read/write files is when I am sending them to the cloud or retrieving them
from the cloud. This is a very effective way to do data transport to and
On Wed, Dec 7, 2016 at 10:14 AM, pink <nabble at mad.pink> wrote:
> I'm interested in learning how people save data and settings for
> applications, especially on mobile devices.
> The method I have been using is to create an invisible data stack and save
> the data as custom properties. I like this the most because I tend to put
> most of my data and settings into arrays, and this requires the least
> of steps and no encoding to read and write.
> Reading and writing to a text file also works, but does require some sort
> encoding and decoding to save arrays.
> I've experimented a little bit with local database files. In particular
> tried Andre Garzia's database library, and Livecloud's local database, both
> of which are pretty nice.
> I'm curious what everyone else uses, and what do you think are the pros and
> cons of different methods?
> View this message in context: http://runtime-revolution.
> Sent from the Revolution - User mailing list archive at Nabble.com.
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
and did a little diving.
And God said, "This is good."
More information about the use-livecode