January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Newbie Confusion

by Serge Stinckwich

I think you have to wait a little bit, because right now Pharo 1.0 is not officially out and there is still some work on Pharo By Example to sync the book with the Pharo 1.0 image. 2010/1/22 Michael Litchard <michael(a)schmong.org>: > Just to let you know, I think the problems I've been experiencing > would scare away many newbies. I'm sticking around because I like > smalltalk and I think the pharo project is worth investing in. Here's > one I'm finding difficult to ignore. > I'm using the Pharo By Example book to learn smalltalk. No matter what > image I try I get the same problem. The O2 browser is not default, and > I cannot change my default. Following the instructions in the book > should result in getting a menu of options. I get nothing. The > learning process is dead in the water now. What image should I be > using? I trust future newbies won't be having to ask this question. > > > Michael Litchard. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

Jan. 22, 2010

Re: [Pharo-project] Problem with RB, code critics, Tests package and Traits

by Alexandre Bergel

Thanks Lukas, Alexandre On 21 Jan 2010, at 19:46, Lukas Renggli wrote: >> Can someone reproduce it ? > > Yeah, usually I can reproduce the easy ones: > > Name: Refactoring-Core-lr.101 > Author: lr > Time: 21 January 2010, 11:45:36 pm > UUID: b7212637-ccf6-448c-bfd0-e97f92af4b1a > Ancestors: Refactoring-Core-lr.100 > > - ignore traits in lint alltogether, their code is already checked > when checking the classes > > Lukas > > >> >> Cheers >> >> Mariano >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 22, 2010

[Pharo-project] Deadlock detection for testcases

by Stefan Marr

Hi: Have currently a lot of trouble with tests which are just deadlocking. Here is quick hack which specifies a timeout for test cases. Maybe it is useful for others, too. Any suggestions for improvement are welcome. Best Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525

Jan. 21, 2010

Re: [Pharo-project] [update] #10507

by Mariano Martinez Peck

On Thu, Jan 21, 2010 at 11:33 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > Great updated. I will build my images with this version from tonight on :-) > > Excellent. Tomorrow I build the PharoDev RC2 :) > Lukas > > 2010/1/21 Adrian Lienhard <adi(a)netstyle.ch>: > > 10507 > > ----- > > > > Issue 945: Annoying bug: UndefinedObject(Object)>>doesNotUnderstand: > #mimeTypes > > Issue 1769: TestRunner author while running tests > > Issue 1772: testSymbolTableM6812 is failing > > Issue 1815: Monticello prints class definitions to the transcript > while loading > > Issue 1841: Make the System -> Software update a preference for 1.0 > > Issue 1861: Use old network (note: to take effect you need to restart > the image) > > Issue 1771: testFinalizationOfEquals sometimes fails and sometimes > doesn't > > > > With this update, all pending 1.0 issues have been resolved and tests are > green. > > > > If no new issues pop up soon, we are going to declare this version as > RC2. > > > > Cheers, > > Adrian > > ___________________ > > http://www.adrian-lienhard.ch/ > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > 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 >

Jan. 21, 2010

Re: [Pharo-project] Problem with RB, code critics, Tests package and Traits

by Lukas Renggli

> Can someone reproduce it ? Yeah, usually I can reproduce the easy ones: Name: Refactoring-Core-lr.101 Author: lr Time: 21 January 2010, 11:45:36 pm UUID: b7212637-ccf6-448c-bfd0-e97f92af4b1a Ancestors: Refactoring-Core-lr.100 - ignore traits in lint alltogether, their code is already checked when checking the classes Lukas > > Cheers > > Mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 21, 2010

Re: [Pharo-project] [ANN 1.1] prebuilt Core#11177

by Alexandre Bergel

Just to inform you that building a dev from a core is easy and seems to work (I haven't intensively use the resulting image though). There are some deprecation raised in the refactoring. Cheers, Alexandre On 21 Jan 2010, at 18:12, Marcus Denker wrote: > http://gforge.inria.fr/frs/download.php/25338/PharoCore-1.1-11177-UNSTABLE.… > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 21, 2010

Re: [Pharo-project] [update] #10507

by Lukas Renggli

Great updated. I will build my images with this version from tonight on :-) Lukas 2010/1/21 Adrian Lienhard <adi(a)netstyle.ch>: > 10507 > ----- > > Issue 945: Â Â Â Annoying bug: UndefinedObject(Object)>>doesNotUnderstand: #mimeTypes > Issue 1769: Â Â TestRunner author while running tests > Issue 1772: Â Â testSymbolTableM6812 is failing > Issue 1815: Â Â Monticello prints class definitions to the transcript while loading > Issue 1841: Â Â Make the System -> Software update a preference for 1.0 > Issue 1861: Â Â Use old network (note: to take effect you need to restart the image) > Issue 1771: Â Â testFinalizationOfEquals sometimes fails and sometimes doesn't > > With this update, all pending 1.0 issues have been resolved and tests are green. > > If no new issues pop up soon, we are going to declare this version as RC2. > > Cheers, > Adrian > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 21, 2010

