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

Re: [Pharo-project] [enh] Cleaning of and test for MessageTally

by StÃ©phane Ducasse

thanks On Mar 16, 2010, at 2:15 AM, Alexandre Bergel wrote: > Waiting in PharoInbox. This fix has been developed in a 11271. > > SLICE-MessageTallyCleaningAndTest-Alexandre_Bergel.1 > > > This slices comprises an update for two packages, Tools and ToolsTest. > The new version of Tools clean MessageTally. A user of MessageTally may now decide whether he > wants to close the tally. Although it is convenient to close it (in order to not keep a reference of the > compiled method and the class), this behavior is not always wished. Especially when test have to be > written! > The user has now the option to not open the result window. > > ToolsTest contains few and simple tests. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > 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

March 16, 2010

Re: [Pharo-project] [Pharo-users] Pharo party near Annecy, France

by StÃ©phane Ducasse

I'm sure that ESUG is ready to support the coke and other beverages. Just ask the board. Stef On Mar 15, 2010, at 4:56 PM, laurent laffont wrote: > Hi > > Reminding. > > We try to know how many people will be at the event. > > Cheers, > > Laurent Laffont > > > On Thu, Feb 25, 2010 at 6:46 PM, laurent laffont <laurent.laffont(a)gmail.com> wrote: > Hi, > > We (a developper group) organize a Pharo & Smalltalk meeting near Annecy, France. Saturday, March 20th. 2:00 pm - 6:00pm. > Location. FÃ©lix CrÃ©ation. 4 bis, avenue du Pont de Tasset | 74960 Cran-Gevrier / ANNECY | France > > Welcome to all curious developpers who wants to learn. Welcome to all experienced developpers who wants to share their knowledge. > > We will have wireless access, big screen ... and coffee :) > > Send me a mail if you want to participate. > > Cheers, > > Laurent Laffont > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

March 16, 2010

Re: [Pharo-project] [ANN 1.0] RC3! #10515 pre-built core image

by StÃ©phane Ducasse

thanks chris! Stef On Mar 15, 2010, at 9:13 PM, Chris Muller wrote: > I am happy to report the Magma test suite ran through to completion on > this version. > > On behalf of Pharo + Magma users, thank you. > > - Chris > > On Mon, Mar 15, 2010 at 4:49 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: >> Hi all, >> >> This is PharoCore RC3 and we need your help! >> >> The plan is the following: >> 1. Please test PharoCore RC3 (see link below) and let us know if you find any problems >> 2. If all is fine Mariano builds a new Pharo RC3 image in a few days >> 3. Then please test the Pharo RC3 image and its additional tools and report any problems >> 4. If all is fine we declare RC3 as the final 1.0 release >> >> Cheers, >> Adrian >> >> On Mar 15, 2010, at 10:37 , Marcus Denker wrote: >> >>> >>> >>> https://gforge.inria.fr/frs/download.php/26668/PharoCore-1.0-10515rc3.zip >>> >>> >>> This should be tested a lot... >>> >>> -- >>> 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 >> >> >> _______________________________________________ >> 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

March 16, 2010

Re: [Pharo-project] Code Freeze 1.1?

by StÃ©phane Ducasse

for code 1.1 I would like to be able to remove Preferences. Stef On Mar 16, 2010, at 10:19 AM, Marcus Denker wrote: > Hi, > > Now with 1.0 done, I think we should think about freezing 1.1. > > The main reason of course is that 1.1 is *far more pleasent* to use than 1.0. The other > thing is that 1.1 did change quite some things that have impact on external code (Preferences, > as an example). > > So I think we should > > -> start slowing down on 1.1 (Stef suggested that already) > -> start polishing (tests...) > -> start to look at the Dev image. > -> Official code freeze end of March. > -> Release if possible end of April (this of course depends on the state of things). > > > Any reasons against? > > > Marcus > > > -- > 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

March 16, 2010

Re: [Pharo-project] Code Freeze 1.1?

by StÃ©phane Ducasse

