April 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] squeaksource is down - a different perspective

by StÃ©phane Ducasse

On Apr 27, 2011, at 12:12 PM, Tudor Girba wrote: > Hi, > > squeaksource.com is down a lot. People get frustrated at times. The situation clearly needs rectification. > > But, here is the thing: I love it! It simply means that the future that seemed to work just fine only a couple of years ago was long overpassed. This is phenomenal growth. > > And I can afford to love it because the promise of SmalltalkHub is right around the corner. That is so great. I am looking forward to move to it, and then I will be looking forward to getting it on its knees in a couple of years :). yes I like the metaphor. Killed by success. Stef > > Cheers, > Doru > > -- > www.tudorgirba.com > > "To lead is not to demand things, it is to make them happen." > > > >

April 27, 2011

Re: [Pharo-project] [ANN] PharoDev-1.3-13173

by Philippe Marschall

On 27.04.2011 18:41, Sven Van Caekenberghe wrote: > > On 27 Apr 2011, at 18:27, Philippe Marschall wrote: > >> - ZnServer class >> #initialize references AutoStart > > Zn is not a standard part of this image, so it must have come with Seaside ? Yeah, I built from Core and ran some of the functional tests with: - AJP - Comanche Light - Swazoo - Zinc and found a bug in Zinc :-P Cheers Philippe

April 27, 2011

Re: [Pharo-project] GitFs / MCGit

by Max Leske

Concerning 2: No, it doesn't make sense at all to return nil. The reason that no exception is signalled is simply that that case should never be possible (not really an argument, I know :D). The method #packedObjectWithSignature is only sent if no loose object could be found. Then the packs are scanned and if the object isn't found in the packs the method returns nil. I think an exception would make a lot of sense but I didn't implement an exception handling mechanism for FSGit so a user will get slapped in the face with a debugger. Better though than having to track down that nil bug... On 27.04.2011, at 16:21, Camillo Bruni wrote: > Hi Max, > > I took another effort to work on the git bindings of MC. > However I ran into troubles with FSGitFilesystem on commiting. > > 1. I fail when saving the repos in GitCommit >> parents when it starts to lazily load the object which does not exist yet... > > 2. GitRespository >> packedObjectWithSignature: aGitObjectSignature > does not throw an exception but simply returns nil? does this make sense? > > > maybe you have a clue how to solve this faster than I do :-) > > camillo

April 27, 2011

Re: [Pharo-project] GitFs / MCGit

by Max Leske

Can you send me the stack traces? On 27.04.2011, at 16:21, Camillo Bruni wrote: > Hi Max, > > I took another effort to work on the git bindings of MC. > However I ran into troubles with FSGitFilesystem on commiting. > > 1. I fail when saving the repos in GitCommit >> parents when it starts to lazily load the object which does not exist yet... > > 2. GitRespository >> packedObjectWithSignature: aGitObjectSignature > does not throw an exception but simply returns nil? does this make sense? > > > maybe you have a clue how to solve this faster than I do :-) > > camillo

April 27, 2011

Re: [Pharo-project] SqueakSource

by Fabrizio Perin

