Hi,��

@Stef: Previewing an scenario like yours, where not always you want to install my experimental tool, my script [1] displays a button morph for 3 seconds which the user can press to cancel the installation. Not that fancy as a manager tool, but I think it works.

But I recognize it can be annoying to force users to use external tools to setup scripts in the preferences directory...

[1]: http://ws.stfx.eu/LQ3FQ0MIOH4O

Mart��n

On Tue, Nov 4, 2014 at 10:58 AM, stepharo <stepharo@free.fr> wrote:
Yes

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 areused to ���customize��� your image.

Yes but there are implicit. There are there but we do not see them and manipulate them if you see what I mean.
And there are static.
What I want to say also is that this is not the spying framework but the projects people work on.

Uko

[1]: https://github.com/RobertoMinelli/DFlow/blob/master/installDFlow.st
[2]: http://smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter <http://smalltalkhub.com/#%21/%7Edalsat/ShoreLine-Reporter>