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

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by StÃ©phane Ducasse

good question. I'm doing 1.1 and 1.0 is not in my radar. We should learn for 1.1 to make it faster and one way is to get tests greener before. Stef > Hi, > > But if it is done, why don't you just release the official one? > > Cheers, > Doru > > > On 25 Mar 2010, at 09:25, StÃ©phane Ducasse wrote: > >> +1 >> >> 1.1 is waiting for you guys and it is sexy and requires people to use it :) >> >> On Mar 25, 2010, at 9:00 AM, Marcus Denker wrote: >> >>> >>> On Mar 25, 2010, at 8:53 AM, Geert Claes wrote: >>> >>>> >>>> >>>> Mariano Martinez Peck wrote: >>>>> >>>>> Sorry. Want I wanted to ask is...for next Pharo releases, I do the same >>>>> but >>>>> making clear O2 is not by default ? or I just don't say anything about O2 >>>>> in the release ? >>>>> >>>> >>>> While choice is a good thing it does make things more complicated and the >>>> PBE book will need to just choose one I guess. It should be easier to swap >>>> betweem OB or O2 though, maybe not necessarily both in the same image at the >>>> same time but easy to load/unload. >>>> >>>> Have they really moved that far apart that the initial idea of >>>> OB-Enhancements is not possible? >>>> >>> >>> 1.0 is *DONE* *DONE* *DONE*. We should not discuss changing now everthing again. >>> We can do that for 1.1 >>> >>> 1.0 does not have O2. >>> >>> So for the book, there will be a special image with O2 loaded. >>> >>> 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 > > -- > www.tudorgirba.com > > "Reasonable is what we are accustomed with." > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 25, 2010

Re: [Pharo-project] SystemSetting fixes + Preferences references removal

by StÃ©phane Ducasse

thanks a lot .... Stef On Mar 25, 2010, at 9:41 AM, Alain Plantec wrote: > Hi all, > > In the InBox: > SLICE-SystSettings > * range setting: bad widget height in the SettingBrowser > * improve TimeProfiler (MorphTreeMorph example) > * remove resurrected Preferences references > > Cheers > Alain > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 25, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Tudor Girba

Hi, But if it is done, why don't you just release the official one? Cheers, Doru On 25 Mar 2010, at 09:25, StÃ©phane Ducasse wrote: > +1 > > 1.1 is waiting for you guys and it is sexy and requires people to > use it :) > > On Mar 25, 2010, at 9:00 AM, Marcus Denker wrote: > >> >> On Mar 25, 2010, at 8:53 AM, Geert Claes wrote: >> >>> >>> >>> Mariano Martinez Peck wrote: >>>> >>>> Sorry. Want I wanted to ask is...for next Pharo releases, I do >>>> the same >>>> but >>>> making clear O2 is not by default ? or I just don't say anything >>>> about O2 >>>> in the release ? >>>> >>> >>> While choice is a good thing it does make things more complicated >>> and the >>> PBE book will need to just choose one I guess. It should be >>> easier to swap >>> betweem OB or O2 though, maybe not necessarily both in the same >>> image at the >>> same time but easy to load/unload. >>> >>> Have they really moved that far apart that the initial idea of >>> OB-Enhancements is not possible? >>> >> >> 1.0 is *DONE* *DONE* *DONE*. We should not discuss changing now >> everthing again. >> We can do that for 1.1 >> >> 1.0 does not have O2. >> >> So for the book, there will be a special image with O2 loaded. >> >> 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 -- www.tudorgirba.com "Reasonable is what we are accustomed with."

March 25, 2010

Re: [Pharo-project] Auto-rename image and changes file after updating

by Mariano Martinez Peck

On Thu, Mar 25, 2010 at 9:27 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > save as doe not work? > because I do simply save as. > > Yes, it works. But you have to do, system about, copy the version, and then put it in the save us popup hhahaa there are persons VERY lazy :) > > On Mar 25, 2010, at 3:51 AM, HernÃ¡n Morales Durand wrote: > > > Hi, I've noticed every time I update a Pharo image I should rename > > manually the image and changes file names to match the new updated > > version number. I.e.: > > > > If you have > > PharoCore-1.1-11291-UNSTABLE.changes > > PharoCore-1.1-11291-UNSTABLE.image > > > > then update to #11295 and save and quit, you should modify the file > > names manually to > > > > PharoCore-1.1-11295-UNSTABLE.changes > > PharoCore-1.1-11295-UNSTABLE.image > > > > The attached files does the following: > > > > -After a Pharo software update, evaluate the > > FileOutNewNamesAfterUpdate.st script > > -Quit the image > > -For Win users: Run the batch updateFileNames.bat to rename the image > > and changes files to the latest version. > > (this is not the same as Save as...) > > > > Feel free to modify and use it as you want :) > > Cheers, > > > > HernÃ¡n > > > <FileOutNewNamesAfterUpdate.st><updateFileNames>_______________________________________________ > > 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 25, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Lukas Renggli

