August 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Announcer problem :)

by StÃ©phane Ducasse

So igor is thinking about ephemerons and object formats. Because we are going over all the weak on:do: and rewriting the ones we can. whenListChanged: aBlock "Specify a block to value after the contents of the list has changed" "Basically when you set a new list of items" <api: #event> | block | block := [ :announcement :ann | aBlock cull: announcement newContents cull: announcement oldContents cull: announcement cull: ann ]. listAnnouncer weak on: ValueChanged do: block On Aug 4, 2013, at 4:16 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > addDependent: anObject > > self announcer > on: MorphChanged > do: [ :ann | anObject update: ann selector ]. > > self announcer > on: MorphChangedWithArguments > do: [ :ann | anObject update: ann selector with: ann arguments ]. > > ^ anObject > > is an example of the problem because addDependent: was holding also weakly its dependent and now > we cannot use weak with blocks. > > Stef

Aug. 4, 2013

is there anyone who can use SimpleMIDIPort on Mac OSX 10.6.8?

by NISHIHARA Satoshi

is there anyone who can use SimpleMIDIPort on Mac OSX 10.6.8? StÃ©phane Ducasse san told me that it can use MIDIPlugin in Pharo 2.0 on Mac 10.8.3. but I can't use MIDIPlugin on Mac OSX 10.6.8. SimpleMIDIPort>>#midiIsSupported -> false SimpleMIDIPort>>#primPortCount -> 0 vm: Pharo.app(13/03/13) Pharo-126.app(13/05/04) Pharo-145.app(13/05/31) Pharo-169.app(13/07/10) Pharo-186.app(13/07/15) Pharo-187.app(13/07/19) Pharo-188.app(13/07/31) I would like to know whether it is a problem of all those that are using 10.6.8 or personal trouble. -p.s.- On Eliot Miranda san's CogMT.r2761.app and Cog.r2761.app, SimpleMIDIPort>>#midiIsSupported -> true SimpleMIDIPort>>#primPortCount -> 1 regards.

Aug. 4, 2013

Re: [Pharo-dev] [Pharo-fuel] Fuel API bug

by StÃ©phane Ducasse

impressive :) Tx guys. We are fighting with memory leaks like mad :) Stef On Aug 4, 2013, at 4:49 PM, Max Leske <maxleske(a)gmail.com> wrote: > Done. > > Name: ConfigurationOfFuel-MaxLeske.207 > Author: MaxLeske > Time: 4 August 2013, 4:49:17.037 pm > UUID: 5cc59075-e365-4a58-a20b-22e40b2b70c9 > Ancestors: ConfigurationOfFuel-MartinDias.206 > > * created new version 1.9.2 for development > * pointed development to 1.9.2 > * includes changes Camillo wanted to introduce into 1.9.1 (DateAndTime fix) > > > On 04.08.2013, at 16:35, Max Leske <maxleske(a)gmail.com> wrote: > >> Yeah, no problem. I'll get on it right away. >> >> Max >> >> On 04.08.2013, at 16:10, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> Hi guys >>> >>> can you rename this method? >>> >>> on: aCollectionOrStream do: aBlock >>> "Evaluates a block with a new stream based on the collection or stream. Answers the result of the block evaluation. Follows the style of FileStream>>fileNamed:do:." >>> | aStream | >>> aStream := self on: aCollectionOrStream. >>> [ ^ aBlock value: aStream ] ensure: [ aStream close ] >>> >>> >>> Please do not use on:do: for something that is not about exception (and announcements). >>> >>> It is too confusing and refactor after. >>> >>> Stef >> > > > _______________________________________________ > Pharo-fuel mailing list > Pharo-fuel(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-fuel

Aug. 4, 2013

Re: [Pharo-dev] Fuel API bug

by Max Leske

