- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3341 in pharo: use #= for integer comparison instead of #==

by pharo＠googlecode.com

Comment #6 on issue 3341 by stephane...(a)gmail.com: use #= for integer comparison instead of #== http://code.google.com/p/pharo/issues/detail?id=3341 Thanks this is nice to see some progress on this front too. We will get there.

March 26, 2011

[Pharo-project] who is using softSqueak and standard Squeak

by StÃ©phane Ducasse

Hi guys just out of curiosity who is using SoftSqueak and Standard Squeak theme? I know that lukas like colored windows now may be specific new style with this behavior could be done? Stef

March 26, 2011

Re: [Pharo-project] Issue 3864 in pharo: [Failing Test] 1.3 ImageSegmentTestExport

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3864 by stephane...(a)gmail.com: [Failing Test] 1.3 ImageSegmentTestExport http://code.google.com/p/pharo/issues/detail?id=3864 in 13112

March 26, 2011

Re: [Pharo-project] Issue 2704 in pharo: Tests for broken withNoLineLongerThan: behavior.

by pharo＠googlecode.com

Updates: Status: Closed Labels: Milestone-1.3 Comment #10 on issue 2704 by stephane...(a)gmail.com: Tests for broken withNoLineLongerThan: behavior. http://code.google.com/p/pharo/issues/detail?id=2704 Thanks a lot. We have not much time for looking at these enhancements but there are still nice to have. So thanks Integrated in 13112

March 26, 2011

[Pharo-project] COG VM Locale?

by Hilaire Fernandes

Is it likely it'll be fixed? If so when? I need to know so I can move to plan B if necessary. http://code.google.com/p/cog/issues/detail?id=1 Hilaire -- Education 0.2 -- http://blog.ofset.org/hilaire

March 26, 2011

Re: [Pharo-project] "Does Committing Code to an Open Source Project Mean Committing Career Suicide?"

by csrabak＠bol.com.br

Craig, IANALÂ but the reading of the section 2897 (1) and (2) seem to me exactly the cases the site is bringing on, and being so harder to discern in cases of SW development than other 'hard' stuff, like say kid toy inventions versus working in a factory that builds industrial furnaces. -- Cesar Rabak Em 25/03/2011 06:00, Craig Latta < craig(a)netjam.org > escreveu: Wow. The stuff in there about California law is simply false. See the California labor code, sections 2870-2872 (e.g., at [1]). -C [1] http://law.justia.com/codes/california/2009/lab/2870-2872.html -- Craig Latta www.netjam.org/resume +31 06 2757 7177 + 1 415 287 3547

March 25, 2011

Re: [Pharo-project] Pharo 1.2 red again

by Dale Henrichs

On Mar 25, 2011, at 3:29 PM, Tudor Girba wrote: > Sounds great. So, what needs to be done then? That depends upon what you are trying to do...For GemStone I have a class called GLASSProjectSupport that does the following: 1. fetches all mczs and configurations for ConfigurationOfGLASS into an in-memory dictionary-based repository 2. copies new mcz files (packages and configs) into a directory in an svn checkout directory, recording the original repository from which the package was downloaded 3. updates a packing list file so that the new mcz files are automatically copied into the correct directory for release 4. generates a topaz script that is used to bootstrap GLASS from the svn directory and the repository map is used to set the repositoryGroup correctly (as if the mcz files weren't loaded from the svn directory). The basic script for doing step 1 is here: http://code.google.com/p/metacello/wiki/FAQ#How_do_I_create_a_local_cache_r… although you would probably want to set ignoreImage: to true: version ignoreImage: true. There's a little bit more monkey business if you want to store your project configuration (like ConfigurationOfGLASS) in your archive directory. If you want to record the original repositories or get your hands on the list of mcz files/configs that were loaded, then it gets a little more complicated: loadDirective := version fetch loadDirective You can traverse the loadDirective and extract the additional information you might want ... If you are going to load using Metacello then a script for step 4 is here: http://code.google.com/p/metacello/wiki/FAQ#How_do_I_override_the_repositor… I have toyed with the idea of creating something like a .mar file which would essentially encapsulate the above into a couple of steps: - one for create the .mar file - one for loading from the .mar file The .mar file would be a zipped up directory repository plus some sort of doit that would provide the load instructions/options....for a .mar file it might be worth restoring the repositoryGroups for the mcz files, which means recording a repository map... I haven't looked closely at the .sar file stuff, but maybe the .mar file could be wrapped in a .sar so that other deliverables could be included ... and a .mar file would just be a special case of a .sar file? I am partial to the .mar file idea and I don't think there's that much new that would have to be invented, but I haven't thought through all of the issues yet ... but now might be a good time to encapsulate the whole process and tie it up with a bow:) Dale

March 25, 2011

Re: [Pharo-project] Pharo 1.2 red again

by Tudor Girba

Sounds great. So, what needs to be done then? I would be interested to use this in the context of Moose as well. Cheers, Doru On 24 Mar 2011, at 21:36, StÃ©phane Ducasse wrote: > this is a good news > > Stef > > On Mar 24, 2011, at 4:59 PM, Dale Henrichs wrote: > >> Stef, >> >> Yep ... all the pieces are there ... it's just a matter of putting them together in the right order..this is what we do for GemStone GLASS builds... >> >> Dale >> >> On Mar 24, 2011, at 1:21 AM, StÃ©phane Ducasse wrote: >> >>> henrichs >>> >>> do you know if you have now the pieces in place to be able to freeze a configuration and all its recursive sets in a dedicated repository? >>> >>> Stef >> >> > > -- www.tudorgirba.com "Every successful trip needs a suitable vehicle."

March 25, 2011

Re: [Pharo-project] Issue 2704 in pharo: Tests for broken withNoLineLongerThan: behavior.

by pharo＠googlecode.com

Comment #9 on issue 2704 by nicolas....(a)gmail.com: Tests for broken withNoLineLongerThan: behavior. http://code.google.com/p/pharo/issues/detail?id=2704 SLICE-Issue-2704-String-withNoLineLongerThan-nice.1 contains fresh Squeak test and fix. Pocho, you can correct the alternative if you want, but this method is damned tricky (I broke some teeth on it).

March 25, 2011

Re: [Pharo-project] Issue 2704 in pharo: Tests for broken withNoLineLongerThan: behavior.

by pharo＠googlecode.com

Comment #8 on issue 2704 by nicolas....(a)gmail.com: Tests for broken withNoLineLongerThan: behavior. http://code.google.com/p/pharo/issues/detail?id=2704 No, both methods fails with this test: String crlf withNoLineLongerThan: 5. Also, does your version works when there is no space available near ? 'ThisMightBe tooLong' withNoLineLongerThan: 5.

March 25, 2011