July 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Code porting to Pharo 6.1-64

by Guillermo Polito

Hi Dario, Have you defined those methods in the class side? a) propertyAt: aKey ifAbsent: aBlock > ^ self properties at: aKey ifAbsent: aBlock > b) propertyAt: aKey ifAbsentPut: aBlock > ^ self properties at: aKey ifAbsentPut: aBlock > c) propertyAt: aKey put: aValue > ^ self properties at: aKey put: aValue > I will let Marcus answer more properly but I think you should rename those methods to not collapse with the behaviour in the base class... On Wed, Jul 4, 2018 at 8:16 PM dario.trussardi(a)tiscali.it < dario.trussardi(a)tiscali.it> wrote: > I wrong....... > > the error is relative to my root class ... > > For this class i implemented the class method > > propertyAt: aKey ifAbsent: aBlock > > This is in conflict with : > > the Behavior originalName method implement: > > ^ (( self isObsolete and:[ self name beginsWith: 'AnObsolete ............ > > > where isObsolete TClass is: > > self propertyAt: #obsolete ifAbsent: false > > Thanks for considerations, > > Dario > > Ciao, > > i work to port some code from Pharo 4.0 to Pharo 6.1-64. > > My root class into Pharo 4.0 define the properties > > instance variable and some relative method: > > a) propertyAt: aKey ifAbsent: aBlock > > ^ self properties at: aKey ifAbsent: aBlock > > b) propertyAt: aKey ifAbsentPut: aBlock > > ^ self properties at: aKey ifAbsentPut: aBlock > > c) propertyAt: aKey put: aValue > > ^ self properties at: aKey put: aValue > > d)...... > > Now when i port this code into the Pharo 6.1-64 when compile the code > > the Behavior originalName method implement: > > ^ (( self isObsolete and:[ self name beginsWith: 'AnObsolete ............ > > > where isObsolete TClass is: > > self propertyAt: #obsolete ifAbsent: false > > > But my class implement a specific propertyAt: ifAbsent: method > > and the system generates errors and don't compile the code. > > > Thank you for every consideration. > > Dario > > > > > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

July 5, 2018

Re: [Pharo-users] do-it or inspect-it in the spotter search bar?

by Paul DeBruicker

I had time today to implement this. The attached mczs, in pharo 6.1, allow you to hit Cmd-i to inspect or cmd-d to do it. You can test by loading the test package and typing in the spotter search bar, GTCounter increaseValue then hitting Cmd-d several times then Cmd-i to see what value you ended on. To implement I edited the GTSpotterMorph>>bindingDictionnary to look for and act cmd-i and cmd-d GT-Spotter-PaulDeBruicker.mcz <http://forum.world.st/file/t94460/GT-Spotter-PaulDeBruicker.mcz> GT-Tests-Spotter-PaulDeBruicker.mcz <http://forum.world.st/file/t94460/GT-Tests-Spotter-PaulDeBruicker.mcz> Paul DeBruicker wrote > I was feeling lazy was wondered if it would be possible to hit Cmd-D or > Cmd-I in the spotter input field rather than opening a playground and > typing something in then hitting it. E.g. > > > 1 + 1 Cmd-I > > would open an inspector on the number 2 > > > After looking at GTSpotter>>#spotterFor... methods I couldn't figure out > how to make it happen in the half hour I had to spend on it. > > > I recognize opening the playground is Cmd-O Cmd-W but I just open the > spotter ~50x as often as a new playground so the muscle memory isn't > there. If I could do quick one-liners in the spotter then the playground > would get opened even less often. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

July 5, 2018

Re: [Pharo-users] Code porting to Pharo 6.1-64

by dario.trussardi＠tiscali.it

I wrong....... the error is relative to my root class ... For this class i implemented the class method propertyAt: aKey ifAbsent: aBlock This is in conflict with : the Behavior originalName method implement: ^ (( self isObsolete and:[ self name beginsWith: 'AnObsolete ............ where isObsolete TClass is: self propertyAt: #obsolete ifAbsent: false Thanks for considerations, Dario > Ciao, > > i work to port some code from Pharo 4.0 to Pharo 6.1-64. > > My root class into Pharo 4.0 define the properties > > instance variable and some relative method: > > a) propertyAt: aKey ifAbsent: aBlock > > ^ self properties at: aKey ifAbsent: aBlock > > b) propertyAt: aKey ifAbsentPut: aBlock > > ^ self properties at: aKey ifAbsentPut: aBlock > > c) propertyAt: aKey put: aValue > > ^ self properties at: aKey put: aValue > > d)...... > > Now when i port this code into the Pharo 6.1-64 when compile the code > > the Behavior originalName method implement: > > ^ (( self isObsolete and:[ self name beginsWith: 'AnObsolete ............ > > > where isObsolete TClass is: > > self propertyAt: #obsolete ifAbsent: false > > > But my class implement a specific propertyAt: ifAbsent: method > > and the system generates errors and don't compile the code. > > > Thank you for every consideration. > > Dario > > > >

July 4, 2018

Code porting to Pharo 6.1-64

by dario.trussardi＠tiscali.it

Ciao, i work to port some code from Pharo 4.0 to Pharo 6.1-64. My root class into Pharo 4.0 define the properties instance variable and some relative method: a) propertyAt: aKey ifAbsent: aBlock ^ self properties at: aKey ifAbsent: aBlock b) propertyAt: aKey ifAbsentPut: aBlock ^ self properties at: aKey ifAbsentPut: aBlock c) propertyAt: aKey put: aValue ^ self properties at: aKey put: aValue d)...... Now when i port this code into the Pharo 6.1-64 when compile the code the Behavior originalName method implement: ^ (( self isObsolete and:[ self name beginsWith: 'AnObsolete ............ where isObsolete TClass is: self propertyAt: #obsolete ifAbsent: false But my class implement a specific propertyAt: ifAbsent: method and the system generates errors and don't compile the code. Thank you for every consideration. Dario

July 4, 2018

Instance of IceUnknownBranch did not understand #id

by HernÃ¡n Morales Durand

I wonder if anyone could help here. I am installing a BaselineOf in Pharo 6.1 (Windows) using a script like the following: Iceberg enableMetacelloIntegration: true; remoteTypeSelector: #httpsUrl. Metacello new baseline: 'MyProject'; repository: 'github://user/repo/src'; load. Unfortunately the repository is private and I cannot share the URL. When I open the Iceberg UI all downloaded packages has "Local repository missing" (see screenshots). To fix this currently I assign manually the local directory (assuming they were correctly downloaded). Also I tried adding repository information in the #baseline: method baseline: spec <baseline> spec baseline: 'MyProject' with: [ spec repository: 'github://user/repo' ]. .... Any idea how could I debug this? Cheers, HernÃ¡n

July 4, 2018

[ANN] New Academic Partner: University of YaoundÃ© 1

by Marcus Denker

The Pharo Consortium is very happy to announce that University of YaoundÃ© 1 has joined as a Academic Partner. About - University of YaoundÃ© 1: http://www.uy1.uninet.cm - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org

July 4, 2018

Re: [Pharo-users] MJpeg and ZdcSocketStream>>upToAll:limit: DNU

by CÃ©drick BÃ©ler

I published the small changes on Richard repo. Cheers, CÃ©drick > Le 4 juil. 2018 Ã 16:30, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> a Ã©crit : > > Worked like a charm ;) > > <PastedGraphic-8.png> > > Still some windows problem I guess: blue line. But cool :) > > Any idea on how to get ZdcSocketStream work instead ? > > Thnaks, > > CÃ©drick > >> Le 4 juil. 2018 Ã 16:26, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> a Ã©crit : >> >> Well, you could also try switching the socket stream class Zn uses to the old one: >> >> ZnNetworkingUtils default socketStreamClass: SocketStream. >> >> This is a global setting affecting all Zn operations. >> >> And then move the #limit: back in. >> >>> On 4 Jul 2018, at 16:22, CÃ©drick BÃ©ler <cdrick65(a)gmail.com <mailto:cdrick65@gmail.com>> wrote: >>> >>> I changed to #upTo: >>> >>> >>> I have no more DNU, but no streaming is shown beside the test image (I think it comes from MJpeg). >>> >>> Testing on a public URL gives the same resultâ¦ (webcam.st-malo.com <http://webcam.st-malo.com/>). >>> >>> <PastedGraphic-7.png> >>> >>> Iâll try more (IâCCed the orignal author). >>> >>> Thx Sven, >>> >>> >>> CÃ©drick >>> >>> >>> >>> <Mjpeg.st <http://mjpeg.st/>> >>> >>> >>> >>> >>>> Le 4 juil. 2018 Ã 16:03, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> a Ã©crit : >>>> >>>> That is old. I vaguely remember running that, it did work at the time. >>>> >>>> Indeed #upToAll:limit: is SocketStream specific. >>>> >>>> I guess you could just (try to) remove the #limit: part, it is just a kind of safety measure to stop when the boundary is not found (as the stream is unlimited). >>>> >>>>> On 4 Jul 2018, at 15:54, CÃ©drick BÃ©ler <cdrick65(a)gmail.com <mailto:cdrick65@gmail.com>> wrote: >>>>> >>>>> Hi, >>>>> >>>>> Iâm trying to get a video stream in Pharo from a Pi video stream using this lib on the. Pi (https://github.com/jacksonliam/mjpg-streamer <https://github.com/jacksonliam/mjpg-streamer>) >>>>> >>>>> Then I found this library on Pharo (from 2013). >>>>> https://www.min.at/prinz/?entry=entry130413-020021 <https://www.min.at/prinz/?entry=entry130413-020021> >>>>> http://www.min.at/prinz/repo/mjpeg >>>>> >>>>> I had to change a method relative to Annoucment. #on:do: => #when:do: >>>>> >>>>> Now I have a problem in Pharo 7 (same in Pharo 6) with ZdcSocketStream>>upToAll:limit: (see pic) >>>>> >>>>> >>>>> >>>>> <PastedGraphic-6.png> >>>>> >>>>> >>>>> >>>>> TIA, >>>>> >>>>> CÃ©drick >>>>> >>>> >>>> >>> >> >> >

July 4, 2018

Re: [Pharo-users] MJpeg and ZdcSocketStream>>upToAll:limit: DNU

by CÃ©drick BÃ©ler

Worked like a charm ;) Still some windows problem I guess: blue line. But cool :) Any idea on how to get ZdcSocketStream work instead ? Thnaks, CÃ©drick > Le 4 juil. 2018 Ã 16:26, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : > > Well, you could also try switching the socket stream class Zn uses to the old one: > > ZnNetworkingUtils default socketStreamClass: SocketStream. > > This is a global setting affecting all Zn operations. > > And then move the #limit: back in. > >> On 4 Jul 2018, at 16:22, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: >> >> I changed to #upTo: >> >> >> I have no more DNU, but no streaming is shown beside the test image (I think it comes from MJpeg). >> >> Testing on a public URL gives the same resultâ¦ (webcam.st-malo.com) >> >> <PastedGraphic-7.png> >> >> Iâll try more (IâCCed the orignal author). >> >> Thx Sven, >> >> >> CÃ©drick >> >> >> >> <Mjpeg.st> >> >> >> >> >>> Le 4 juil. 2018 Ã 16:03, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : >>> >>> That is old. I vaguely remember running that, it did work at the time. >>> >>> Indeed #upToAll:limit: is SocketStream specific. >>> >>> I guess you could just (try to) remove the #limit: part, it is just a kind of safety measure to stop when the boundary is not found (as the stream is unlimited). >>> >>>> On 4 Jul 2018, at 15:54, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: >>>> >>>> Hi, >>>> >>>> Iâm trying to get a video stream in Pharo from a Pi video stream using this lib on the. Pi (https://github.com/jacksonliam/mjpg-streamer) >>>> >>>> Then I found this library on Pharo (from 2013). >>>> https://www.min.at/prinz/?entry=entry130413-020021 >>>> http://www.min.at/prinz/repo/mjpeg >>>> >>>> I had to change a method relative to Annoucment. #on:do: => #when:do: >>>> >>>> Now I have a problem in Pharo 7 (same in Pharo 6) with ZdcSocketStream>>upToAll:limit: (see pic) >>>> >>>> >>>> >>>> <PastedGraphic-6.png> >>>> >>>> >>>> >>>> TIA, >>>> >>>> CÃ©drick >>>> >>> >>> >> > >

July 4, 2018

Re: [Pharo-users] MJpeg and ZdcSocketStream>>upToAll:limit: DNU

by Sven Van Caekenberghe

Well, you could also try switching the socket stream class Zn uses to the old one: ZnNetworkingUtils default socketStreamClass: SocketStream. This is a global setting affecting all Zn operations. And then move the #limit: back in. > On 4 Jul 2018, at 16:22, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > > I changed to #upTo: > > > I have no more DNU, but no streaming is shown beside the test image (I think it comes from MJpeg). > > Testing on a public URL gives the same resultâ¦ (webcam.st-malo.com) > > <PastedGraphic-7.png> > > Iâll try more (IâCCed the orignal author). > > Thx Sven, > > > CÃ©drick > > > > <Mjpeg.st> > > > > >> Le 4 juil. 2018 Ã 16:03, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : >> >> That is old. I vaguely remember running that, it did work at the time. >> >> Indeed #upToAll:limit: is SocketStream specific. >> >> I guess you could just (try to) remove the #limit: part, it is just a kind of safety measure to stop when the boundary is not found (as the stream is unlimited). >> >>> On 4 Jul 2018, at 15:54, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: >>> >>> Hi, >>> >>> Iâm trying to get a video stream in Pharo from a Pi video stream using this lib on the. Pi (https://github.com/jacksonliam/mjpg-streamer) >>> >>> Then I found this library on Pharo (from 2013). >>> https://www.min.at/prinz/?entry=entry130413-020021 >>> http://www.min.at/prinz/repo/mjpeg >>> >>> I had to change a method relative to Annoucment. #on:do: => #when:do: >>> >>> Now I have a problem in Pharo 7 (same in Pharo 6) with ZdcSocketStream>>upToAll:limit: (see pic) >>> >>> >>> >>> <PastedGraphic-6.png> >>> >>> >>> >>> TIA, >>> >>> CÃ©drick >>> >> >> >

July 4, 2018

Re: [Pharo-users] MJpeg and ZdcSocketStream>>upToAll:limit: DNU

by CÃ©drick BÃ©ler

I changed to #upTo: I have no more DNU, but no streaming is shown beside the test image (I think it comes from MJpeg). Testing on a public URL gives the same resultâ¦ (webcam.st-malo.com <http://webcam.st-malo.com/>). Iâll try more (IâCCed the orignal author). Thx Sven, CÃ©drick > Le 4 juil. 2018 Ã 16:03, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : > > That is old. I vaguely remember running that, it did work at the time. > > Indeed #upToAll:limit: is SocketStream specific. > > I guess you could just (try to) remove the #limit: part, it is just a kind of safety measure to stop when the boundary is not found (as the stream is unlimited). > >> On 4 Jul 2018, at 15:54, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: >> >> Hi, >> >> Iâm trying to get a video stream in Pharo from a Pi video stream using this lib on the. Pi (https://github.com/jacksonliam/mjpg-streamer) >> >> Then I found this library on Pharo (from 2013). >> https://www.min.at/prinz/?entry=entry130413-020021 >> http://www.min.at/prinz/repo/mjpeg >> >> I had to change a method relative to Annoucment. #on:do: => #when:do: >> >> Now I have a problem in Pharo 7 (same in Pharo 6) with ZdcSocketStream>>upToAll:limit: (see pic) >> >> >> >> <PastedGraphic-6.png> >> >> >> >> TIA, >> >> CÃ©drick >> > >

July 4, 2018