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

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Mariano Martinez Peck

This is weird...we have several tests failing, erroring, successing in different OS. Someone has already reported in windows, Laurent in Linux, and here is in mac. Can someone please put all the information together so that we know which tests are failing and in which OS. Cheers Mariano 2010/1/22 laurent laffont <laurent.laffont(a)gmail.com> > On Linux, exupery VM > > Laurent > > 2010/1/22 Benoit St-Jean <bstjean(a)yahoo.com> > >> Here's the first test run, on a fresh image (see JPEG attached for >> results). >> >> >> I just unzipped the files, started Pharo and ran the Test Runner. >> >> No preferences changed, nothing even evaluated in a workspace! >> >> I'm on XP if that helps! >> >> >> _______________________________________________ >> 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. 22, 2010

Re: [Pharo-project] about bufferedFileStream

by StÃ©phane Ducasse

Thanks. I was wondering if in addition to chunk versus single element reading, the logic of the tools was not fooled and for example accessing two times the source code (may be for identifying selector and the other for method body or something like that). Stef On Jan 21, 2010, at 8:19 PM, Levente Uzonyi wrote: > On Thu, 21 Jan 2010, StÃ©phane Ducasse wrote: > >> Hi levente >> >> I was wondering why the bufferedFileStream made the system faster. >> I mean are querying the same contents on several occasion? > > As Nicolas said, not all primitives have the same cost. The file primitives cost a lot more than primitive 65 or some smalltalk code. > And as Igor said accessing the disk costs a lot more than accessing memory, but that only counts in rare cases. Yes I imagine that. Marcus in the past did an experience to get all the code in memory and it was fast to do some source code search :) > Here's an example showing that the file primitive costs almost the same if it reads 1 or 2000 bytes: > > #(1 2000) collect: [ :bufferSize | > (1 to: 5) collect: [ :run | > StandardFileStream readOnlyFileNamed: SourceFiles second name do: [ :file | > | buffer fileID | > fileID := file instVarNamed: #fileID. > buffer := String new: bufferSize. > Smalltalk garbageCollect. > [ 1 to: 100000 do: [ :each | > file > primSetPosition: fileID to: 0; > primRead: fileID into: buffer startingAt: 1 count: bufferSize ] ] timeToRun ] ] ] > > ===> #( > #(458 466 463 466 467) > #(482 484 492 483 484)) > > This means that a primitive send takes ~2.5 microseconds so it can be used ~400000 times/second. > If you read one byte/primitive that means 400KB/sec, if you read 2000 bytes/primitive you get 800MB/sec (your disk may be slower of course). > > Using the buffer you get the following values: > (1 to: 10) collect: [ :run | > StandardFileStream readOnlyFileNamed: SourceFiles second name do: [ :file | > Smalltalk garbageCollect. > [ 1 to: 100000 do: [ :each | > file next ] ] timeToRun ] ] > ===> #(15 14 12 11 12 12 11 12 12 12) > > It takes ~12 milliseconds to read 100KB if you read the bytes one-by-one. That means 8.3MB/sec. This is far from 800MB/sec, but much better than the 400KB/sec. > > > Why does it matter? Because MultiByteFileStream (which is the default FileStream) can only read (and convert) single bytes. Ok so this means that reading files could be really speed up by supporting a kind of "larger chunk" reading. > > > Levente > > >> >> 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

Jan. 22, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Mariano Martinez Peck

> - I hate the old style Squeak cursor and would rather see different > cursors (see ConfigurationOfVistaCursors for an example) I tried. It looks nicer, but...too white. Most of the backgrounds are white or soft colors...thus, I really cannot distinguish very much the mouse... Can I put that cursos but in black ? If true, how ? Thanks Mariano

Jan. 22, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Mariano Martinez Peck

