On Thu, Jul 22, 2010 at 3:45 PM, Adrian Lienhard <adi@netstyle.ch> wrote:

On Jul 22, 2010, at 14:42 , St�phane Ducasse wrote:

> probably because we were stupid to remove it from the image.

I don't think so.

Rather because we have:
- nobody who takes responsibility to maintain this package
- no tests for this package
- no build and test server to detect problems automatically


I think it is a combination of the 2. First, we are not stupid to remove it from core. They HAVE to be removed and put it as separate package.

Then, I agree with ALL adrian comments. But I also agree that this problem can be minimized. When you remove methods/classes in PharoCore, it would be good to search them in "Pharo". That's why I did ConfigurationOfPharoNonCore.

Cheers

Mariano
�
Cheers,
Adrian

BTW, the two expressions posted below work for me on a recent Mac VM in a Pharo 1.0 image.


> If you can check there are two fixes on the bug archives and it would be great that somebody compares with squeak
> version. I did not see that much changes from this part of the system on their side.
>
> Stef
> On Jul 22, 2010, at 2:36 PM, Hilaire Fernandes wrote:
>
>> I tried the Pharo sound package, so far it looks sound is not working.
>> Is it true or is it a mistake of myself.
>>
>> For example:
>>
>> No sound output when executing:
>> FMSound bass1 play
>>
>> DNU FMSound copy when executing:
>> (FMSound lowMajorScaleOn: FMSound bass1) play
>>
>> Hilaire
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project