Re: App restart after update
On Jul 5, 2008, at 7:25 PM, Bill Vlahos wrote: I am using a splash screen but it don't actually start using this template stack. I touch it to get version info. OK. Whenever you touch a stack to get version info it will be loaded into memory. I tried deleting it as suggested and I also tried stop using it and neither seem to work. Stop using it won't do anything in regards to whether or not it is in memory but deleting a main stack will always remove it from memory. If you try to reference the stack using the full filename (i.e. trying to access version info) after you delete it, however, the stack will be loaded back into memory. Deleting a substack will just delete the substack but not to anything to the mainstack. The revert command seems to be for the main stack and I'm not sure how I would actually use it in this situation. If you update the stack file on disk that the main stack resides in, 'revert' will reload the mainstack (and substacks) from disk. I'm missing something. Let me know if this helps at all. Regards, -- Trevor DeVore Blue Mango Learning Systems www.bluemangolearning.com-www.screensteps.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: App restart after update
I am using a splash screen but it don't actually start using this template stack. I touch it to get version info. I tried deleting it as suggested and I also tried stop using it and neither seem to work. The revert command seems to be for the main stack and I'm not sure how I would actually use it in this situation. I'm missing something. Bill On Jun 17, 2008, at 9:56 PM, Trevor DeVore wrote: On Jun 18, 2008, at 12:44 AM, Bill Vlahos wrote: Most of the time I only update the stacks. What is the command to unload the stacks? After I unload the stacks how do I reinitialize the standalone stack? I'm assuming you used the splash stack technique and you don't have to update any stacks that were used to build the standalone. If the stacks are not stack files then this won't work. If they are then proceed. You can unload your application stacks using: delete stack NAME_OF_MAINSTACK This will remove the stack from memory. After removing the application stacks from memory just call whatever handler in the stack used to create the executable initializes and launches your application. Perhaps startup or preopenStack. That could should already take care of loading your application stacks into memory and launching the application. There is also the 'revert' command which will reload the stack from disk. I haven't used this technique myself though. -- Trevor DeVore Blue Mango Learning Systems ScreenSteps: http://www.screensteps.com Developer Resources: http://revolution.bluemangolearning.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: App restart after update
Trevor DeVore wrote: On Jun 18, 2008, at 12:44 AM, Bill Vlahos wrote: Most of the time I only update the stacks. What is the command to unload the stacks? After I unload the stacks how do I reinitialize the standalone stack? There is also the 'revert' command which will reload the stack from disk. I haven't used this technique myself though. I use "revert" frequently, it works great. You don't have to call any handlers or initiate any messages; it works just as though the stack were opening for the first time. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: App restart after update
On Jun 18, 2008, at 12:44 AM, Bill Vlahos wrote: Most of the time I only update the stacks. What is the command to unload the stacks? After I unload the stacks how do I reinitialize the standalone stack? I'm assuming you used the splash stack technique and you don't have to update any stacks that were used to build the standalone. If the stacks are not stack files then this won't work. If they are then proceed. You can unload your application stacks using: delete stack NAME_OF_MAINSTACK This will remove the stack from memory. After removing the application stacks from memory just call whatever handler in the stack used to create the executable initializes and launches your application. Perhaps startup or preopenStack. That could should already take care of loading your application stacks into memory and launching the application. There is also the 'revert' command which will reload the stack from disk. I haven't used this technique myself though. -- Trevor DeVore Blue Mango Learning Systems ScreenSteps: http://www.screensteps.com Developer Resources: http://revolution.bluemangolearning.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: App restart after update
Richard,
Interesting idea. Thanks.
Bill Vlahos
On Jun 17, 2008, at 5:59 PM, Richard Gaskin wrote:
Bill Vlahos wrote:
> Quitting the application after the download is easy but how do I
> have the computer automatically relaunch it?
>
> I would need this for Macintosh and Windows and Linux.
Uninstallers face a similar issue, since they need to delete an app
but of course an app can't delete itself.
Their approach may work for your circumstance as well:
An uninstaller commonly copies itself to the local temp directory
and then launches that copy to do the deed.
With Rev 2.9 you can now get the temp folder on all three platforms
with:
get specialFolderPath("temporary")
Temp directories are automatically cleared out by the system
periodically (often on restart), so while it does mean another copy
of an app somewhere it's not one that will live for long after it's
needed.
--
Richard Gaskin
Managing Editor, revJournal
___
Rev tips, tutorials and more: http://www.revJournal.com
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
Re: App restart after update
Trevor, Most of the time I only update the stacks. What is the command to unload the stacks? After I unload the stacks how do I reinitialize the standalone stack? Bill Vlahos On Jun 17, 2008, at 5:37 PM, Trevor DeVore wrote: On Jun 17, 2008, at 1:49 AM, Bill Vlahos wrote: My application can update itself by downloading and placing the new version in the appropriate spot. To utilize the new version the user has to quit the old version and relaunch it which brings up the new version. An example of this is Firefox which downloads the new file, expands it, quits the running application, and then relaunches the new one (and I presume deletes the old version). Quitting the application after the download is easy but how do I have the computer automatically relaunch it? I would need this for Macintosh and Windows and Linux. Hey Bill, Are you replacing the executable when you install the new version or just the stacks? I ask because if you are just replacing stacks then you just need to unload all stacks from memory and reinitialize everything. If you do need to quit the application and relaunch a new executable then email me off-list and I can send you the relevant parts of the GLX Application Framework that relaunch an executable on Mac and Windows. I just finished up some updates to this area of the code. I don't have anything for Linux but the Sparkle framework (OS X only) uses a script for relaunching that may be portable to Linux. I've wanted to switch to a script on OS X (I use a small launcher app I made in XCode for relaunching right now) so it would be interesting to take a look at it again. Regards, -- Trevor DeVore Blue Mango Learning Systems ScreenSteps: http://www.screensteps.com Developer Resources: http://revolution.bluemangolearning.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: App restart after update
Bill Vlahos wrote:
> Quitting the application after the download is easy but how do I
> have the computer automatically relaunch it?
>
> I would need this for Macintosh and Windows and Linux.
Uninstallers face a similar issue, since they need to delete an app but
of course an app can't delete itself.
Their approach may work for your circumstance as well:
An uninstaller commonly copies itself to the local temp directory and
then launches that copy to do the deed.
With Rev 2.9 you can now get the temp folder on all three platforms with:
get specialFolderPath("temporary")
Temp directories are automatically cleared out by the system
periodically (often on restart), so while it does mean another copy of
an app somewhere it's not one that will live for long after it's needed.
--
Richard Gaskin
Managing Editor, revJournal
___
Rev tips, tutorials and more: http://www.revJournal.com
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
Re: App restart after update
On Jun 17, 2008, at 1:49 AM, Bill Vlahos wrote: My application can update itself by downloading and placing the new version in the appropriate spot. To utilize the new version the user has to quit the old version and relaunch it which brings up the new version. An example of this is Firefox which downloads the new file, expands it, quits the running application, and then relaunches the new one (and I presume deletes the old version). Quitting the application after the download is easy but how do I have the computer automatically relaunch it? I would need this for Macintosh and Windows and Linux. Hey Bill, Are you replacing the executable when you install the new version or just the stacks? I ask because if you are just replacing stacks then you just need to unload all stacks from memory and reinitialize everything. If you do need to quit the application and relaunch a new executable then email me off-list and I can send you the relevant parts of the GLX Application Framework that relaunch an executable on Mac and Windows. I just finished up some updates to this area of the code. I don't have anything for Linux but the Sparkle framework (OS X only) uses a script for relaunching that may be portable to Linux. I've wanted to switch to a script on OS X (I use a small launcher app I made in XCode for relaunching right now) so it would be interesting to take a look at it again. Regards, -- Trevor DeVore Blue Mango Learning Systems ScreenSteps: http://www.screensteps.com Developer Resources: http://revolution.bluemangolearning.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: App restart after update
Le 17 juin 08 à 22:21, Chipp Walters a écrit : Bill, Typically re-launching is done with a helper app, which is sort of a Catch-22 issue with Rev-- because if you downloaded a new engine for your app, who's to say the helper app's engine isn't going to have a problem launching as well. Of course, you could also get tricky and try and create batch scripts to launch your new apps, but there's a lot of issues with it as well-- especially Virus checkers who don't approve of such. I've found the best way around this is to create a splash-screen app which is only the engine and load the app from stacks, which are easily updated and downloaded w/out issue. When the splash-screen app launches, it can also look for a new version of itself as well, and point users to a webpage to download the new splash-screen app. I prefer downloading/installing from a web page as then there are ZERO issues with proxy servers or any buggy transport code which might be in the splash-screen app. I've had thousands of downloads of various products we sell using this technique and very few issues. best of luck, Chipp ___ another advantage of this technique is that you can keep a record of your udpates. Handy if the new version is buggy! cheers, François ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: App restart after update
Bill, Typically re-launching is done with a helper app, which is sort of a Catch-22 issue with Rev-- because if you downloaded a new engine for your app, who's to say the helper app's engine isn't going to have a problem launching as well. Of course, you could also get tricky and try and create batch scripts to launch your new apps, but there's a lot of issues with it as well-- especially Virus checkers who don't approve of such. I've found the best way around this is to create a splash-screen app which is only the engine and load the app from stacks, which are easily updated and downloaded w/out issue. When the splash-screen app launches, it can also look for a new version of itself as well, and point users to a webpage to download the new splash-screen app. I prefer downloading/installing from a web page as then there are ZERO issues with proxy servers or any buggy transport code which might be in the splash-screen app. I've had thousands of downloads of various products we sell using this technique and very few issues. best of luck, Chipp ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
