As I said I away but if you are in hurry you can see the code here https://github.com/kilon/ChronosManager/blob/master/ChronosManager.package/ChronosManager.class/class/updateToLatestVersion.st
The idea is that the class carries the current release of the project that is installed while the latest release is read online from inside a release file which is a simple text file with release information written in human readable format. Regex is used to detect a v0.1 pattern and top most find is used for fetching the number of latest release. Autoupdate also checks internet connection with github so the user never see an error in case of failure to connect instead it just does not update. Next step will be to clean up and delete any previously downloaded files via autoupdate. This way image folder won't grow in size in each autoupdate. UIManager can be used to alert the user for a new update and ask for permission to download it. There is no reason for git to be installed for autoupdate to work , only thing needed is a normal Pharo image. When I return to Athens I will improve it further and document it. On Fri, 25 Dec 2015 at 17:05, Hernán Morales Durand < hernan.mora...@gmail.com> wrote: > Hi Dimitris, > > 2015-12-25 13:01 GMT-03:00 Dimitris Chloupis <kilon.al...@gmail.com>: > >> I am on holidays to at London for Christmas with no direct access to my >> machine. >> >> But you can get a very good idea how to do what you want by taking a look >> at standalone Pharo apps like Phratch and Dr Geo . The good news is that is >> both very easy and extremely flexible. You can also change the icon of the >> app and and the name of the Pharo executable to make the user completely >> unaware officials Pharo existence. You can also add squeak to your google >> searches because they have been several posts about this in the squeak >> mailing list . Pharo is incompatible with squeak but it's still a fork of >> squeak so there is a lot of common ground. >> >> After that you can start removing packages you don't need, Pharo is in >> the process of of being modularlized so that is easy to start with a >> skeleton image. If you are in need of a specific Pharo library choosing >> Cuis which is also a squeak fork is simple and much lighter than Pharo >> image. Squeak , Pharo and Cuis share the same VMs. >> >> Las but not least if you are on Windows there has been a thread on our >> list on how to make window installers for Pharo apps the easy way. You may >> want to google that too, I think Damien made a guide about it . >> >> We can go on and on and on how much Pharo can be customized. I even >> recently made an auto update functionality for me Pharo project >> ChronosManager which detects if the github repository has a new release >> available and downloads it so that the user use always the latest stable >> release without a need to worry about it or do anything about it ;) >> > > If you don't mind to share, I could try to integrate it in > ApplicationUpdater > > http://smalltalkhub.com/#!/~hernan/ApplicationUpdater > > Cheers, > > Hernán > > >> >> On Fri, 25 Dec 2015 at 13:42, Saša Janiška <g...@atmarama.com> wrote: >> >>> On Pet, 2015-12-25 at 11:48 +0100, Cyril Ferlicot wrote: >>> >>> >>> > First, be careful with Pharo 5 because this is an alpha. There is high >>> > chance that some things breake. If you find some bug you can report it >>> > on pharo's fogbugz (the link is on Pharo website). >>> >>> OK. No problem. >>> >>> > For the deployment you have a different virtual machine for >>> > OSX/Linux/windows. >>> >>> That's clear. :-) >>> >>> > For now the VM is only 32b, this can create some trouble for Linux >>> > users but the 64b VM should come soon! :) maybe for Pharo 6? >>> >>> Pharo-5 is scheduled for the 1Q/2016? >>> >>> > For now there is not a lot of classic application. I think you can >>> > take a look at Dr Geo. >>> >>> That one looks interesting. Thank you for that. >>> >>> > If you want to do open source you can use the same method that >>> > PharoLauncher that open a window in full screen and let a setting for >>> > developers to be able to get a classic Pharo environment. But the user >>> > might have acess to the code through GTSpotter or Morph's halos. >>> >>> I plan to do open-source, but would like to hide code and other dev >>> tools in order not to confus end-users. >>> >>> > If you don't want the user to get an acess to the code by any mean you >>> > have to cut everything by hand for now. (Disable spotter, disable >>> > halo, disable world menu, disable the debugger...). >>> >>> OK, it means it's possible...Will explore and/or ask. ;) >>> >>> >>> > I would like to have a way to lock an image directly from Pharo >>> >>> +1 >>> >>> >>> > Welcome to Pharo and merry Christmas! >>> >>> Thank you! >>> >>> >>> Sincerely, >>> Gour >>> >>> -- >>> Perform your prescribed duty, for doing so is better than not >>> working. One cannot even maintain one's physical body without work. >>> >>> >>> >>> >>> >>>