Thanks for the feedback > > Trying to load Magma after the announcement yesterday, I ran into issues with 4 causes: > > - Flaps removal we got Flaps in 1.0 :) > - MethodProperties removal > - Underscore assignement > - Network :P > > Obviously, the tests were hard to run without a network, some of the Collection tests seemed to run excessively long as well (in that I alt-. before they finished). > > There's also the Preferences deprecation, which is bound to cause some work. > > Cheers, > Henry > > On Mar 16, 2010, at 2:10 39PM, Alexandre Bergel wrote: > >> Moose, including Mondrian and Spy load well in Pharo 1.1. No big effort were needed for this. >> I haven't seen that many problems in porting applications to 1.1. >> >> The only thing I bumped into so far, are initialExtent (but apparently this was fixed) and tool registration. >> >> Alexandre >> >> >> On 16 Mar 2010, at 07:50, StÃ©phane Ducasse wrote: >> >>> + 1 >>> end of march for a code freeze would be great. >>> Stef >>> >>> >>> On Mar 16, 2010, at 10:19 AM, Marcus Denker wrote: >>> >>>> Hi, >>>> >>>> Now with 1.0 done, I think we should think about freezing 1.1. >>>> >>>> The main reason of course is that 1.1 is *far more pleasent* to use than 1.0. The other >>>> thing is that 1.1 did change quite some things that have impact on external code (Preferences, >>>> as an example). >>>> >>>> So I think we should >>>> >>>> -> start slowing down on 1.1 (Stef suggested that already) >>>> -> start polishing (tests...) >>>> -> start to look at the Dev image. >>>> -> Official code freeze end of March. >>>> -> Release if possible end of April (this of course depends on the state of things). >>>> >>>> >>>> Any reasons against? >>>> >>>> >>>> Marcus >>>> >>>> >>>> -- >>>> 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 >>> >>> >>> _______________________________________________ >>> 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 >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> 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

March 16, 2010

Re: [Pharo-project] Case statement and lazy comparison in Pharo

by StÃ©phane Ducasse

+ 1 On Mar 15, 2010, at 11:26 PM, Michael Roberts wrote: > I would try and reduce the number of branches first. you can use guard > conditions to exit early. > > This is not necessarily exact below, but you hopefully get the idea... > > (self currentRow == sortedRows last and: [self currentCell isNil]) > ifTrue: [^self navigationKey: event] > > self currentRow ifNil: [^self]. > > self currentCell ifNil: > [^self setCurrentRowToNext] > > self setCurrentCellToNext. > > self currentCell ifNil: [^self]. > > self currentCell performKeyFocus: event inCellBounds: > (self pvtGetCellBounds: self currentCell) > > > A different approach entirely is to have an object(s) that represents > the nil state for the row and cell. That way you are not checking > constantly for it being nil, and perhaps you can dispatch some > behaviour to it. > > cheers, > Mike > > On Mon, Mar 15, 2010 at 9:49 PM, nullPointer <epicfan(a)gmail.com> wrote: >> >> Well, perhaps is a theme worked in another times but... is possible for Pharo >> have a basic Case or elseIf statement? I know is easy create you own >> structure control, but not is more useful have a "standard" for everybody? >> IÂ´m tired of write code like that... >> >> (self currentRow == sortedRows last and: [ self >> currentCell isNil ]) ifTrue: >> [ >> self navigationKey: event >> ] >> ifFalse: >> [ >> (self currentRow notNil and: [ self currentCell isNil ]) ifTrue: >> [ >> self setCurrentRowToNext. >> ] >> ifFalse: >> [ >> (self currentRow notNil and: [ self currentCell notNil ]) ifTrue: >> [ >> self setCurrentCellToNext. >> >> self currentCell notNil ifTrue: >> [ >> self currentCell performKeyFocus: event inCellBounds: (self >> pvtGetCellBounds: self currentCell). >> ]. >> ]. >> ]. >> ]. >> >> >> Write code with that format is pathetical :( >> >> Is valid too have a "and" and "or" lazy? Exists a not lazy with #& and #| , >> but could exists an #&& and #|| . Is more easy... >> >> value1 == value2 and:[ <condition> ] and: [<condition>] ...... >> >> or >> >> value1 == value2 && <condition> && <condition> ......... ??? >> >> Well, perhaps is a stupid question but I miss a more complete way for write >> code. If in Smalltalk is possible do easy that and include it in "core" why >> not do it? >> >> Is a reasonable desire :) >> >> Regards >> >> >> >> >> >> >> -- >> View this message in context: http://n4.nabble.com/Case-statement-and-lazy-comparison-in-Pharo-tp1594080p… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> _______________________________________________ >> 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

March 16, 2010

Re: [Pharo-project] Virtual Pharo sprints

by StÃ©phane Ducasse

We can organize that :) Stef On Mar 15, 2010, at 7:21 PM, GermÃ¡n Arduino wrote: > I also!!!! Very good idea! > > > 2010/3/15 <csrabak(a)bol.com.br>: >> I vote strongly for this! >> >> >> >> >> Em 15/03/2010 11:36, Torsten Bergmann < astares(a)gmx.de > escreveu: >> Since it is hard to be on two places of the world at the same >> time (and to save the climate) I could imagine a "virtual sprint" >> where people who are close can meet in person (in Buenos Aires, >> others in London, others in Berne) but work together online. >> >> One should be able to just tune in using collaborative tools >> (webcam, skype, IRC, Nebraska, Cobalt, ...). >> >> Ideally the tools are written in Pharo (In my archive is some working >> webcam code) ... >> >> Bye >> T. >> >> >> -- >> GMX DSL: Internet, Telefon und Entertainment fÃ¼r nur 19,99 EUR/mtl.! >> http://portal.gmx.net/de/go/dsl02 >> >> _______________________________________________ >> 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

