- Pharo-dev - lists.pharo.org

[Pharo-project] [COTDC] MCFileRepositoryInspector
by laurent laffont Feb. 5, 2011

Feb. 5, 2011

** 1st Comment Of The Day Contest - One Day One Comment ** Rules: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). The first round is for: MCFileRepositoryInspector GO GO !! Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

3 8

Re: [Pharo-project] Issue 3154 in pharo: FSMemoryFileSystem does not store timestamps
by pharo＠googlecode.com Feb. 5, 2011

Feb. 5, 2011

Comment #2 on issue 3154 by damien.p...@gmail.com: FSMemoryFileSystem does not store timestamps http://code.google.com/p/pharo/issues/detail?id=3154 Work in progress in PharoTaskForces. Previously existing tests are green but the new functionality is not explicitly tested yet.

1 0

[Pharo-project] [ANN] New article on using callbacks in Reef
by Esteban Lorenzano Feb. 5, 2011

Feb. 5, 2011

Hi, I just published an article on using callbacks in Reef framework. You can read it here: http://smallworks.com.ar/en/community/Reef/reefSimpleTutorialPart2 I know, it is very delayed with my latest promises, but there are a "deadline collision" with this and Reef documentation it's coming out as soon as possible :) well... enjoy and any observation is really well-welcome. best, Esteban

2 1

[Pharo-project] [update 1.1] #11419
by Marcus Denker Feb. 5, 2011

Feb. 5, 2011

Part 1 of fixes used at Netstyle for deployment of CMSBOX with 1.1.1 11419 ----- Issue 2750: Loading an image segment can introduce a class named AnObsoleteFake37SomeName Issue 3498: remove:ifAbsent: in linked list leads to interruption/sync problems -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] Issue 3498 in pharo: remove:ifAbsent: in linked list leads to interruption/sync problems
by pharo＠googlecode.com Feb. 5, 2011

Feb. 5, 2011

Status: Accepted Owner: stephane.ducasse New issue 3498 by stephane.ducasse: remove:ifAbsent: in linked list leads to interruption/sync problems http://code.google.com/p/pharo/issues/detail?id=3498 If you fill an issue for the first time, please read "How to report bugs" at http://www.pharo-project.org/community/issue-tracking Pharo image: <core, dev or web> Pharo core version: <copy from World/System/About> Virtual machine used: <ex: pharo-vm-0.15.2f-linux> Class browser used if applicable: <ex: O2PackageBrowserAdaptor. If you don't know, print "SystemBrowser default"> Steps to reproduce: 1. 2. 3. Paste or attach stack trace if applicable (look at the file PharoDebug.log located in the same directory as your image):

3 17

Re: [Pharo-project] Issue 2750 in pharo: Loading an image segment can introduce a class named AnObsoleteFake37SomeName
by pharo＠googlecode.com Feb. 5, 2011

Feb. 5, 2011

Comment #6 on issue 2750 by marcus.d...@gmail.com: Loading an image segment can introduce a class named AnObsoleteFake37SomeName http://code.google.com/p/pharo/issues/detail?id=2750 added to 11419

1 1

Re: [Pharo-project] Which ConfigurationOfPharo should use in Pharo 1.2 ?
by Marcus Denker Feb. 5, 2011

Feb. 5, 2011

On Feb 5, 2011, at 9:53 AM, Sven Van Caekenberghe wrote: > > On 05 Feb 2011, at 08:31, Marcus Denker wrote: > >> I attach the complete script used for building 1.2 as the builder.sh stiches it together: >> >> >> <Pharo-1.2.st> > > It would be really cool if this were an artifact as well, so that those interested in certain builds can see exactly how they were produced. > > Ok, I will do that. > PS: the things you are doing with the CI server are really coola ans useful. > All praise should go to Lukas for https://github.com/renggli/builder which makes all this very trivial... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] [Ocean] Simple client Tcp socket
by Noury Bouraqadi Feb. 5, 2011

Feb. 5, 2011

Hi, Jannik asked for an example. I thought that it might interest others to test. So far, it does work only on Mac OS. 1) In a command line terminal evaluate the following echo "Hello from NetCat" | nc -l 1234 2) Then in a workspace evaluate this code. serverAddress := OCNIPV4SocketAddress loopbackAddressWithPort: 1234. socket := OCNTcpSocket new. socket isConnected. "---> false" socket connectToServer: serverAddress. socket isConnected. "---> true" socket send: 'Hello from Pharo'. Transcript cr; show: socket receive. socket destroy. socket isConnected. "---> false" That's all for now, Noury

