cutting dependencies

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

cutting dependencies

Stéphane Ducasse
Hi guys,

Just to keep you informed. Tomorrow we will use Moose on Pharo1.1core to assess some dependencies
between packages. We already did that in the past and cut some obvious dependencies. We will redo one
step with Jannik and Marcus. We will probably redo a couple of sessions. The goal is to identify evil cyclic dependencies
and fix them. The tool of jannik is good for that and we applied it on Morphic now we want to apply it on
pharo.

In the past we fixed some problems and identified missing infrastructural elements. For example
the lack of a registration mechanism for the main menu. Now the fact that Setting is cool will also
reduce some problems we saw before. This will raise the question of the usage of services too.
Because Services are a registration mechanism.

Some of you may have noticed that Andreas was successful to remove some packages from Squeak.
It should be noted that a lot of these packages are already unloadable in Pharo :)
The reorganization also in Test was already done in pharo. Lot of the changes happening in Squeak now
(except some of the speed improvements) has already been done some time ago in Pharo.
So this is nice to see that our vision was right.
During a couple of years we pushed to get a smaller/cleaner system in Squeak and this is happening.
So this is nice to see that we are right even if most people will not recognize or remember it :)

Stef (going swimming in this cold winter).



_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: cutting dependencies

Alexandre Bergel
> Just to keep you informed. Tomorrow we will use Moose on  
> Pharo1.1core to assess some dependencies
> between packages. We already did that in the past and cut some  
> obvious dependencies. We will redo one
> step with Jannik and Marcus. We will probably redo a couple of  
> sessions. The goal is to identify evil cyclic dependencies
> and fix them. The tool of jannik is good for that and we applied it  
> on Morphic now we want to apply it on
> pharo.

Excellent!

Alexandre

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.






_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: cutting dependencies

Alain Plantec-4
In reply to this post by Stéphane Ducasse
Stéphane Ducasse a écrit :
> Now the fact that Setting is cool will also
> reduce some problems we saw before. This will raise the question of the usage of services too.
> Because Services are a registration mechanism.
>  
I thought that Services was to be removed and I've started to do so (It
would allow to fully remove Preferences).
Have I missed something ?
Alain


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: cutting dependencies

Marcus Denker-4

On Jan 6, 2010, at 5:44 PM, Alain Plantec wrote:

> Stéphane Ducasse a écrit :
>> Now the fact that Setting is cool will also
>> reduce some problems we saw before. This will raise the question of the usage of services too.
>> Because Services are a registration mechanism.
>>
> I thought that Services was to be removed and I've started to do so (It
> would allow to fully remove Preferences).
> Have I missed something ?

No, services (the artefact that is there now, unused) should be removed. But we might need to introduce
something similar (but simpler) later again.

        Marcus
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: cutting dependencies

Stéphane Ducasse

On Jan 6, 2010, at 7:54 PM, Marcus Denker wrote:

>
> On Jan 6, 2010, at 5:44 PM, Alain Plantec wrote:
>
>> Stéphane Ducasse a écrit :
>>> Now the fact that Setting is cool will also
>>> reduce some problems we saw before. This will raise the question of the usage of services too.
>>> Because Services are a registration mechanism.
>>>
>> I thought that Services was to be removed and I've started to do so (It
>> would allow to fully remove Preferences).
>> Have I missed something ?
>
> No, services (the artefact that is there now, unused) should be removed. But we might need to introduce
> something similar (but simpler) later again.

Yes we will have

>
> Marcus
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project