[Pharo-project] [update] #10507

by Adrian Lienhard

10507 ----- Issue 945: Annoying bug: UndefinedObject(Object)>>doesNotUnderstand: #mimeTypes Issue 1769: TestRunner author while running tests Issue 1772: testSymbolTableM6812 is failing Issue 1815: Monticello prints class definitions to the transcript while loading Issue 1841: Make the System -> Software update a preference for 1.0 Issue 1861: Use old network (note: to take effect you need to restart the image) Issue 1771: testFinalizationOfEquals sometimes fails and sometimes doesn't With this update, all pending 1.0 issues have been resolved and tests are green. If no new issues pop up soon, we are going to declare this version as RC2. Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/

Jan. 21, 2010

Re: [Pharo-project] O2: tester wanted!

by David RÃ¶thlisberger

> in my PharoCore-1.0-10505 image I had #testSmartGroupSwitch that failed and #testExtensionNodes and #testStyling that errored. ah, then probably I fixed the other test methods by fixing the undeclared references. Thanks, David > On Jan 21, 2010, at 16:09 , David RÃ¶thlisberger wrote: > >> Hi Adrian, >> >>> However, there are 6 undeclared classes referenced in the code. >> ok, I fixed these undeclared references. >> >>> Also 2 tests have errors and one fails. >> Which tests fail? I only got one error in a test which I fixed now. >> >> Cheers, >> David >> >> >>> On Jan 19, 2010, at 23:11 , Mariano Martinez Peck wrote: >>> >>>> On Tue, Jan 19, 2010 at 11:03 PM, Alexandre Bergel < >>>> alexandre.bergel(a)inria.fr> wrote: >>>> >>>>> Dear All, >>>>> >>>>> For people who do not know, O2 is the browser David has implemented in >>>>> the last few years. It replaces class-categories on the left-hand side >>>>> pane with a list of packages. We are still away from having packages >>>>> as real first class entities, but this is a good step toward. Note >>>>> that some people find O2 a bit slower than other available code >>>>> browsers. >>>>> >>>>> David and I spent some time on fixing O2. O2 has now no dependencies >>>>> to OB anymore. >>>>> We would like that people try it and submit bug reports on the google >>>>> bug tracker. In a fresh 10505, you can load O2 by evaluating: >>>>> >>>>> Gofer new squeaksource: 'MetacelloRepository'; package: >>>>> 'ConfigurationOfO2'; load. (Smalltalk at: #ConfigurationOfO2) perform: >>>>> #loadDefault >>>>> >>>>> >>>> Yes, but be aware that that piece of code load only the core, as you can see >>>> here: >>>> >>>> group: 'default' with: #('Core' ); >>>> group: 'Core' with: #( 'OmniBrowser2' 'O2-Standard' 'O2-Morphic' >>>> 'O2-Enhancements' ); >>>> group: 'Dev' with: #( 'Core' 'O2-Refactory' 'OCForO2' ); >>>> >>>> >>>> As I remember, most of the problems of O2 were sometimes related to the >>>> integration to RB. So, if you really want to tests it, please, test it using >>>> the RB: >>>> >>>> ((Smalltalk at: #ConfigurationOfO2) project version: '1.0') load: 'Dev' >>>> >>>> >>>> As I already said to Alexandre and David in private, I will put O2 again in >>>> the next image. So, it would be cool if it is tested "completely". >>>> >>>> >>>> >>>>> O2 does not need OB whatsoever. O2 loads in a Core (I tried in a >>>>> 11165). Before and after loading O2, running OB tests give "548 run, >>>>> 547 passes, 1 failures" [*]. >>>>> >>>>> >>>> Yes, if someone can help with that failure would be cool, I have already >>>> reported it. >>>> >>>> >>>> >>>>> Cheers, >>>>> Alexandre >>>>> >>>>> [*] the test have been loaded using (ConfigurationOfOmniBrowser >>>>> project version: '1.1') load: 'Dev Tests' >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >>> _______________________________________________ >>> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 21, 2010

[Pharo-project] Grrrrrrr the problem of always...... not finding a version when merging

by Mariano Martinez Peck

The other day, we were with stef doing some merge, and we were speaking about a recurrent problem. I don't undetstand completely the problem, maybe I am wrong. When merging with MC, it searches the complete history of the package. But, actually, I don't care. I just want the last one to merge....Ok, the problem is that if a version is not found. For example, now, I am trying to merge my slice about cleanup and fixes of ImageSegments, and I have this error when merging: "Error: Could not find version 'CompilerTests-MarcusDenker.24'. Maybe you need to add a repository?" I added http://www.squeaksource.com/PharoTreatedInbox but I got the same results. I attach PharoDebug. Any ideas how to fix this ? I cannot merge :( Should I open an issue ? Mariano

Jan. 21, 2010