Time-Stamping Demo programs #2

[Richmond]

On 24/04/12 04:04, Kay C Lan wrote:
> On Mon, Apr 23, 2012 at 4:45 PM, Richmond<richmondmathewson at gmail.com>wrote:
>
>> Blast! I am trying to find a way so that I don't have a file "floating
>> about" on somebody's system that they can just flush away to
>> reset the 30 day limit on my DEMO.
>>
> I'm assuming then you must have some sort of licensing system for those who
> wish to go beyond the demo. How does this work? Surely your demo licensing
> system must be based aound it.
>
> I'm out of my depth here because I only develop for a very small circle of
> users (more like a dot really;-) so licensing isn't an issue, but I thought
> the whole concept of the Splash stack was to get around the limitation of a
> stack not being able to save to itself. Once you have a Splash-Working
> stack arrangement you can save your rego info in an encrypted sub-stack, as
> a customProp so it isn't available to prying eyes to throw away or amend.

They can, however, throw away the substack (because, as far as I can 
work out, it cannot
be a substack - so cannot be hidden inside a standalone's file structure 
- but a free-standing stack),
at which point a standalone would recreate the stack with an updated 
time-stamp.

> _______________________________________________
> 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