On 01 Nov 2014, at 22:15, stepharo <stepharo@free.fr> wrote:
On 27/10/14 13:44, Yuriy Tymchuk wrote:
To summarise Iâd like to propose adding startup scripts manager to pharo luncher. I'm not sure that there are startup scripts. But yes you got what I meant. a super simple way to load a bunch of projects in another image based on the current one.
The projects that I know are using startup actions [1][2]. These are files that go into ~/Library/Preferences/pharo/ and define what has to be run on image startup. They are used to âcustomizeâ your image. Uko [1]: https://github.com/RobertoMinelli/DFlow/blob/master/installDFlow.st <https://github.com/RobertoMinelli/DFlow/blob/master/installDFlow.st> [2]: http://smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter <http://smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter>
Whatâs more, usually we are working on our one âprojectâ. And as itâs a good practice to start from a fresh image, we either have to load a configuration of it into fresh images or download pre-built image from CI. And we are too bound to CI because of image building. What I see as next step in the development workflow, is to say to the launcher: I want this Project is this Image (3.0, 4.0) with this prefs (experiences). The launcher builds the thing and you can work with it.
In general I like your idea a lot, but letâs have a little discussion to hear what the others have to say.
:)
and I would like a button that say: snapshot this image as my project :) (the system should have a way to know the system package versus others. it should be possible with some metadata :)
I know that I'm lazy (and bored to redo all the time the same thing :))
Uko
On 27 Oct 2014, at 13:13, stepharo <stepharo@free.fr> wrote:
Dear experience makers (Martin, yuriy, tommaso, roberto and others,)
you would like to have many people doing your experience.... I know you would love that. Here is my suggestion: ease the use of new images. Each time I want to load the projects I'm hacking and I do not have a jenkins for it, it is painful (setting up the repos.... loading....). So I do not change often images and I'm reluctant to load new stuff (like your experiments)
- build a simple little tool that could be integrated in pharo and would do the following: - let the user (un)/select some packages or configurations - generate a script to reload these configurations really easily
This way I can load my project and then you provide a script for your experience. and after I can reload my project with your material for experience in my new image. Right now I do not like to hack the preference file because I have images where I do not want any interference
So is my proposal clear?
Stef