Thanks! I really think that we should systematically use a dependency management system. Of course it does not fix the problems but we can move on. I think that we can benefit of the idea of a platform classes hierarchy, this is why we push the change.
>>>>>>> I will integrate the following SocketStream tests and before I would >>>>>>> love to see if this >>>>>>> does not impact seaside >>>>>>> >>>>>>> http://code.google.com/p/pharo/issues/detail?id=2767 >>> >>> Does anybody have the time to give feedback on this important network >>> changes? >> >> I did a short test with Seaside and everything still seems to work. And >> if it fixes bugs, I'm all tits forward about it. Ok I will integrate it now. This was the next item on the list. >> The deprecation of SmalltalkImage >> #platformName is a PITA though. It >> requires us to have different versions of Comanche and WebClient for >> different versions of Pharo. I will integrate now webClient. May be I will need to know what I should load in. :) > Pharo 1.0 is long outdated, Pharo 1.2 is not stable yet. We should > only target Pharo 1.1. > > Also the latest development tools only work in Pharo 1.1. There is no > point in making Seaside work in all versions. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
