November 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] MAC OS upgrade and Pharo compatibility

by Peter Hugosson-Miller

No, Stef, I'm the same: bugs love me! I am sooooooo glad for the excellent backup program SuperDuper. I did the Lion install two times before it worked OK (third time just like I wrote in my post above), but the other two times I was very happy to have the backup to go back to, I can tell you! -- Cheers, Peter On Sat, Nov 5, 2011 at 10:56 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Yes because I could not update after the first install. > So I was lucky to have another machine where I could install and update > **then** migrate. > I was mad during 3 days. > Of course for everybody around it worked well but I attrack bugs. > Stef > On Nov 5, 2011, at 10:40 PM, Peter Hugosson-Miller wrote: > > > Definitely do a backup, then format the disk and perform a clean > install, then do all the necessary software updates until the machine is > completely up to date. Finally restore your user settings and apps from the > backup. That's my recipe for minimum frustration when dealing with Lion :-) > > > > -- > > Cheers, > > Peter > > > > On Sat, Nov 5, 2011 at 10:34 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > There is no problem for pharo on lion. > > Now do a backup because lion of your machine. > > Lion frustrated me a lot. > > > > And in general when I see the amount of applications spinning to death > on normal usage, I think that pharo is doing well. > > > > Stef > > > > On Nov 5, 2011, at 8:09 PM, Dario Trussardi wrote: > > > > > Hi, > > > > > > i'm interested to upgrade my MacBook Operating System, from > Leopard to Lion version. > > > > > > I'm not expert about it and i will not do error. > > > > > > My question is about Pharo compatibility. > > > > > > Now i work with Pharo 1.0 #10517 and GemTools 1.0-beta.8.3. > > > > > > I need to do something or all work fine after upgrade the O/S ? > > > > > > Thanks, > > > > > > Dario > > > > > > P.S. Excuse me if question is not very very pertinent to Pharo > > > > >

Nov. 5, 2011

Re: [Pharo-project] MAC OS upgrade and Pharo compatibility

by StÃ©phane Ducasse

Yes because I could not update after the first install. So I was lucky to have another machine where I could install and update **then** migrate. I was mad during 3 days. Of course for everybody around it worked well but I attrack bugs. Stef On Nov 5, 2011, at 10:40 PM, Peter Hugosson-Miller wrote: > Definitely do a backup, then format the disk and perform a clean install, then do all the necessary software updates until the machine is completely up to date. Finally restore your user settings and apps from the backup. That's my recipe for minimum frustration when dealing with Lion :-) > > -- > Cheers, > Peter > > On Sat, Nov 5, 2011 at 10:34 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > There is no problem for pharo on lion. > Now do a backup because lion of your machine. > Lion frustrated me a lot. > > And in general when I see the amount of applications spinning to death on normal usage, I think that pharo is doing well. > > Stef > > On Nov 5, 2011, at 8:09 PM, Dario Trussardi wrote: > > > Hi, > > > > i'm interested to upgrade my MacBook Operating System, from Leopard to Lion version. > > > > I'm not expert about it and i will not do error. > > > > My question is about Pharo compatibility. > > > > Now i work with Pharo 1.0 #10517 and GemTools 1.0-beta.8.3. > > > > I need to do something or all work fine after upgrade the O/S ? > > > > Thanks, > > > > Dario > > > > P.S. Excuse me if question is not very very pertinent to Pharo > >

Nov. 5, 2011

Re: [Pharo-project] MAC OS upgrade and Pharo compatibility

by Peter Hugosson-Miller

Definitely do a backup, then format the disk and perform a clean install, then do all the necessary software updates until the machine is completely up to date. Finally restore your user settings and apps from the backup. That's my recipe for minimum frustration when dealing with Lion :-) -- Cheers, Peter On Sat, Nov 5, 2011 at 10:34 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > There is no problem for pharo on lion. > Now do a backup because lion of your machine. > Lion frustrated me a lot. > > And in general when I see the amount of applications spinning to death on > normal usage, I think that pharo is doing well. > > Stef > > On Nov 5, 2011, at 8:09 PM, Dario Trussardi wrote: > > > Hi, > > > > i'm interested to upgrade my MacBook Operating System, from > Leopard to Lion version. > > > > I'm not expert about it and i will not do error. > > > > My question is about Pharo compatibility. > > > > Now i work with Pharo 1.0 #10517 and GemTools 1.0-beta.8.3. > > > > I need to do something or all work fine after upgrade the O/S ? > > > > Thanks, > > > > Dario > > > > P.S. Excuse me if question is not very very pertinent to Pharo > > >

Nov. 5, 2011

Re: [Pharo-project] about name for logging message

by StÃ©phane Ducasse

