May 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN] 5965 Can't allocate semaphores? VirtualMachine>>maxExternalSemaphores: aSize | Not enough space for external objects, set a larger size at startup!

by Igor Stasenko

On 23 May 2012 18:57, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > Hey guys, > > this is kind of a show stopper for images in production :/ > http://code.google.com/p/pharo/issues/detail?id=5965 > i thought we already dealt with it. no? > sebastian > > o/ > > > > > > -- Best regards, Igor Stasenko.

May 23, 2012

Re: [Pharo-project] Bug in Pharo-1.4-14438-OneClick.sh

by Damien Cassou

Hi, On Tue, May 22, 2012 at 9:56 PM, GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> wrote: > I attached my version of script. thank you very much. I updated http://code.google.com/p/pharo/issues/detail?id=5950. Thanks -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

May 23, 2012

Re: [Pharo-project] what is the magic with MCVersionInfo allInstances do: [ :each | each instVarNamed: 'ancestors' put: nil ]. ' ?

by Chris Muller

I don't know if your goal is to save space but... one of the nice things I've been enjoying about using a Magma-based MC repository is that the VersionInfo chain only goes back as far as you've actually accessed. Beyond that it's terminated by a Proxy object. It's the best of both worlds: the full version history is instantly and transparently available but without taking up any space until it's accessed.. On Mon, May 21, 2012 at 2:42 PM, Dale Henrichs <dhenrich(a)vmware.com> wrote: > The immediate impact of this is that you wont' be able to use the packages in your image in a three way merge, because the system will no longer be able to find a common ancestor. By implication you shouldn't save any of the packages either, because you risk polluting the "package pool" with ancestor-less versions. > > I've done a little experimentation with this in the git work (at one point in time, I was not saving the ancestry information on disk) ... > > If you somehow record the immediate ancestor(s) of the package, you can restore the ancestry chain with the MonticelloBrowser 'adopt' operation and then you can do the merge or save the package ... > > You can save and load these puppies ... I'm pretty sure that the ancestry is used only for merging ... > > oh yeah, the name of the package with the author and version number is derived from the first ancestor, i.e., the package that was loaded into the image, while this doesn't cause explicit problems, it can be unsettling ... > > At least that's what I recall.... > > Dale > > ----- Original Message ----- > | From: "Mariano Martinez Peck" <marianopeck(a)gmail.com> > | To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> > | Sent: Monday, May 21, 2012 10:58:23 AM > | Subject: [Pharo-project] what is the magic with MCVersionInfo allInstances do: [ :each | each instVarNamed: > | 'ancestors' put: nil ]. ' ? > | > | Hi guys. Can a MC guy tell me what happens when I do: > | > | MCVersionInfo allInstances do: [ :each | each instVarNamed: > | 'ancestors' put: nil ]. > | > | what is what is actually clean? is that useful? what are the > | consequences/impact when I do that? is my image broken? can I still > | use monticello browser and all my projects with it? > | > | thanks > | > | -- > | Mariano > | http://marianopeck.wordpress.com > | > | >

May 23, 2012

[Pharo-project] [ANN] 5965 Can't allocate semaphores? VirtualMachine>>maxExternalSemaphores: aSize | Not enough space for external objects, set a larger size at startup!

by Sebastian Sastre

Hey guys, this is kind of a show stopper for images in production :/ http://code.google.com/p/pharo/issues/detail?id=5965 sebastian o/

May 23, 2012

Re: [Pharo-project] Speed dating at PharoConf

by Esteban Lorenzano