March 16, 2010

Re: [Pharo-project] What is the best way to...

by Lukas Renggli

Also Pier-Document converts Packages, Classes and Methods to Pier pages that can then be displayed on the web or converted to LaTeX or a book or ... Lukas On 16 March 2010 15:43, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Tue, Mar 16, 2010 at 3:25 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Damien did a package to print latex but I do not know its status. >> I'm still dreaming about a Visitor over package, class.... >> that would produce >> Â Â Â Â fileout >> Â Â Â Â html >> Â Â Â Â tex > > SmallAutoDoc produces html or latex. It's quite old however and I > don't know it's current status: > http://www.squeaksource.com/SmallAutoDoc/ > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > > _______________________________________________ > 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

March 16, 2010

Re: [Pharo-project] What is the best way to...

by Damien Cassou

On Tue, Mar 16, 2010 at 3:25 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Damien did a package to print latex but I do not know its status. > I'm still dreaming about a Visitor over package, class.... > that would produce > Â Â Â Â fileout > Â Â Â Â html > Â Â Â Â tex SmallAutoDoc produces html or latex. It's quite old however and I don't know it's current status: http://www.squeaksource.com/SmallAutoDoc/ -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

March 16, 2010

Re: [Pharo-project] A pause... for tests and orthogonal concerns

by StÃ©phane Ducasse

On Mar 15, 2010, at 2:09 PM, Schwab,Wilhelm K wrote: > Stef, > > There is a part of me that wants 1.1 tomorrow<g> to get Alien and full freedom to use underscores, among other things. Briefly on $_, it came back up on squeak-dev, with the usual polarity and screams of doom due to poor aesthetics. It is and IMHO always will be a consideration of external interfacing and avoiding name collisions. I scanned but did not read. I think that Squeak should decide what is good for them. For us _ is banned as := _ can be in selector (not for readibility purposes :)) but for connection to stuff in C outside there :). > Back on topic, tests are good thing. As far as how I can help, a good starting point will be to clean up my image build process. It appears to do a good job of identifying work that I have failed to package and saving the packages I have flagged as mine. I wonder about possible problems with dependencies among packages, but can't say that I have had problems with that; for whatever reason, "cyclic dependencies" magage to terrorize every new Dolphin user at some point :) I am unclear on whether Dolphin is too pedantic, Pharo is too relaxed (and somehow manages to "clean up the messes later"), or whether I am not pushing Pharo hard enough to have problems. Yes we should improve also on the process (not integration) but development process. > Regardless of the details above, I need to revise the load step of my build, and I have been hoping that Loader will appear so I can rewrite it once rather than twice. I noticed mention today that SqueakSource was down (appears ok now). Not meaning to complain about a free service, it hit me once before and I had to add complexity to my builds to work around it; I had thought about taking that out, but a local-only option appears important. I am unclear on how to do that with Metacello - any ideas? Since Gofer supports local and distant loading. It should not be a problem. Ask in metacello ml. Dale is cool and responsive. > > I was going to ask about Citezen and Metacello, but the SqueakSource wiki page shows instructions for it. I will try to test it soon. > > Bill > > > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse > Sent: Sunday, March 14, 2010 6:06 PM > To: Pharo Development > Subject: [Pharo-project] A pause... for tests and orthogonal concerns > > hi guys > > I was discussing with pavel and I like his point. I would like to do a kind of pause and fix the tests. Improve a bit the fact that we get more tests incrementally to avoid regression. > Tell what you think and think how you could help. > > 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

March 16, 2010