Android: custom prop vs. .txt?

Ralph DiMola rdimola at evergreeninfo.net
Fri Jun 1 11:58:04 CDT 2012


On Android the stack is in the engine folder that is read-only. It resides
in the apk(a zip formatted file). The engine folder is virtual and read
only. If you want to modify a stack it needs to be a separate stack that you
move to the documents folder. Any file that you want read/write must be
moved from the assets folder to the documents folder(or SD card). I use an
SQLite database in the documents folder for user data but a text file would
work also.

Ralph DiMola
IT Director
Evergreen Information Services
rdimola at evergreeninfo.net

-----Original Message-----
From: use-livecode-bounces at lists.runrev.com
[mailto:use-livecode-bounces at lists.runrev.com] On Behalf Of
ambassador at fourthworld.com
Sent: Friday, June 01, 2012 12:21 PM
To: use-livecode at lists.runrev.com
Subject: Re: Android: custom prop vs. .txt?

Nicolas Cueto wrote:

> I have an Android app that uses a small amount of data (under 10Kb). 
> The data gets updated regularly. Haven't decided when.
> Perhaps every half-second, or perhaps when the user hits the hardware 
> home-button.
>
> Right now, the data is stored both as a custom prop of the card and as 
> a .txt file. Maybe, though, I can just rely on .txt? Or would the 
> Android device and/or OS for some reason prefer I use "write to txt" 
> as little as possible? Perhaps to save energy?
> Perhaps because it's slower than saving to a custom prop?

"Saving"?

Issuing a save command to the stack with the props should take slightly
longer than writing the data to a file, but with only 10k the difference
will be negligible.

If you don't need to save often then using custom props will provide good
efficiency and simple, robust behavior.

- rg/4w

_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode




More information about the use-livecode mailing list