mine On May 23, 2012, at 5:43 PM, Mariano Martinez Peck wrote: > Here is mine. > > On Wed, May 23, 2012 at 5:21 PM, Guillaume Larcheveque <guillaume.larcheveque(a)gmail.com> wrote: > one more > > Guillaume > > 2012/5/22 phil(a)highoctane.be <phil(a)highoctane.be> > > All right, all right... Here is one more :-) > > Phil > > 2012/5/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Hi guys > > We want to try a strange session during the Pharo Conf :) > We would like to organize a kind of speed dating so that we all know what we are doing. > > It would be cool if you could send me one slide about you. > Here is mine. > > > > > Stef > > > > > > -- > Philippe Back > "Helping you hit the top 3 outcomes you really want to achieve" > > Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be | Web: http://philippeback.eu | Blog: > http://philippeback.be > > High Octane SPRL > rue cour Boisacq 101 > 1301 Bierges > > > > > -- > Guillaume Larcheveque > > > > > > -- > Mariano > http://marianopeck.wordpress.com > > <AboutMarianoMartinezPeck.pdf>

May 23, 2012

Re: [Pharo-project] Posible bug

by Sean P. DeNigris

Igor Stasenko wrote > > because then it will be not from scratch. > of course i using image(s) vmmaker built by jenkins, where all stuff > already preloaded. > but it important bit of knowledge, which people should know how things > rolling. > Okay, I got it. Would it be a good compromise to point them to the Jenkins script that syncs the config with the current image? Is it LoadVMMaker.st? Maybe this (or whatever information you would need to compile from scratch that changes over time) could be added as an artifact to the Cog-VM on Jenkins (or as another job, like "Build VM from Scratch"). This way, anyone could go to the last successful build and see which versions of Pharo, ConfigurationOfXxx, git, etc. were used and get the same result. -- View this message in context: http://forum.world.st/Posible-bug-tp4631484p4631601.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 23, 2012

[Pharo-project] [Pharo-Conf] Meeting Lille center tomorrow morning 8:15â¦

by Marcus Denker

Hello, For those interested, we offer a meeting spot in the cetner of Lille tomorrow morning at 8:15 in front of Gare Lille Flanders to go together by Metro to Inria. Where? Gare Lille Flanders, main entrance, in front, by the fountain When? at 8:15 (so there is time to buy metro tickets) Marcus -- Marcus Denker -- http://marcusdenker.de

May 23, 2012

Re: [Pharo-project] Speed dating at PharoConf

by Mariano Martinez Peck

Here is mine. On Wed, May 23, 2012 at 5:21 PM, Guillaume Larcheveque < guillaume.larcheveque(a)gmail.com> wrote: > one more > > Guillaume > > 2012/5/22 phil(a)highoctane.be <phil(a)highoctane.be> > > All right, all right... Here is one more :-) >> >> Phil >> >> 2012/5/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> >>> Hi guys >>> >>> We want to try a strange session during the Pharo Conf :) >>> We would like to organize a kind of speed dating so that we all know >>> what we are doing. >>> >>> It would be cool if you could send me one slide about you. >>> Here is mine. >>> >>> >>> >>> >>> Stef >>> >>> >>> >> >> >> -- >> Philippe Back >> "Helping you hit the top 3 outcomes you really want to achieve" >> >> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: >> phil(a)highoctane.be | Web: http://philippeback.eu | Blog: >> http://philippeback.be >> >> High Octane SPRL >> rue cour Boisacq 101 >> 1301 Bierges >> >> > > > -- > *Guillaume Larcheveque* > > > -- Mariano http://marianopeck.wordpress.com

May 23, 2012

Re: [Pharo-project] Pressed Morph feedback on PharoTheme

by StÃ©phane Ducasse

> > It makes the default interaction a lot more reactive (i.e. you notice on screen when you are pressing on a button). Now with your change I do not understand why and when a button is becoming blue. > > Side note about UI changes in Nautilus: will there be any changes about the Groups/Hierarchy/Class/Comments buttons ? I have a hard time getting used to them (lack of selection/state clues, unusual behavior for buttons). Yes we all are saying that this is not working since we do not know if the state we are in. Stef

May 23, 2012

[Pharo-project] [update 2.0] #20093

by Marcus Denker

20093 ----- Issue 5963: remove empty package PluggableTextMorphWithLimits http://code.google.com/p/pharo/issues/detail?id=5963 Issue 5960: Failing tests: SourceFileArrayTest http://code.google.com/p/pharo/issues/detail?id=5960 -- Marcus Denker -- http://marcusdenker.de

May 23, 2012