1 0

Re: [Pharo-project] Which ConfigurationOfPharo should use in Pharo 1.2 ?
by Marcus Denker Feb. 5, 2011

Feb. 5, 2011

On Feb 5, 2011, at 12:16 AM, GermÃ¡n Arduino wrote: > Sorry I should have written: "Marcus", sorry. > I attach the complete script used for building 1.2 as the builder.sh stiches it together: > 2011/2/4 GermÃ¡n Arduino <garduino(a)gmail.com>: >> Thanks by the explanations Dale. >> >> Thanks Guillermo and Markus by the points. >> >> Until moment any way of installation I tried failed with different >> sort of messages. >> >> By now I downloaded the ready image pointed by Markus but would like >> to build my own. >> >> Thanks! >> >> >> 2011/2/4 Dale Henrichs <dhenrich(a)vmware.com>: >>> Sure: >>> >>> http://gemstonesoup.wordpress.com/2011/01/17/metacello-1-0-beta-28-unearthe… >>> >>> Be sure to look at the section of development cycle ... and tools support, too... >>> >>> Dale >>> >>> On Feb 4, 2011, at 6:37 AM, Guillermo Polito wrote: >>> >>> Dale, Is there a place where I can read how to configure the symbolic versions? >>> >>> Thx! >>> Guille :) >>> >>> On Fri, Feb 4, 2011 at 11:29 AM, Dale Henrichs <dhenrich(a)vmware.com<mailto:dhenrich@vmware.com>> wrote: >>> ConfigurationOfPharo should have a #stable symbolic version defined that specifies the version that should be used in 1.2, 1.1, and 1.0 ... then one just loads the #stable version: >>> >>> (ConfigurationOfPharo project version: #stable) load >>> >>> and you'll get the right version loaded for the platform version ... even though the version is under development I think it is valid to specify a #stable symbolic version for Pharo1.2, just so folks don't have to ask this question over and over again ... Don't let the name 'stable' scare you ... >>> >>> The intent is that the #stable symbolic version specifies the version that should be loaded .... the developer decides which versions are #stable for each platform version and when a new version becomes "the version to use" the developer updates the specification. >>> >>> The users of a configuration shouldn't have to think ... remember in the past the recommended pattern was: >>> >>> ConfigurationOfPharo project latestVersion load >>> >>> and that worked fine until Pharo1.1 and Pharo1.2 were introduced. The expression: >>> >>> (ConfigurationOfPharo project version: #stable) load >>> >>> is intended to replace the use of #latestVersion because it makes it possible to explicitly specify the "latest version" on a platform by platform and platform version basis... >>> >>> Sorry if I appear to be ranting ... I'm just trying to get the message out:) >>> >>> Dale >>> >>> On Feb 4, 2011, at 6:01 AM, Guillermo Polito wrote: >>> >>> I'm Using '1.2-beta2'. >>> >>> Should we remove invalid and unused versions? I'll add a few comments at lunch time ;) >>> >>> On Fri, Feb 4, 2011 at 10:53 AM, GermÃ¡n Arduino <garduino(a)gmail.com<mailto:garduino@gmail.com><mailto:garduino@gmail.com<mailto:garduino@gmail.com>>> wrote: >>> I tried the 2 latest Beta and fail, also the 1.1 version fail. >>> >>> Which ConfigurationOfPharo I should use with Pharo 1.2 ? >>> >>> Cheers. >>> >>> >>> >>> >>> >>> >>> >>> >> >> >> >> -- >> ================================================= >> GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: garduino >> Arduino Software & Web Hosting http://www.arduinosoftware.com >> PasswordsPro http://www.passwordspro.com >> ================================================= >> > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 2

[Pharo-project] different vmFullPath between MacVM
by Luc Fabresse Feb. 5, 2011

Feb. 5, 2011

Hi All, SmalltalkImage current vmFullPath evaluates to: '/Applications/SmalltalkVMs' with the MacVM 5.7.4 (the directory that contains the .app vm application) '/Applications/SmalltalkVMs/Squeak-4.2.5beta1U.app/Contents/MacOS/Squeak VM Opt' with the MacVM 4.2.5b1 (the exec file) Is this difference known? I found nothing on the mailing lists. Is it a bug? it is to know we should adapt Coral or not. Cheers, #Luc

1 0