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 ?
You can overwrite the stack files on disk. If you need to do the swap in vitro, you can even delete the memory copy and re-open from disk after saving the new one. That's how devolution handles its live updates -- the code for devolution setup is wide open, borrow what you need (a kind mention in credits is always appreciated <g>).
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...
Could be, but if you make a summary of available versions it's a small transaction. Or you could have it be a manual process, perhaps driven by the user selecting "Check for Updates..." form a Help menu.
-- Richard Gaskin Fourth World Media Corporation __________________________________________________ Rev tools and more: http://www.fourthworld.com/rev _______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