2010/1/22 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > El vie, 22-01-2010 a las 18:13 +0100, Mariano Martinez Peck escribiÃ³: > > > > > > I generally use: > > Preferences enable: #fastDragWindowForMorphic. > > Preferences disable: #windowAnimation. > > > > ok...this two are ok in the dev image. Aren't they ? > > > > Preferences enable: #updateSavesFile. > > > > I am not sure what it does. But anyway, we remove the update from the > > dev image...so, this still make sense? > > > > What does it saves ? which kind of file is it ? a mcz ? > > Yes it saves the files of the update stream and as you correctly state, > it is not needed because the updat eoption is disable. :) > > :) Sol...in summary, you agree with the default preferences! > > > > > > > > > > > > Preferences disable: #windowAnimation. > > > > > > > - When installing Seaside now doesn't ask for user and > > password > > > ( admin/seaside ). In addition, the Seaside Control Panel is > > only > > > isntalled if OB is installed. This means that yu can install > > it in > > > core or dev. Thanks Dale! > > > - Disable of System Update for Dev images as it is not > > working > > > properly. > > > > > > Isn't working? In the image from your link, the preference is > > working > > correctly. > > > > > > > > > > > The link is: > > > > > > https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2… > > > > > > Cheers > > > > > > Mariano > > > > > > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > > Miguel CobÃ¡ > > http://miguel.leugim.com.mx > > > > > > > > _______________________________________________ > > 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 > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 22, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Miguel Enrique CobÃ¡ Martinez

El vie, 22-01-2010 a las 18:13 +0100, Mariano Martinez Peck escribiÃ³: > > > I generally use: > Preferences enable: #fastDragWindowForMorphic. > Preferences disable: #windowAnimation. > > ok...this two are ok in the dev image. Aren't they ? > > Preferences enable: #updateSavesFile. > > I am not sure what it does. But anyway, we remove the update from the > dev image...so, this still make sense? > > What does it saves ? which kind of file is it ? a mcz ? Yes it saves the files of the update stream and as you correctly state, it is not needed because the updat eoption is disable. :) > > > > > > Preferences disable: #windowAnimation. > > > > - When installing Seaside now doesn't ask for user and > password > > ( admin/seaside ). In addition, the Seaside Control Panel is > only > > isntalled if OB is installed. This means that yu can install > it in > > core or dev. Thanks Dale! > > - Disable of System Update for Dev images as it is not > working > > properly. > > > Isn't working? In the image from your link, the preference is > working > correctly. > > > > > > > The link is: > > > https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2… > > > > Cheers > > > > Mariano > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > > _______________________________________________ > 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 -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Jan. 22, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Mariano Martinez Peck

> > I generally use: > Preferences enable: #fastDragWindowForMorphic. > Preferences disable: #windowAnimation. > ok...this two are ok in the dev image. Aren't they ? > Preferences enable: #updateSavesFile. > I am not sure what it does. But anyway, we remove the update from the dev image...so, this still make sense? What does it saves ? which kind of file is it ? a mcz ? > Preferences disable: #windowAnimation. > > > > - When installing Seaside now doesn't ask for user and password > > ( admin/seaside ). In addition, the Seaside Control Panel is only > > isntalled if OB is installed. This means that yu can install it in > > core or dev. Thanks Dale! > > - Disable of System Update for Dev images as it is not working > > properly. > > Isn't working? In the image from your link, the preference is working > correctly. > > > > > > > The link is: > > > https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2… > > > > Cheers > > > > Mariano > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 22, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Mariano Martinez Peck

> ... > > I cannot reproduce the Gofer test failure. Can you debug it and/or > provide a stack trace? > > Sorry...I cannot reproduce them. Here are green. Can some someone that has failing do it ? > 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 >

Jan. 22, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Mariano Martinez Peck