> Have they really moved that far apart that the initial idea of > OB-Enhancements is not possible? OB-Enhancements patches and changes the OB meta-model and the morphic view in ways that break other browsers and unit tests that have not been built with OB-Enahncements in mind. It is possible to load either of the two browsers, and even both, in any recent Pharo image. I am using OB in Pharo 1.0 and 1.1. OB passes all tests in both environments., including eCompletion, Shout and the Refactoring Engine. http://hudson.lukas-renggli.ch/job/Development/lastCompletedBuild/testRepor… Lukas -- Lukas Renggli http://www.lukas-renggli.ch

March 25, 2010

[Pharo-project] SystemSetting fixes + Preferences references removal

by Alain Plantec

Hi all, In the InBox: SLICE-SystSettings * range setting: bad widget height in the SettingBrowser * improve TimeProfiler (MorphTreeMorph example) * remove resurrected Preferences references Cheers Alain

March 25, 2010

Re: [Pharo-project] Auto-rename image and changes file after updating

by StÃ©phane Ducasse

save as doe not work? because I do simply save as. On Mar 25, 2010, at 3:51 AM, HernÃ¡n Morales Durand wrote: > Hi, I've noticed every time I update a Pharo image I should rename > manually the image and changes file names to match the new updated > version number. I.e.: > > If you have > PharoCore-1.1-11291-UNSTABLE.changes > PharoCore-1.1-11291-UNSTABLE.image > > then update to #11295 and save and quit, you should modify the file > names manually to > > PharoCore-1.1-11295-UNSTABLE.changes > PharoCore-1.1-11295-UNSTABLE.image > > The attached files does the following: > > -After a Pharo software update, evaluate the > FileOutNewNamesAfterUpdate.st script > -Quit the image > -For Win users: Run the batch updateFileNames.bat to rename the image > and changes files to the latest version. > (this is not the same as Save as...) > > Feel free to modify and use it as you want :) > Cheers, > > HernÃ¡n > <FileOutNewNamesAfterUpdate.st><updateFileNames>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 25, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by StÃ©phane Ducasse

+1 1.1 is waiting for you guys and it is sexy and requires people to use it :) On Mar 25, 2010, at 9:00 AM, Marcus Denker wrote: > > On Mar 25, 2010, at 8:53 AM, Geert Claes wrote: > >> >> >> Mariano Martinez Peck wrote: >>> >>> Sorry. Want I wanted to ask is...for next Pharo releases, I do the same >>> but >>> making clear O2 is not by default ? or I just don't say anything about O2 >>> in the release ? >>> >> >> While choice is a good thing it does make things more complicated and the >> PBE book will need to just choose one I guess. It should be easier to swap >> betweem OB or O2 though, maybe not necessarily both in the same image at the >> same time but easy to load/unload. >> >> Have they really moved that far apart that the initial idea of >> OB-Enhancements is not possible? >> > > 1.0 is *DONE* *DONE* *DONE*. We should not discuss changing now everthing again. > We can do that for 1.1 > > 1.0 does not have O2. > > So for the book, there will be a special image with O2 loaded. > > 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 25, 2010

Re: [Pharo-project] Auto-rename image and changes file after updating

by Mariano Martinez Peck

jajajaj thanks HernÃ¡n. You were less lazy than me. I always do the same (manually) ;) Thanks! Mariano 2010/3/25 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> > Hi, I've noticed every time I update a Pharo image I should rename > manually the image and changes file names to match the new updated > version number. I.e.: > > If you have > PharoCore-1.1-11291-UNSTABLE.changes > PharoCore-1.1-11291-UNSTABLE.image > > then update to #11295 and save and quit, you should modify the file > names manually to > > PharoCore-1.1-11295-UNSTABLE.changes > PharoCore-1.1-11295-UNSTABLE.image > > The attached files does the following: > > -After a Pharo software update, evaluate the > FileOutNewNamesAfterUpdate.st script > -Quit the image > -For Win users: Run the batch updateFileNames.bat to rename the image > and changes files to the latest version. > (this is not the same as Save as...) > > Feel free to modify and use it as you want :) > Cheers, > > HernÃ¡n > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 25, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Marcus Denker

On Mar 25, 2010, at 8:53 AM, Geert Claes wrote: > > > Mariano Martinez Peck wrote: >> >> Sorry. Want I wanted to ask is...for next Pharo releases, I do the same >> but >> making clear O2 is not by default ? or I just don't say anything about O2 >> in the release ? >> > > While choice is a good thing it does make things more complicated and the > PBE book will need to just choose one I guess. It should be easier to swap > betweem OB or O2 though, maybe not necessarily both in the same image at the > same time but easy to load/unload. > > Have they really moved that far apart that the initial idea of > OB-Enhancements is not possible? > 1.0 is *DONE* *DONE* *DONE*. We should not discuss changing now everthing again. We can do that for 1.1 1.0 does not have O2. So for the book, there will be a special image with O2 loaded. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 25, 2010