September 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Getting Pharo 1.0 released

by Vicnet

Hello, > > Is "Pharo by Example" done ? > Yes :) I don't find PBE.image and actual image is not ok (SimpleSwitchMorph does't exist). I suppose that image will be build on official 1.0 so it is not ready. What should import on actual image (10440) to be able to do example ? I found PharoMorphicExtra on Pharo wiki that seems to be ok for PBE (except some linked lib) ? Is there anything else ? Thanks for PBE. a+ Vicnet -- View this message in context: http://n2.nabble.com/Getting-Pharo-1-0-released-tp3578354p3624877.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 11, 2009

[Pharo-project] BrowserEnvironment is broken?

by Oscar Nierstrasz

Hi Folks, In the latest pharo-web image (pharo1.0-10440-BETAweb09.09.1), the BrowserEnvironment is acting strangely: (BrowserEnvironment new forClasses: (Boolean withAllSubclasses)) selectMethods: [:method | method sendsToSuper ]; label: 'super sends'; open. This lists a whole bunch of methods that do *not* send super, including Boolean>>#&. If I check: (Boolean>>#&) sendsToSuper --> false So what is wrong? This worked ok back at the beginning of July ... - on

Sept. 11, 2009

Re: [Pharo-project] [Bulk] Re: Rio: binary mode copy not keep

by Vicnet

Hello, > "Directory home binary files first isBinary" return false > I think it should return true because base dir is binary. Is my assertion ok ? If Directory is in binary mode, should #files return File in binary mode too ? a+ Vicnet -- View this message in context: http://n2.nabble.com/Rio-binary-mode-copy-not-keep-tp3571512p3624825.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 11, 2009

Re: [Pharo-project] May be some problems with MC history

by StÃ©phane Ducasse

thanks lukas in general you did not get any problems? Beause I was careful and the changes seemed simple except the last one The result is that apparently I lost classes that were not in the changes! and instance variables. I'm now comparing with the squeak trunk image to see if this is an MC problem because this is the first time I got that strange behavior. Stef On Sep 11, 2009, at 9:09 AM, Lukas Renggli wrote: >> Does any (lukas) use the history feature to merge? > > Sometimes, if I would like to merge changes made in another branch. > Imagine the following situation: > > a.1 ---- wc (working copy) > \---- b.1 --- b.2 > > Now I want to include the changes that happened between b.2 and b.3, > but not those that were done between a.1 and b.1. I use the history > and to calculate a diff between b.1 and b.2 and selectively load the > changes. If the changes are separate from what happened between a.1 > and wc and a.1 and b.1 this should be relatively simple. Unfortunately > Monticello cannot figure out such dependencies, because it keeps the > ancestry on a package level only. In fact, with Monticello 2 an > operation like this should be smooth and automatic like a normal > merge. > >> I will retry to do the changes one by one and run the tests in >> between >> to see what went wrong >> but I 'm not sure that what is going wrong is the changes (I have the >> impression that may be MC history is not capturing >> exactly everything but I can be wrong). > > MC1 does not capture the ancestry of the individual methods, that's > why you have to extremely careful and check if you do not override > changes that were made between a.1 and wc and if you do not introduce > changes made between a.1 and b.1. I know this can be very tricky, > especially when there are many changes between a.1 and wc and a.1 and > b.1. MC2 promises rescue here. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 11, 2009

Re: [Pharo-project] one click distribution

by Damien Cassou

On Fri, Sep 11, 2009 at 10:42 AM, <astares(a)gmx.de> wrote: > http://gforge.inria.fr/frs/download.php/23114/Pharo1.0-10440-BETAdev09.09ON… > > now works on windows > > Any feedback from the other platforms? works perfectly on Linux -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Sept. 11, 2009

[Pharo-project] Pharo and SFC

by Torsten Bergmann

On goal of Squeak was/still is to become part of the Software Freedom Center. Dont know about the benefits but will/should Pharo work towards that goal too? Thx T. -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser

Sept. 11, 2009

[Pharo-project] one click distribution

by astares＠gmx.de

http://gforge.inria.fr/frs/download.php/23114/Pharo1.0-10440-BETAdev09.09ON… now works on windows Any feedback from the other platforms? Bye T. -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate fÃ¼r nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02

Sept. 11, 2009

Re: [Pharo-project] May be some problems with MC history

by Lukas Renggli

> Does any (lukas) use the history feature to merge? Sometimes, if I would like to merge changes made in another branch. Imagine the following situation: a.1 ---- wc (working copy) \---- b.1 --- b.2 Now I want to include the changes that happened between b.2 and b.3, but not those that were done between a.1 and b.1. I use the history and to calculate a diff between b.1 and b.2 and selectively load the changes. If the changes are separate from what happened between a.1 and wc and a.1 and b.1 this should be relatively simple. Unfortunately Monticello cannot figure out such dependencies, because it keeps the ancestry on a package level only. In fact, with Monticello 2 an operation like this should be smooth and automatic like a normal merge. > I will retry to do the changes one by one and run the tests in between > to see what went wrong > but I 'm not sure that what is going wrong is the changes (I have the > impression that may be MC history is not capturing > exactly everything but I can be wrong). MC1 does not capture the ancestry of the individual methods, that's why you have to extremely careful and check if you do not override changes that were made between a.1 and wc and if you do not introduce changes made between a.1 and b.1. I know this can be very tricky, especially when there are many changes between a.1 and wc and a.1 and b.1. MC2 promises rescue here. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Sept. 11, 2009

[Pharo-project] May be some problems with MC history

by StÃ©phane Ducasse

hi all yesterday I decided to have a look at MC changes in squeak to see if this has an impact for the closure last fixes merge. So I did with the latest scriptLoader in the pharo repository ScriptLoader new addExtraRepositories then I select each version of the monticello package in squeak trunk starting from 314 up to 321 and used the history and asked to get the delat with the previous version. This way I could get all the changes one by one. Now I ended up having - methods refering to instance variables that were not included (methodDefinitiosn for example with 321) - when I run the tests I realized that most of the Mock classes where gone. Except for 321 I do not see a change that could affect the MC merging. Does any (lukas) use the history feature to merge? I will retry to do the changes one by one and run the tests in between to see what went wrong but I 'm not sure that what is going wrong is the changes (I have the impression that may be MC history is not capturing exactly everything but I can be wrong). Stef

Sept. 11, 2009

Re: [Pharo-project] little tools support to better browse the squeaktrunk

by StÃ©phane Ducasse

ok I will check Stef On Sep 11, 2009, at 12:08 AM, Michael Roberts wrote: > Stef, i have added to PharoInbox > > Name: ScriptLoader-MikeRoberts.1054 > -Adds Squeak trunk convenience. > > no point doing it by hand? > > cheers, > Mike > > On Thu, Sep 10, 2009 at 8:01 PM, StÃ©phane > Ducasse<stephane.ducasse(a)inria.fr> wrote: >> Hi all >> >> to push the closure fixes I needed to browse the squeak trunk so I >> added >> >> ScriptLoader new addExtraRepositories >> >> so that all the packages get their 3.9a histories and that we can in >> one click browse the >> squeak repository. >> >> As a test I will integrate some fixes done on the MC browser and >> other >> MC related features. >> I will document that of course in our nice bugtracker. >> >> Stef >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 11, 2009