Thanks lukas, It worked :) On Fri, Jan 22, 2010 at 5:52 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > > Ok, OBButtonBarTest>>testLayout we have seen before. I thought that I > > fixed it, but obviously it still breaks depending on the active UI > > Theme. The thing is that the "Watery 2" are so bulky that they float > > over the space that the test-case gives them, so the layout breaks. I > > made the space wider, so it passes with all UI Themes again. It will > > break again when somebody makes the fonts bigger or something similar > > ... > > Fixed here: > > Name: OB-Tests-Morphic-lr.24 > Author: lr > Time: 22 January 2010, 5:52:31 pm > UUID: d7dbc6d2-a995-4be4-a321-6f63797ce39c > Ancestors: OB-Tests-Morphic-lr.23 > > - avoid that the 'Watery 2' UI Theme lets the buttons of the button > morph overflow and break the test > > Lukas > > > > > I cannot reproduce the Gofer test failure. Can you debug it and/or > > provide a stack trace? > > > > Lukas > > > > -- > > Lukas Renggli > > http://www.lukas-renggli.ch > > > > > > -- > 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. 22, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Mariano Martinez Peck

2010/1/22 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > El vie, 22-01-2010 a las 16:10 +0100, Mariano Martinez Peck escribiÃ³: > > > > > > Hey Mariano, good work. the 1.0 release is almost here. > > I like the image, but as the others say centered and in a white > background or a blue like the one of the image. > > If you really like the idea of having a nice background like this, we will someone can take care about it. I know nothing. Just did a Proof of concept :) Does someone want to take care of this please? > Cheers > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 22, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Simon Denier

On 22 janv. 2010, at 16:33, Tudor Girba wrote: > Hi Mariano, > > Nice work. > > Moose loads and works as expected. I also loaded O2 without problems. And the Moose tests run fine on a linux server. > > Cheers, > Doru > > > On 22 Jan 2010, at 15:32, Mariano Martinez Peck wrote: > >> Hi folks. This is 1.0 RC2. Please, look at this image in a nice way >> because it is very likely that if there is no big issue, it will be >> 1.0 official. We need to release 1.0. >> >> Issues fixed: In addition to the fixes from the PharoCore, we have: >> 1033, 1182, 1826, 1862. >> >> Big changes: >> >> - Now we use OB from Lukas Renggli repository and we have ALL TESTS >> GREEN!!! Thanks Lukas! >> - O2 loads again in the image without breaking OB. Read the >> workspace to see how to install it. Thanks David and Alexandre! >> - We have almost (only one failing here) ALL TESTS of the PharoDev >> image in green. They are more than 8800. >> >> Smaller changes: >> >> - Fixed the problem with Metacello and OCompletion. No more overrides. >> - System -> About now shows the real Pharo name, not the core. I am >> also being "compatible" with the new SystemVersion that we have in >> 1.1 :) Thanks Michael and Miguel! >> - I didn't left again my proxy settings. I fixed this in my build >> scripts. It should be clean :) >> - Mercury bar is back again. If you want to disable: Preferences >> disable: #mercuryPanel. >> - Added a lot of cleanups after creating the image, including >> condensing .changes >> - Added Refactoring-Spelling again. Thanks Stan! >> - I wrote a ConfigurationOfNile instead of Nile-All and depends on >> Monticello dependencies. >> - New welcome workspaces. Also getting started workspace and another >> workspace explaining how to load external packages like Seaside (2.8 >> and 3), Magritte, Pier, Moose, GetTools, O2, etc. Finally it is also >> added a link to the new ProfStef :) >> Do you think that with this we are able to close issue1479 ? >> - Background with Pharo picture. This was a joke. It looked >> nice :) I promise I don't put it again if you don't like. To >> remove it evaluate: >> World color: Color white. >> - Enable the preference fastDragWindowForMorphic. Sorry, but it most >> computers this works REALLY slow. If you want them back, just >> disable it. >> - When installing Seaside now doesn't ask for user and password >> ( admin/seaside ). In addition, the Seaside Control Panel is only >> isntalled if OB is installed. This means that yu can install it in >> core or dev. Thanks Dale! >> - Disable of System Update for Dev images as it is not working >> properly. >> >> >> The link is: https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2… >> >> Cheers >> >> Mariano >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "We cannot reach the flow of things unless we let go." > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Simon

Jan. 22, 2010