why tell a person who's writing the app how to write it? if that is what he
wants/needs to do then i'm sure he/anyone would appriciate answers and not
lectures (unless it is a better or alternative method in accomplishing what
he wants to do).
a good example for this is when i wanted to (and figured out how to) prevent
a user from accessing anything outside of my app or exiting my app. certain
access levels and exit / end buttons are used for a specific purpose, but i
still got a few stray replies talking about the "way" palm apps should go,..
ie, no exit buttons, just relaunch another.
-----Original Message-----
From: Brian Mathis <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Monday, December 20, 1999 3:25 PM
Subject: Re: Persistant data storage for registration purposes?
>On Mon, 20 Dec 1999, Rubin, Dan wrote:
>> Hi All,
>>
>> What is the best way to store persistant data in a way that it does not
get
>> removed if the application that creates/uses the data is removed and
>> re-installed. I would like to store something like an integer etc...
that
>> would be used for registration purposes (to keep track of how many times
the
>> app is started etc...)
>>
>> Thanks for any tips...
>> - Dan
>
>This has been hashed out before, but basically, here's my feeling. Your
>app isn't important enough to me to let you store stuff that I can't
>remove from my device. I don't care if it's the coolest, newest, most
>amazing thing in the world. The people who are going to pay will pay, and
>those who don't want to, won't. The minescule amount of $$ you might not
>receive is not worth polluting the entire world's devices.
>
>--
>Brian Mathis
>Direct Edge
>http://www.directedge.com
>
>
