Here is what I use all of the time. The concept is much simpler that
what you were proposing.
There is a single app, which is the engine and all of the livecode
libraries linked to it. This is deployed once, unless there is a new
engine with features you want to use. ie livecode 6.0 to 7.0
The app fetches an index file, that contain all of the links to the
other available stacks. I have it set up such that each is a separate
application from the users perspective.
The user doubleclicks on the app/stack and it gets loaded. I have
thought about saving the stacks locally for when the user was not
connected to the internet, but none of my users have asked for that
capability. That would not be hard to add.
Security wise, just set the password on the stack. You can certainly
add on your own encryption if you want.
Here is the code to the WHOLE app!
on opencard
set itemdel to tab
put url "https://dl.dropbox.com/s/~~~~/Index.txt"; into AppList
set the dgText of grp "AppPicker" to Applist
-- 2 items per line, the url to the stack and the text that the user sees
end opencard
on mousedoubleup
set the itemdel to tab
put the dgHilitedLines of grp "AppPicker" into tLine
put the dgDataOfLine[tLine] of grp "AppPicker" into tData
put tData["theLink"] into tURL
go to URL tURL
end mousedoubleup
on CloseStackRequest
answer "Are you sure you want to quit?" with "No way" or "OK"
if it = "OK" then
## close stack:
quit
end if
## no other action neccessary
end CloseStackRequest
On 11/7/14 3:33 PM, j...@souslelogo.com wrote:
Hi list
Here's something I've had in mind for quite some time.
Let's say you have an app built with LC that you send to
various users as standalones with regular updates.
What if all the most important functions of that app were
gathered as handlers in the main stack script for instance, and
at every startup, a script would check with a remote server
for a possible update of that script, and dowload the new
version (if any) to replace the old one with a simple
"set script of this stack to myVar" ?
The standalone could be a simple front end with all the
most important objects, and therefore would weight slightly
less than the complete app, and above all would need to
be downloaded only once by end users who would not have
to worry about versions and updates.
At first glance this looks like a convenient way to update
existing functions, add new ones, manage different settings
among users, etc.
But what about safety ? Is there a way to encrypt the main
script while it is downloaded at startup so that it can't be
caught by some sniffer ? And is there any other crucial
security issue that didn't cross my mind ?
Thanks
jbv
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
