Trial software and registering
drothe at optusnet.com.au
Wed Mar 16 16:59:00 CST 2005
I agree with Malte, having a function limited app for demo purposes and an
ID KEY system for the full app
seems to be the best answer for me. My full app is the standalone.exe and I
also use an idkey.rev stack for
verifying username against the encrypted key.
On startup the main stack(app) is hidden while the idkey.rev is run to do
hide this stack
When the app is first installed it places a carefully named
cipherfile(file1) into the system folder.
For the first run the enter registration form(idkey.rev) is displayed where
the user types his/her details into, it is checked against the cipherfile,
if all matches ok another carefully named file(file2) containing the
username & idkey is written to the system folder.
Every time the app is started it(silently) checks for (file2) & decodes the
username against the idkey, if the key is incorrect or absent it displays
the Enter Registration form. If all matches ok it shows the main stack(app),
which also displays a
"Registerd to: Users Name" field at the about screen or somewhere within the
main stack, this way if someone somehow copies the idkey they will have
software registered to another person which they will be reminded of each
time they use it!
If you try to run the app with idkey.rev absent the stack remains hidden!
I have a stack from which I generate the users idkey using their name.
This is emailed to them once payment is received!
I created the idkey gen stack using the principles from the "Sons of
Thunder" website ,
volution/revolution.htm find section Deployment - (Nearly) Unbreakable
Hope this helps.......Dwayne Rothe
> Hi Karen,
> You could get the date when your app is started the first time, write
> it to a file and display a registering dialogue 30 days later.
> Personally I prefer a "crippleware" scheme (disable certain
> functionality like save) over a time based registration scheme but
> that´s a matter of personal preference I think. ;-)
> Concerning a password generator you might want to take a look at this
> stack. There are many other ways to do it, but the stack should help
> getting you started.
> Scripts are commented.
> When it comes to building your app make sure you password protect the
> stack (otherwise people can read through the code if the stack is
> opened in a text editor)
> If you have any questions feel free to ask. :-)
More information about the use-livecode