"rather not have apps... from a web page"
b.xavier at internet.lu
Sun Mar 27 04:38:29 CST 2005
One way which I use is the following
- check ftp file is version changed
- propose download - let user update
- check ftp file for update
- check user/version allowed or back to version 1
- get update list
- download, update scripts/media that need it
- and or run update script.
Requirement: ftp server and connection to it.
Remember to keep it simple... Version 2 also requires more checks. IOWs, not
worth shareware or freeware prices/efforts IMOHO. It's the best way to
reduce problems and bugs.
You can see how version 1 works in the latest HotKeyN2O which I mentioned a
> -----Original Message-----
> From: use-revolution-bounces at lists.runrev.com
> [mailto:use-revolution-bounces at lists.runrev.com] On Behalf Of jbv
> Sent: Sunday, March 27, 2005 11:31
> To: How to use Revolution
> Subject: Re: "rather not have apps... from a web page"
> > Just make your app a single-window executable which periodically
> > checks your server for updates and downloads them. You can
> do it all
> > from within your app, so the admin doesn't have to do
> another install
> > everytime you update and you save your users the step of going to
> > another program (the browser) to get updated.
> Just curious : how do you manage upgrades of a standalone, if
> not by downloading new versions of sub-stacks that will be
> downloaded and saved on the HD, and thus ending with more
> than 1 file on the user's HD ?
> Of course, there's also the possibility to open a distant
> stack from the standalone, but that means client - server
> communication everytime the executable is used...
> Unless I'm missing something...
> use-revolution mailing list
> use-revolution at lists.runrev.com
More information about the use-livecode