- Pharo-users - lists.pharo.org

[ANN] New service: The Pharo catalog

by Esteban Lorenzano

Hi, Last week I made a super small project to consolidate all projects published in all metarepos. Is very simple, in the style of smalltalkhub repository list, but it shows all projects with the info their owners provided. Yes, it could be a lot better, but we do not want to lose much time with this because not far in the future (but not right now) we will put online a much better service :) You can see the catalog here: http://catalog.pharo.org <http://catalog.pharo.org/> and a JSON variant here: http://catalog.pharo.org/catalog/json <http://catalog.pharo.org/catalog/json> enjoy, Esteban

April 1, 2015

Re: [Pharo-users] Cormas Pharo Port v0.2 available

by Serge Stinckwich

Thank you Alex, for trying to dl CORMAS. Yes, I fix the problem. Should work now ;-) BTW, this is really difficult to understand the problem because when a dependancy is missing, there is a debug window with Warning but no explanation in the header. You have to click on the String, what dependancy is missing. Look at the attached screenshot. On Wed, Apr 1, 2015 at 1:32 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi Serge! > > Iâve tried to load Cormas, but I got an error about some missing dependenciesâ¦ > > Alexandre > > >> On Mar 31, 2015, at 5:00 PM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >> >> Dear all, >> >> I made available a new version (v0.2) of Cormas on Pharo. >> CORMAS is a multi-agent simulation engine that is running on >> VisualWorks Smalltalk: >> http://cormas.cirad.fr/indexeng.htm >> >> You can download this version by using the last Moose 5.1 image : >> https://ci.inria.fr/moose/job/moose-5.1/ >> >> and doing in a Playground: >> >> Gofer new >> url: 'http://smalltalkhub.com/mc/SergeStinckwich/CORMAS/main'; >> configurationOf: 'Cormas'; >> loadStable. >> >> At the moment, nothing is working ;-) >> Almost classes of the original VW version are now in Pharo except some >> classes like Jun* that will I guess disappear for the new version if >> we use ROASSAL instead. I will start to clean the code now in order to >> be able to run as simple model like Fire Automata model >> >> All the code is also available on github here: https://github.com/cormas/cormas >> >> If some of you want to be added in the CORMAS github org, please tell me: >> https://github.com/cormas >> I will feel less alone ;-) >> >> You can join the mailing-list to help here: >> https://groups.google.com/forum/#!forum/cormas-dev >> >> Regards, >> >> -- >> Serge Stinckwich >> UCBN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

April 1, 2015

Re: [Pharo-users] Proxies: Subclassing nil

by Luc Fabresse

and the latest repo is: http://smalltalkhub.com/#!/~CAR/Ghost but it has not diverged too much from the old one yet. #Luc 2015-04-01 8:29 GMT+02:00 stepharo <stepharo(a)free.fr>: > Mariano spent a couple of years on it so... > > > > Le 31/3/15 21:37, Denis Kudriashov a Ã©crit : > > Hi > if you want to build proxy look at Ghost library from Mariano Martinez > I not know right repository. Maybe this: > http://smalltalkhub.com/#!/~CAR/Ghost/ or http://ss3.gemstone.com/ss/Ghost > > 2015-03-31 19:51 GMT+03:00 Sean P. DeNigris <sean(a)clipperadams.com>: > >> From "Design Patterns" pg. 215: >> >> You can make[8] generic proxies in Smalltalk by defining classes whose >> superclass is nil and defining the doesNotUnderstand: method to handle >> messages. >> >> [8] Almost all classes ultimately have Object as their superclass. >> Hence >> this is the same as saying "defining a class that doesn't have Object as >> its >> superclass." >> >> but in Pharo: >> nil subclass: #MyProxy >> instanceVariableNames: '' >> classVariableNames: '' >> category: '' >> -> MessageNotUnderstood: receiver of >> "subclass:instanceVariableNames:classVariableNames:category:" is nil >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/Proxies-Subclassing-nil-tp4816443.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> > >

April 1, 2015

Re: [Pharo-users] Proxies: Subclassing nil

by stepharo

