One way which I use is the following version 1 - check ftp file is version changed - propose download - let user update
version 2 - 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 mail ago... cheers Xavier > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] 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... > > Thanks, > JB > > _______________________________________________ > use-revolution mailing list > [email protected] > http://lists.runrev.com/mailman/listinfo/use-revolution > _______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
