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

[Pharo-project] Fwd: 1.1.2 post production fixes from netstyle
by StÃ©phane Ducasse Feb. 4, 2011

Feb. 4, 2011

Begin forwarded message: > From: Adrian Lienhard <alienhard(a)netstyle.ch> > Date: February 4, 2011 10:35:24 AM GMT+01:00 > To: Marcus Denker <marcus.denker(a)inria.fr> > Cc: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: 1.1.2 > > The fixes we add to 1.1.1 are: > > * http://code.google.com/p/pharo/issues/detail?id=2750 > This is important for image segments. Apart from that we use a plain 1.1.1 image stripped with #cleanUpForProduction. > > * http://code.google.com/p/pharo/issues/detail?id=3498 > This is the fix for the concurrency issue in linked list that kills your image. I would certainly add this one to 1.1.2 > > * http://code.google.com/p/pharo/issues/detail?id=3542 > This one is "Add SmalltalkImage>>#gcBiasToGrow: and friends to core". It is not critical, but we use it to be able to modify the two additional GC params. > > * lastly we removed the duplicated methods from a trait in Behavior to make Lint tests pass (I think I posted that but I can't find it in the tracker right now). See attachement. > > > Cheers, > Adrian > > > __________________________ > www.adrian-lienhard.ch > twitter.com/adrianlienhard >

1 0

[Pharo-project] Hudson build for Seaside too?
by Torsten Bergmann Feb. 4, 2011

Feb. 4, 2011

>I was trying to load the latestVersion of ConfigurationOfSeaside3 into the >latest PharoCore 1.2 No, this wont work. The default config should be used only on Pharo-dev since it loads tests, tools, ... Loading Seaside on Pharo Core makes only sense for deployment and then you have to pick the pieces from the config that you need. You can do this with the #load: method on the config and given the groups you need: (ConfigurationOfSeaside30 project version: '3.0.3') load: { 'Grease Core' } for instance loads only Grease. >Is there a place to get the script that turns PharoCore 1.2 into >Pharo 1.2 ? Pharo 1.2 is always built by using (guess what, tadaaa): the "ConfigurationOfPharo" So from PharoCore 1.2 to PharoDev 1.2: ------------------------------------------------------------------- Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load. ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) load ------------------------------------------------------------------- The last version is currently "1.2-beta2", just look into the ConfigurationOfPharo class. The build script "Pharo-1.2.st" that the Hudson server is using is available at: http://lists.gforge.inria.fr/pipermail/pharo-project/attachments/20110203/8… It first updates the core and does some other "magic". You can just file this into a recent 1.2 core and your machine is the build server :) Take care when you use it - it automatically saves when finished and therefore overwrites the core image used. Bye T -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

2 1

[Pharo-project] Issue 3635 in pharo: [Hudson] reuse images downstream
by pharo＠googlecode.com Feb. 4, 2011

Feb. 4, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com New issue 3635 by marcus.d...(a)gmail.com: [Hudson] reuse images downstream http://code.google.com/p/pharo/issues/detail?id=3635 Pharo Full should use the image created by Pharo core. Normally this should work, but it did not. Maybe because we use a build slave?

1 3

[Pharo-project] Hudson build for Seaside too?
by Torsten Bergmann Feb. 4, 2011

Feb. 4, 2011

Sven wrote: >For the last couple of weeks, and again this evening I wanted to start using >1.2 as my main image, but that requires Seaside 3, the above still does not >work for me: Hi Sven, works for me without a problem. I work in latest pharo-dev 1.2 with Seaside 3.0.3 loaded. Can run JqueryWidgetBox and MetaSource for example without any problem, just bootstrapped today using the configs. There are some red tests due to the fact that Seaside uses Preferences in some packages and these are thrown out in Pharo 1.2. Maybe your image is outdated. Did you try one of the prebuilt clean pharo 1.2 images from the hudson server http://ci.pharo-project.org ? Try the one from the latest working build from today (see [1]) and download the image (direct url to the ZIP is [2]). Make sure you start in a new directory (or at least rename the package-cache folder). Then run the following expressions: DEVImageWorkspaces openExternalProjectWorkspace In this workspace run the first script Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load. ((Smalltalk at: #ConfigurationOfSeaside30) project latestVersion) load. Tell me if this works for you. Bye T. [1] https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/116/ [2] https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/116/artif… -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl

2 2

[Pharo-project] Tools->Configuration browser fails with DNU in Pharo1.3
by Igor Stasenko Feb. 4, 2011