Mariano spent a couple of years on it so... Le 31/3/15 21:37, Denis Kudriashov a Ã©crit : > Hi > if you want to build proxy look at Ghost library from Mariano Martinez > I not know right repository. Maybe > this:http://smalltalkhub.com/#!/~CAR/Ghost/ > <http://smalltalkhub.com/#%21/%7ECAR/Ghost/> or > http://ss3.gemstone.com/ss/Ghost > > 2015-03-31 19:51 GMT+03:00 Sean P. DeNigris <sean(a)clipperadams.com > <mailto:sean@clipperadams.com>>: > > From "Design Patterns" pg. 215: > > You can make[8] generic proxies in Smalltalk by defining > classes whose > superclass is nil and defining the doesNotUnderstand: method to handle > messages. > > [8] Almost all classes ultimately have Object as their > superclass. Hence > this is the same as saying "defining a class that doesn't have > Object as its > superclass." > > but in Pharo: > nil subclass: #MyProxy > instanceVariableNames: '' > classVariableNames: '' > category: '' > -> MessageNotUnderstood: receiver of > "subclass:instanceVariableNames:classVariableNames:category:" is nil > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Proxies-Subclassing-nil-tp4816443.html > Sent from the Pharo Smalltalk Users mailing list archive at > Nabble.com. > >

April 1, 2015

Re: [Pharo-users] Cormas Pharo Port v0.2 available

by stepharo

Excellent serge! Keep pushing. Le 31/3/15 22:00, Serge Stinckwich a Ã©crit : > Dear all, > > I made available a new version (v0.2) of Cormas on Pharo. > CORMAS is a multi-agent simulation engine that is running on > VisualWorks Smalltalk: > http://cormas.cirad.fr/indexeng.htm > > You can download this version by using the last Moose 5.1 image : > https://ci.inria.fr/moose/job/moose-5.1/ > > and doing in a Playground: > > Gofer new > url: 'http://smalltalkhub.com/mc/SergeStinckwich/CORMAS/main'; > configurationOf: 'Cormas'; > loadStable. > > At the moment, nothing is working ;-) > Almost classes of the original VW version are now in Pharo except some > classes like Jun* that will I guess disappear for the new version if > we use ROASSAL instead. I will start to clean the code now in order to > be able to run as simple model like Fire Automata model > > All the code is also available on github here: https://github.com/cormas/cormas > > If some of you want to be added in the CORMAS github org, please tell me: > https://github.com/cormas > I will feel less alone ;-) > > You can join the mailing-list to help here: > https://groups.google.com/forum/#!forum/cormas-dev > > Regards, >

April 1, 2015

Re: [Pharo-users] Cormas Pharo Port v0.2 available

by Alexandre Bergel

Hi Serge! Iâve tried to load Cormas, but I got an error about some missing dependenciesâ¦ Alexandre > On Mar 31, 2015, at 5:00 PM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > Dear all, > > I made available a new version (v0.2) of Cormas on Pharo. > CORMAS is a multi-agent simulation engine that is running on > VisualWorks Smalltalk: > http://cormas.cirad.fr/indexeng.htm > > You can download this version by using the last Moose 5.1 image : > https://ci.inria.fr/moose/job/moose-5.1/ > > and doing in a Playground: > > Gofer new > url: 'http://smalltalkhub.com/mc/SergeStinckwich/CORMAS/main'; > configurationOf: 'Cormas'; > loadStable. > > At the moment, nothing is working ;-) > Almost classes of the original VW version are now in Pharo except some > classes like Jun* that will I guess disappear for the new version if > we use ROASSAL instead. I will start to clean the code now in order to > be able to run as simple model like Fire Automata model > > All the code is also available on github here: https://github.com/cormas/cormas > > If some of you want to be added in the CORMAS github org, please tell me: > https://github.com/cormas > I will feel less alone ;-) > > You can join the mailing-list to help here: > https://groups.google.com/forum/#!forum/cormas-dev > > Regards, > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 31, 2015

Re: [Pharo-users] Proxies: Subclassing nil

by Mariano Martinez Peck