Hi stefan > >> self log: >> self logCr: > > Why is it a rather platform specific CR? Why not some platform independent NL (new line)? Indeed nl is better. I used Cr because people with Transcript show: 'foo' ; cr and not nl as far as I know > And in 1.3, I found the TranscriptModel with #addEntry: which looked like the new way of doing things since #show: has some comment which said it is deprecated/or not cool anymore. AddEntry: is a low level api. Now I will check because there were some movements around transcript in 1.3 and may be some left over were not cleaned. > > Best regards > 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 2974 > Fax: +32 2 629 3525 > >

Nov. 5, 2011

Re: [Pharo-project] about name for logging message

by StÃ©phane Ducasse

Thanks david I do not have OSProcess at hand, but where are these messages defined? On Object? Would it be a problem for you if we define trace and trace: on Object? Stef >>> Hi guys >>> >>> I introduce >>> log to replace Transcript show: ? >>> logCr and crLog >>> >>> Now stupidly I did not notice that it will capture log on number :( and also on collection, >>> >>> So any suggestion of what would be a nice logging message? >>> short and cool. >>> >> How about trace? > > In OSProcess, #trace and #trace: are used for a similar purpose. > This is intended for debugging with "transcript" output coming > from the VM and therefore less dependent on process scheduling > in the image. > > Dave > >

Nov. 5, 2011

Re: [Pharo-project] MAC OS upgrade and Pharo compatibility

by StÃ©phane Ducasse

There is no problem for pharo on lion. Now do a backup because lion of your machine. Lion frustrated me a lot. And in general when I see the amount of applications spinning to death on normal usage, I think that pharo is doing well. Stef On Nov 5, 2011, at 8:09 PM, Dario Trussardi wrote: > Hi, > > i'm interested to upgrade my MacBook Operating System, from Leopard to Lion version. > > I'm not expert about it and i will not do error. > > My question is about Pharo compatibility. > > Now i work with Pharo 1.0 #10517 and GemTools 1.0-beta.8.3. > > I need to do something or all work fine after upgrade the O/S ? > > Thanks, > > Dario > > P.S. Excuse me if question is not very very pertinent to Pharo >

Nov. 5, 2011

Re: [Pharo-project] about name for logging message

by StÃ©phane Ducasse

did you check toothpick by joseph pelrine? Because transcript is not a logger just an historical simple output place. Stef On Nov 5, 2011, at 5:00 PM, Milan Mimica wrote: > Have you thought of a decent logging system with logging levels, output formatter and output appenders? > Current logging sure comes handy, but is really rudimentary. A business application must have a modern logging system, and it's not even a complex thing to do. > I'm just asking whether you have discussed this or have something in mind already. > > On 5 November 2011 12:50, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I introduce > log to replace Transcript show: â¦ > logCr and crLog > > Now stupidly I did not notice that it will capture log on number :( and also on collection, > > So any suggestion of what would be a nice logging message? > short and cool. > > > Stef > > > > -- > Milan Mimica > http://sparklet.sf.net

Nov. 5, 2011

[Pharo-project] MAC OS upgrade and Pharo compatibility

by Dario Trussardi

Hi, i'm interested to upgrade my MacBook Operating System, from Leopard to Lion version. I'm not expert about it and i will not do error. My question is about Pharo compatibility. Now i work with Pharo 1.0 #10517 and GemTools 1.0-beta.8.3. I need to do something or all work fine after upgrade the O/S ? Thanks, Dario P.S. Excuse me if question is not very very pertinent to Pharo

Nov. 5, 2011

Re: [Pharo-project] about name for logging message

by David T. Lewis

On Sat, Nov 05, 2011 at 02:38:14PM +0100, Norbert Hartl wrote: > > Am 05.11.2011 um 12:50 schrieb St?phane Ducasse: > > > Hi guys > > > > I introduce > > log to replace Transcript show: ? > > logCr and crLog > > > > Now stupidly I did not notice that it will capture log on number :( and also on collection, > > > > So any suggestion of what would be a nice logging message? > > short and cool. > > > How about trace? In OSProcess, #trace and #trace: are used for a similar purpose. This is intended for debugging with "transcript" output coming from the VM and therefore less dependent on process scheduling in the image. Dave

Nov. 5, 2011

Re: [Pharo-project] about name for logging message

by Milan Mimica

Have you thought of a decent logging system with logging levels, output formatter and output appenders? Current logging sure comes handy, but is really rudimentary. A business application must have a modern logging system, and it's not even a complex thing to do. I'm just asking whether you have discussed this or have something in mind already. On 5 November 2011 12:50, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Hi guys > > I introduce > log to replace Transcript show: â¦ > logCr and crLog > > Now stupidly I did not notice that it will capture log on number :( and > also on collection, > > So any suggestion of what would be a nice logging message? > short and cool. > > > Stef > -- Milan Mimica http://sparklet.sf.net

Nov. 5, 2011