March 2015 - Pharo-users - lists.pharo.org

[ANN] Dr. Geo 15.04
by Hilaire April 1, 2015

April 1, 2015

Hello, Dr. Geo 15.04 released today, based on Pharo 3. http://www.drgeo.eu/news/drgeo1504 Thanks for your support Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

4 5

Proxies: Subclassing nil
by Sean P. DeNigris April 1, 2015

April 1, 2015

>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.

6 8

Re: [Pharo-users] Proxies: Subclassing nil
by Sean P. DeNigris March 31, 2015

March 31, 2015

jtuchel wrote > I am not an expert in Pharo, but I think you should try subclassing > ProtoObject... I wonder if it was correct that subclassing nil used to be allowed and the proper way to create a proxy, and if so why it was changed... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Proxies-Subclassing-nil-tp4816443p4816502.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

1 0

Re: [Pharo-users] Proxies: Subclassing nil
by Joachim Tuchel March 31, 2015

March 31, 2015

Sean, I am not an expert in Pharo, but I think you should try subclassing ProtoObject... Joachim Am 31.03.2015 18:51 schrieb "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. > >

1 0

Issue on enabling developer options in Pharo Launcher
by Jigyasa Grover March 31, 2015

March 31, 2015

Sir I have installed the latest version of PharoLauncher on my system (OS : Ubuntu 14.04) Whenever I try to enable the developer option in the settings , I get a warning dialog , in which clicking on Proceed hangs up the application. I have repeated the process twice or thrice , but am stuck at the same position. I have attached the screenshot of the warning recieved. Kindly review this issue. Thanks and Regards Jigyasa Grover

6 12

Porting Voss to Pharo
by stepharo March 31, 2015

March 31, 2015

Hi guys if some of you are interested to drive porting VOSS to Pharo, let me know John sent me the code and I can give it to you. There is a dual license - LGPL - commercial Now I do not know the prices for business. Stef Begin forwarded message: From: "John Clapperton" <jc(a)logicarts.com> Subject: VOSS Porting Tips 001 Date: 24 Feb 2015 11:30:37 GMT+1 To: 'StÃ©phane Ducasse' <stephane.ducasse(a)inria.fr> Hi Stephane, I strongly recommend first installing VOSS in VA Smalltalk and working through the tutorial to get the feel of it; then single-step in the debugger through the essential functionality to see how it works, in particular the way messages sent to VORef proxies are forwarded to virtual objects instantiated in the virtual space's VOCache after loading from disk. The public face of a virtual space is an instance of VOManager, which knows the file pathname etc, and which references an instance of VOStorageManager, which is wrapped in a mutual exclusion VOSMShell, so that only one Smalltalk process is allowed in at a time. Inside the VOStorageManager is an instance of VOCache (subclass of VOOrderedDictionary, subclass of Dictionary), which contains all the virtual objects (in that virtual space) currently instantiated in the image. VORef has three instance variables 'voManager id association '. Any message sent to a VORef which is not understood by it (i.e. most of them, it's a proxy) is forwarded to the VORef's VOManager, where it waits for exclusive access to the VOStorageManager. In there, it (the process) looks for that object's id in the VOCache (if not there it's loaded from disk), the object's fixed length (21 bytes) descriptor record in the sparse index file myspace.vot is locked (against other images on other machines), and its VOCacheAssociation is locked into the process's current VOTransaction (which contains a VOOrderedSet of VORefs) against access by other processes in that image, and is assigned to the VORef's 'association' instance variable. The process then returns out of the VOStorageManager, out of the mutual exclusion shell, and back in the context of the VOManager the instantiated virtual object (referenced by the locked VOCacheAssociation's 'value' instvar) is told to perform the message, and whatever that returns is returned to the original sender (if it returns self, then the VORef is returned to the sender). I seem to have got rather deep rather quickly there; let me know which bits you want to know about first. Probably the most Pharo-specific part of the porting will be the new base image Collection subclasses. The VOSS Btree collections (VOLargeOrderedCollection and subclasses) are pretty well self-contained. I realise this morning that you weren't asking whether there was a non-VA implementation, you just meant is it available in chunk format, rather than VA library (.dat) format - yes it's attached hereto. But nevertheless, I strongly recommend having a working version to examine throughout the porting. The current version of VAST is 8.6.1, and VOSS 3.150.14 will object to that when you try to run it, expecting VA 8.6. I've looked at the VA86 to VA861 migration notes, and as far as I can see it's only the version checking code (in VODEVUUU module) which needs to be tweaked. I'll do that and upload to voss.logicarts.com Regards, John

8 9

Syslog client
by olivier auverlot March 31, 2015

March 31, 2015

Hi, I just released an UDP client for the Syslog network protocol (RFC5424). The product is available on SmalltalkHub. http://smalltalkhub.com/#!/~olivierauverlot/Syslog Best regards Olivier ;-)

4 3

GTSpotter with no results
by Christophe Demarey March 31, 2015

March 31, 2015

Hi, I would like to know if some of you already got this problem: when I open GTSpotter (with the shortcut) and I start to type quickly (before any result appears) in the text I'm searching for, I get no result at all. Even If I remove all characters from the search field, GTSpotter still presents an empty list. Thanks, Christophe.

6 6

Problem in creating new project on smalltalk hub
by rohit sharma March 31, 2015

March 31, 2015

hi all, when i am creating new project it is showing "*Oops! *Invalid username or password" , any suggestion? I am already login to my account and using web interface (http://smalltalkhub.com/#!/register) Regards Rohit

2 7

Pharo 4.0 / Roassal2
by Volkert March 30, 2015

March 30, 2015

Hi, can someone tell me, how to load Roassal2 into a Pharo4.0 Image? Or is it not a good idea with the current state of Pharo4.0? Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; configurationOf: 'Roassal2'; loadDevelopment loaded it, but it the examples do not work with playground. I also tried Gofer new smalltalkhubUser: 'Moose' project: 'Glamour'; package: 'ConfigurationOfGlamour'; load. (Smalltalk at: #ConfigurationOfGlamour) perform: #loadDevelopment to load it in the latest Image #40587, but it failed. I have absolutely no idea, what depends on what ... BW Volkert

2 2