On Tue, Mar 31, 2015 at 8:05 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Hey Sean, > > Now to create a proxy you need to subclass ProtoObject and not nil. > > Yes, subclassing from nil was never a good idea. > This was changed years ago to avoid some issues. An example of issue that > existed: when you subclass nil, as > #doesNotUnderstand: is not implemented by default on your proxy, any proxy > created receiving a message would crash the VM if you had not overridded > #doesNotUnderstand:. Another example is that when you iterate over memory > using #nextObject, if the proxy does not answer it you can end with severe > VM crashes. In these examples I am talking about the expected VM behavior > and not about bugs. > > Marea (kind of extended Ghost proxies) proxies deal with object listing. If you load Marea code, see class side of #MARAbstractProxy (#allInstances, #allInstancesDo: etc). > So basically the purpose of ProtoObject was to limit the number of VM > crashes when playing with proxies / ProtoObjects, instead having a default > behavior for several messages such as #doesNotUnderstand: or nextObject. > > Note that the IDE support for ProtoObject is limited as ProtoObject API is > very restricted so it does not have methods such as #inspect, ... That's > also on purpose because Proxies may not implement introspection methods. > > Yes. Ghost proxies provided debugger facilities (printing, inspecting, debugging, exploring, etc) which could be dynamically either enabled or disabled. If enabled, you could debug proxies without intercepting the "debugging" methods. > > > > > 2015-03-31 14:53 GMT-07:00 Sean P. DeNigris <sean(a)clipperadams.com>: > > Denis Kudriashov wrote >> > http://smalltalkhub.com/#!/~CAR/Ghost/ or >> http://ss3.gemstone.com/ss/Ghost >> >> Thanks, Denis! I'll check it out. I'm not sure which repo either. >> Mariano's >> commits are all in both places, but there seems to be some parallel >> development after that... >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/Proxies-Subclassing-nil-tp4816443p4816503.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> > -- Mariano http://marianopeck.wordpress.com

March 31, 2015

Re: [Pharo-users] Proxies: Subclassing nil

by ClÃ©ment Bera

Hey Sean, Now to create a proxy you need to subclass ProtoObject and not nil. This was changed years ago to avoid some issues. An example of issue that existed: when you subclass nil, as #doesNotUnderstand: is not implemented by default on your proxy, any proxy created receiving a message would crash the VM if you had not overridded #doesNotUnderstand:. Another example is that when you iterate over memory using #nextObject, if the proxy does not answer it you can end with severe VM crashes. In these examples I am talking about the expected VM behavior and not about bugs. So basically the purpose of ProtoObject was to limit the number of VM crashes when playing with proxies / ProtoObjects, instead having a default behavior for several messages such as #doesNotUnderstand: or nextObject. Note that the IDE support for ProtoObject is limited as ProtoObject API is very restricted so it does not have methods such as #inspect, ... That's also on purpose because Proxies may not implement introspection methods. 2015-03-31 14:53 GMT-07:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Denis Kudriashov wrote > > http://smalltalkhub.com/#!/~CAR/Ghost/ or > http://ss3.gemstone.com/ss/Ghost > > Thanks, Denis! I'll check it out. I'm not sure which repo either. Mariano's > commits are all in both places, but there seems to be some parallel > development after that... > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Proxies-Subclassing-nil-tp4816443p4816503.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

March 31, 2015

Re: [Pharo-users] Proxies: Subclassing nil

by Sean P. DeNigris

Sean P. DeNigris wrote > Thanks, Denis! I'll check it out. I'm not sure which repo either I loaded the Pharo 3.0 stable version of the Metacello config in MetaRepoForPharo30 (1.2). All tests pass, so I updated the config for 4.0 and copied it to the meta repo for 40 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Proxies-Subclassing-nil-tp4816443p4816517.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 31, 2015

Re: [Pharo-users] [Moose-dev] loading Glamour in Pharo 4

by Andrei Chis

Still in this case the problem seems to be that version 0.1 from ConfigurationOfForum wants to load the development version of Glamour in a Moose 5.0 image, which is not going to work. Cheers, Andrei On Tue, Mar 31, 2015 at 4:46 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > These configurations/the metacello handling of them are > still pretty seriously broken. In Forum from the > Moose CI I cannot run the script because it throws an > error which triggers the broken debugger. As does opening > the workspace. I suspect there are quite some broken > green builds on ci atm. > > Stephan > >

March 31, 2015