Hi Markus, don't worry about that i managed it already 2011/4/27 Marcus Denker <marcus.denker(a)inria.fr> > > On Apr 27, 2011, at 1:03 PM, Philippe Marschall wrote: > > > On 04/27/2011 12:08 PM, Fabrizio Perin wrote: > >> Ok Squeaksource is up again. I did run a script that should load the > >> missing commits if they have been store on the disk. Please check if > >> they are there otherwise you just have to commit them again. > > > > The SeasideWip repository seems to be gone. If it can't be recovered can > > you send me the *.mcz files (AFAIK they're saved on disk) and I'll > > recreate it. > > > I will send them to you (later today) > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > >

April 27, 2011

Re: [Pharo-project] [ANN] PharoDev-1.3-13173

by Mariano Martinez Peck

On Wed, Apr 27, 2011 at 6:41 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > > On 27 Apr 2011, at 18:27, Philippe Marschall wrote: > > > - ZnServer class >> #initialize references AutoStart > > Zn is not a standard part of this image, so it must have come with Seaside > ? > If so, that would be cool, that is something that I want ! > > Anyway, > > ZnServer class>>initialize > Smalltalk addToStartUpList: self after: AutoStart. > Normally, Smalltalk addToStartUpList: self is enought. The #addToStartUpList:after: is ONLY when you depend on someone else starting first, which is not normally the case, Hence being at the end is fine. I don't know Zinc needs, thus. > Smalltalk addToShutDownList: self > > Indeed AutoStart seems to be gone. > I just picked that code up somewhere, what should it have to be then ? > > Apart from that loading error, all Zn tests are green. > > Thx, > > Sven > > > -- Mariano http://marianopeck.wordpress.com

April 27, 2011

Re: [Pharo-project] [ANN] PharoDev-1.3-13173

by Sven Van Caekenberghe

On 27 Apr 2011, at 18:27, Philippe Marschall wrote: > - ZnServer class >> #initialize references AutoStart Zn is not a standard part of this image, so it must have come with Seaside ? If so, that would be cool, that is something that I want ! Anyway, ZnServer class>>initialize Smalltalk addToStartUpList: self after: AutoStart. Smalltalk addToShutDownList: self Indeed AutoStart seems to be gone. I just picked that code up somewhere, what should it have to be then ? Apart from that loading error, all Zn tests are green. Thx, Sven

April 27, 2011

Re: [Pharo-project] new Cog VMs uploaded

by Philippe Marschall

On 26.04.2011 23:01, Eliot Miranda wrote: > ...to http://www.mirandabanda.org/files/Cog/VM/VM.r2379/. These fix > shallowCopy and copyFrom: for contexts and (I hope) fix the linux Locale > plugin. I'm seeing quite a drastic performance degradation in the last two Cog releases for Seaside. r2361 and r2370 would yield about 4300 to 4400 "points" for /tests/functional/WAPerformanceFunctionalTest. r2378 and r2380 are down to about 2600 to 2700. That's almost a third slower. Cheers Philippe

April 27, 2011

Re: [Pharo-project] [ANN] PharoDev-1.3-13173

by Marcus Denker

On Apr 27, 2011, at 6:27 PM, Philippe Marschall wrote: > > - OBDefinition >> #doItReceiver references FakeClassPool > This can not be. I added FakeClassPool back to the Deprecated13 package some updates ago. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 27, 2011

[Pharo-project] ConfigurationOfMagma with support for Magma 1.2 and symbolic versions

by Miguel CobÃ¡

Hi all, I'm glad to announce a new version of ConfigurationOfMagma with support for Magma 1.2. This configuration has been tested on PharoCore 1.1.x PharoCore 1.2.x Thank you very much to Chris Muller who, as always, is working hard to keep Magma running on Squeak and Pharo. I used the same versions of packages he used in his scripts for Squeak in order to update the configuration. You must download the latest PharoCore image or update a existing one before installing Magma, as Magma needs some changes that were applied to Pharo post-release and are available in the update stream. Pharo 1.1.x ------------ Download PharoCore 1.1.2 from: https://gforge.inria.fr/frs/download.php/28341/PharoCore-1.1.2.zip Update it if necessary and save it. Pharo 1.2.x ------------ You have two options: 1. Take a released 1.2.1 from: http://www.pharo-project.org/pharo-download/stable-core This is actually image update 12345. Evaluate: SystemVersion newVersion: 'Pharo1.2.2a'. update the image (it will update to 12350, at this time) and save it. 2. Take a snapshot of the upcoming 1.2.2 release of Pharo 1.2.x line from: https://gforge.inria.fr/frs/download.php/28436/PharoCore-1.2.2a-12345.zip update the image (it will update to 12350, at this time) and save it. Install Magma -------------- Ok, now you have an updated image. Load the configuration by evaluating: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMagma'; load. And depending on which of client, server or the full suite of Magma do you want, evaluate: - Magma client ((Smalltalk at: #ConfigurationOfMagma) project version: #stable) load: 'Client'. - Magma server ((Smalltalk at: #ConfigurationOfMagma) project version: #stable) load: 'Server'. - Magma tester ((Smalltalk at: #ConfigurationOfMagma) project version: #stable) load: 'Tester'. For example, to load the full magma suite evaluate: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMagma'; load. ((Smalltalk at: #ConfigurationOfMagma) project version: #stable) load: 'Tester'. This will load client, server and test of Magma. Running tests ------------- To run the tests evaluate: MagmaTestCase allowWriteBarrier: false. MagmaTestCase fullSuite maDebug. Stable versions --------------- This release of ConfigurationOfMagma includes support for Metacello's symbolic versions. Currently the #stable version of Magma is configured like this: Pharo version #stable version ------------- --------------- Pharo 1.1.x 1.2 Pharo 1.2.x 1.2 Pharo 1.3.x 1.2 That is, Magma 1.2 is the #stable version for Pharo 1.1, Pharo 1.2 and Pharo 1.3. Known issues -------------- Magma 1.2 loads correctly and appears to work for the basic things (create a repo, add data, commit, etc) in PharoCore 1.3 and Pharo 1.3, but the full suite hasn't ran correctly in the current unstable Pharo. So use Magma 1.2 on Pharo 1.3 on your own risk and not for production yet. When the issues (including the Transcript revert that should happen in Pharo soon) are addressed, a new announce will be made for Magma on Pharo 1.3 Any feedback welcome. Enjoy. -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

April 27, 2011