Cyril what would be good is to share what you are disabling and to tunr
such points into points that can be turned
but inside Pharo like that you push the logic to the system.
Now this is important to see that if people for which the value is high
do not work on something
why others would do it.
YES!!!
Do you know how Settings works?
We can adapt it this way.
When I improved the deployment of Synectique Tools I asked to get a
simple way to disable Spotter via a setting but I got as answer "No
because you can do it by removing a global shortcut so it is not needed.".
I do not know how to do it either. So we should document that.
People in companies don't have the time to learn how shortcuts work and
how to remove one without impacting something else. And they don't have
the time to check Spotter code to know how it is call.
If the image is able to have a deployment mode then I don't care how
Spotter is disabled (setting or removing a shortcut). But for now we
don't have it. :)
No you should care because one day you will come with a new requirement :)
I understand what you mean but the point is that Pharo is our common
architecture
so we should just all pay attention and we cannot ask people to do
everything because
we all have 24 h a day. So we should be smart, share and build together.
I mean the User approach that Benjmain proposed and was pushed in Pharo
was not good because it was not modular. Now each part of the system
should be
defined in way that it can be set just as a setting.
We should not have
World ....
User current = ifTrue
But
World use: userSetting
and World should handle it.
There is way more to do :)
When you deploy on linux you should be able to say beSilent to the
system (do not write on places that you cannot).
Valentin works on it and we should continue
Stef
The fact that there is much more to do is the main reason for Pharo to
do it and not the developer. The developer cannot know all the system
and will not be able to protect the code of his company well because he
will forget something as to disable ctrl+o+p (or he is a god developer!
But everyone is not).
This is a large thing to do, so it would be cool that everyone keep that
in mind to allow it little by little (as with the work of Valentin).