Feb. 4, 2011

subject. -- Best regards, Igor Stasenko AKA sig.

1 0

Re: [Pharo-project] Oh, great.. SqS is down
by Marcus Denker Feb. 4, 2011

Feb. 4, 2011

On Feb 3, 2011, at 8:38 PM, Andre Hora wrote: > Hello Marcus, > > A project that I created this week in SqS is missing from the repository too. Moreover, a project that I deleted in the begin of the week in now back to my account... > What a shit. I don't know what to do. Now I even managed to close the workspace window in that SqueakSource image (via VNC, very slow... shit happens). So I first will restore that. Then I will see. But I fear that the image did not get saved... (I *hate* image based persitency for servers... it just stops to save and nobody tells you, so there is no way to react). We need to replace squeaksource soon, this is really sucking too much energy like that. > On Thu, Feb 3, 2011 at 8:26 PM, Carla F. Griggio <carla.griggio(a)gmail.com> wrote: > I've just recieved a mail informing that there was a commit in one of my projects :P That commit was done last week (24/01). > > > On Thu, Feb 3, 2011 at 4:23 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Feb 3, 2011, at 7:57 PM, Tudor Girba wrote: > > > Hi, > > > > It looks like there was a problem: all commits I published over the past couple of days in moose and glamour are now missing from the repository. I did not check other one projects yet. Could there have been a mistake when restarting or are these lost? > > > I imported all lost versions... can you check? > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > > > > > -- > Andre Hora > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

4 5

[Pharo-project] Promoting/popularizing OB
by Igor Stasenko Feb. 4, 2011

Feb. 4, 2011

Hi, just a comment. It would be good to make a screencast(s), which showing the benefits of using OB comparing to standard browser, i.e. you doing some operation in standard browser (like moving ivar from one class to another, or splitting class on two classes, or other refactorings), and then doing the same in OB. So, people will know - the benefits - what they losing (time) by not using advanced tools There is no need to demonstrate an advanced & complex operations, just those which people using most often, when coding. -- Best regards, Igor Stasenko AKA sig.

1 0

[Pharo-project] Issue 3470 in pharo: [Failing Tests] OBKeyBindingsTest
by pharo＠googlecode.com Feb. 4, 2011

Feb. 4, 2011

Status: Accepted Owner: marcus.denker Labels: Milestone-1.3 New issue 3470 by marcus.denker: [Failing Tests] OBKeyBindingsTest http://code.google.com/p/pharo/issues/detail?id=3470 >>> OB.Tests.Morphic.OBKeyBindingsTest.testBrowseIt 0.339 13 >>> OB.Tests.Morphic.OBKeyBindingsTest.testImplementorsOfIt 0.387 13 >>> OB.Tests.Morphic.OBKeyBindingsTest.testReferencesToIt 0.254 13 >>> OB.Tests.Morphic.OBKeyBindingsTest.testSendersOfIt 0.273 13

1 11

[Pharo-project] Issue 3650 in pharo: PluggableShoutMorph not present in latest build of Pharo1.2
by pharo＠googlecode.com Feb. 4, 2011

Feb. 4, 2011

Status: New Owner: ---- New issue 3650 by tulipe.m...(a)gmail.com: PluggableShoutMorph not present in latest build of Pharo1.2 http://code.google.com/p/pharo/issues/detail?id=3650 Pharo image: Pharo1.2rc2 Pharo core version: #12330 Virtual machine used: Cog3.0.0 mac Steps to reproduce: 1. Download latest build from Hudson 2. Open the image 3. Do it on "ProfStef go" in the welcom workspace 4. DNU It seems that the PluggableShoutMorph is not there.

1 3

[Pharo-project] Issue 3603 in pharo: O/ECompletion failure in Trait methods
by pharo＠googlecode.com Feb. 4, 2011

Feb. 4, 2011

Status: Accepted Owner: ryd...(a)gmail.com CC: romain.r...(a)gmail.com Labels: Milestone-1.2-DevImage Milestone-1.3-DevImage OCompletion New issue 3603 by ryd...(a)gmail.com: O/ECompletion failure in Trait methods http://code.google.com/p/pharo/issues/detail?id=3603 A debugger pops up when typing in after super in a trait method, since traits do not implement superclass. Reproduction steps at: http://screencast.com/t/yyjLLm0S Mailing list thread: http://forum.world.st/First-commit-to-Pharoinbox-Need-advice-tp3237535p3241…

3 8