Done. Name: ConfigurationOfFuel-MaxLeske.207 Author: MaxLeske Time: 4 August 2013, 4:49:17.037 pm UUID: 5cc59075-e365-4a58-a20b-22e40b2b70c9 Ancestors: ConfigurationOfFuel-MartinDias.206 * created new version 1.9.2 for development * pointed development to 1.9.2 * includes changes Camillo wanted to introduce into 1.9.1 (DateAndTime fix) On 04.08.2013, at 16:35, Max Leske <maxleske(a)gmail.com> wrote: > Yeah, no problem. I'll get on it right away. > > Max > > On 04.08.2013, at 16:10, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Hi guys >> >> can you rename this method? >> >> on: aCollectionOrStream do: aBlock >> "Evaluates a block with a new stream based on the collection or stream. Answers the result of the block evaluation. Follows the style of FileStream>>fileNamed:do:." >> | aStream | >> aStream := self on: aCollectionOrStream. >> [ ^ aBlock value: aStream ] ensure: [ aStream close ] >> >> >> Please do not use on:do: for something that is not about exception (and announcements). >> >> It is too confusing and refactor after. >> >> Stef >

Aug. 4, 2013

Re: [Pharo-dev] Fuel API bug

by Max Leske

Yeah, no problem. I'll get on it right away. Max On 04.08.2013, at 16:10, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > can you rename this method? > > on: aCollectionOrStream do: aBlock > "Evaluates a block with a new stream based on the collection or stream. Answers the result of the block evaluation. Follows the style of FileStream>>fileNamed:do:." > | aStream | > aStream := self on: aCollectionOrStream. > [ ^ aBlock value: aStream ] ensure: [ aStream close ] > > > Please do not use on:do: for something that is not about exception (and announcements). > > It is too confusing and refactor after. > > Stef

Aug. 4, 2013

Re: [Pharo-dev] about on:do: -> onKey:do:

by Esteban Lorenzano

On Aug 4, 2013, at 4:11 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > No because the asKeyCombination is sent to the argument by the onKey:do: method. I don't really see the relation :) > We will be able to rename it anyway once we sort the problems. yep! most important is to move on and fix that annoying bug. > > >> I would use #onKeyCombination:do: to keep coherency with the framework. >> >> On Aug 4, 2013, at 3:04 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> Hi ben and others >>> >>> we are introducing onKey:do: for bindings so that we can control the complexity and the registration >>> of announcements. So if you can I have a look it would be good. >>> >>> https://pharo.fogbugz.com/default.asp?11299 >>> >>> Stef >> >> > >

Aug. 4, 2013

Announcer problem :)

by StÃ©phane Ducasse

addDependent: anObject self announcer on: MorphChanged do: [ :ann | anObject update: ann selector ]. self announcer on: MorphChangedWithArguments do: [ :ann | anObject update: ann selector with: ann arguments ]. ^ anObject is an example of the problem because addDependent: was holding also weakly its dependent and now we cannot use weak with blocks. Stef

Aug. 4, 2013

Re: [Pharo-dev] about on:do: -> onKey:do:

by StÃ©phane Ducasse

No because the asKeyCombination is sent to the argument by the onKey:do: method. We will be able to rename it anyway once we sort the problems. > I would use #onKeyCombination:do: to keep coherency with the framework. > > On Aug 4, 2013, at 3:04 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Hi ben and others >> >> we are introducing onKey:do: for bindings so that we can control the complexity and the registration >> of announcements. So if you can I have a look it would be good. >> >> https://pharo.fogbugz.com/default.asp?11299 >> >> Stef > >

Aug. 4, 2013

Fuel API bug

by StÃ©phane Ducasse

Hi guys can you rename this method? on: aCollectionOrStream do: aBlock "Evaluates a block with a new stream based on the collection or stream. Answers the result of the block evaluation. Follows the style of FileStream>>fileNamed:do:." | aStream | aStream := self on: aCollectionOrStream. [ ^ aBlock value: aStream ] ensure: [ aStream close ] Please do not use on:do: for something that is not about exception (and announcements). It is too confusing and refactor after. Stef

Aug. 4, 2013

Re: [Pharo-dev] about on:do: -> onKey:do:

by Esteban Lorenzano

I would use #onKeyCombination:do: to keep coherency with the framework. On Aug 4, 2013, at 3:04 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi ben and others > > we are introducing onKey:do: for bindings so that we can control the complexity and the registration > of announcements. So if you can I have a look it would be good. > > https://pharo.fogbugz.com/default.asp?11299 > > Stef

Aug. 4, 2013