February 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo on osx 10.5

by Mariano Martinez Peck

I think Pharo 1.3 and 1.4 (not 2.0) should run ok with Carbon-based VMs. You can get them from: http://www.mirandabanda.org/files/Cog/VM/VM.r2693/Cog.app.tgz Let me know if that works. On Sat, Feb 23, 2013 at 5:47 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > > > " > > > > - Google announced that the Chrome browser will be dropping support for > Leopard starting on Chrome 21. > > By that time Chrome will no longer auto-update, and new Chrome > installations are unalloyed. > > Their rationale for removal of support is that Leopard is an "OS X > version also no longer being updated by Apple."[61] > > > > - Firefox also dropped support for Leopard after it shipped Firefox 16 > in October, 2012.[62]" > > > Nice quote: > > âApple releases new versions of its operating systems relatively quickly, > and each new version contains > significant changes that we must adapt to,â Aas said. âThis requires > resources, and with limited resources > this sometimes means we have to make tough decisions about where to > invest.â > > > http://www.macworld.com/article/1168241/mozilla_sets_end_of_firefox_for_os_… > (this article is already 6 months oldâ¦) > > Mozilla had "limited" resources (revenue, but revenue is resource in > software) of over 163 million USD in 2011â¦ > > Marcus > > > -- Mariano http://marianopeck.wordpress.com

Feb. 23, 2013

Re: [Pharo-project] Pharo on osx 10.5

by Marcus Denker

> > " > > - Google announced that the Chrome browser will be dropping support for Leopard starting on Chrome 21. > By that time Chrome will no longer auto-update, and new Chrome installations are unalloyed. > Their rationale for removal of support is that Leopard is an "OS X version also no longer being updated by Apple."[61] > > - Firefox also dropped support for Leopard after it shipped Firefox 16 in October, 2012.[62]" > Nice quote: âApple releases new versions of its operating systems relatively quickly, and each new version contains significant changes that we must adapt to,â Aas said. âThis requires resources, and with limited resources this sometimes means we have to make tough decisions about where to invest.â http://www.macworld.com/article/1168241/mozilla_sets_end_of_firefox_for_os_… (this article is already 6 months oldâ¦) Mozilla had "limited" resources (revenue, but revenue is resource in software) of over 163 million USD in 2011â¦ Marcus

Feb. 23, 2013

Re: [Pharo-project] Pharo on osx 10.5

by Marcus Denker

On Feb 23, 2013, at 9:14 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Feb 23, 2013, at 9:11 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On Feb 23, 2013, at 8:55 PM, Nicolas Petton <petton.nicolas(a)gmail.com> wrote: >> >>> Hi guys, >>> >>> I don't have osx 10.5, but someone just told me that he only gets a >>> blank window on start-up. >>> >> >> I think we decided that Pharo only supports 10.6 and newerâ¦ it is very complicated >> to support that many many different old OS versions. >> >> The current is 10.8, supporting 10.6, 10.7 and 10.8 is already quite a lot, I think. >> > > In general: If it is ok for you to run a 3 versions old Operating System, I am sure you will > have no problem to use an ancient, unsupported version of Pharo, too. > > " - Google announced that the Chrome browser will be dropping support for Leopard starting on Chrome 21. By that time Chrome will no longer auto-update, and new Chrome installations are unalloyed. Their rationale for removal of support is that Leopard is an "OS X version also no longer being updated by Apple."[61] - Firefox also dropped support for Leopard after it shipped Firefox 16 in October, 2012.[62]" " -- http://en.wikipedia.org/wiki/Mac_OS_X_Leopard I think if Google, with *BILLIONS* of USD of resources can drop support, we can do too. Marcus

Feb. 23, 2013

Re: [Pharo-project] Pharo on osx 10.5

by Marcus Denker

On Feb 23, 2013, at 9:11 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Feb 23, 2013, at 8:55 PM, Nicolas Petton <petton.nicolas(a)gmail.com> wrote: > >> Hi guys, >> >> I don't have osx 10.5, but someone just told me that he only gets a >> blank window on start-up. >> > > I think we decided that Pharo only supports 10.6 and newerâ¦ it is very complicated > to support that many many different old OS versions. > > The current is 10.8, supporting 10.6, 10.7 and 10.8 is already quite a lot, I think. > In general: If it is ok for you to run a 3 versions old Operating System, I am sure you will have no problem to use an ancient, unsupported version of Pharo, too. Marcus

Feb. 23, 2013

Re: [Pharo-project] Pharo on osx 10.5

by Marcus Denker

On Feb 23, 2013, at 8:55 PM, Nicolas Petton <petton.nicolas(a)gmail.com> wrote: > Hi guys, > > I don't have osx 10.5, but someone just told me that he only gets a > blank window on start-up. > I think we decided that Pharo only supports 10.6 and newerâ¦ it is very complicated to support that many many different old OS versions. The current is 10.8, supporting 10.6, 10.7 and 10.8 is already quite a lot, I think. > I can ask the pharo version and vm (I think it's 1.4 one click), but as > I don't know if it is a known issue, I thought I should ask first :) > of courseâ¦ ;-) http://code.google.com/p/pharo/issues/detail?id=6418 Marcus

Feb. 23, 2013

[Pharo-project] Pharo on osx 10.5

by Nicolas Petton

Hi guys, I don't have osx 10.5, but someone just told me that he only gets a blank window on start-up. I can ask the pharo version and vm (I think it's 1.4 one click), but as I don't know if it is a known issue, I thought I should ask first :) Cheers, Nico

Feb. 23, 2013

Re: [Pharo-project] Weird behavior in Nautilus when doing a method rename

by Camillo Bruni

I like the idea :) but that's for 3.0 => add a scope selector to the changes view => add default scopes (Method/Class/SubPackage/Package/System) => add scope creator (certain methods / certain classes / certain packages) that will indeed cover almost every aspect ;) On 2013-02-23, at 16:50, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > I think all this topic should be quite easy. It should be similar to OB > "scope". > All refactors like method rename affects everything if the scope is the > default. If you want to affect only a class/package do a "Browse scoped" to > a class/package. And then the refactors should only affect that. Of course, > we should explain this somewhere in Pharo doc. > I think this is quite easy and enough for most cases. > > On Thu, Feb 21, 2013 at 6:45 AM, Goubier Thierry <thierry.goubier(a)cea.fr>wrote: > >> Le 20/02/2013 21:33, Benjamin a Ã©crit : >> >>> On Feb 20, 2013, at 8:43 PM, stephane ducasse <stephane.ducasse(a)free.fr >>> <mailto:stephane.ducasse@free.**fr <stephane.ducasse(a)free.fr>>> wrote: >>> >>> >>>> On Feb 20, 2013, at 1:07 PM, Benjamin >>>> <benjamin.vanryseghem.pharo(a)**gmail.com<benjamin.vanryseghem.pharo(a)gmail.com> >>>> <mailto:benjamin.vanryseghem.**pharo@gmail.com<benjamin.vanryseghem.pharo(a)gmail.com>>> >>>> wrote: >>>> >>>> There is actually no simple way to simply rename a method. >>>>> We should maybe add one which keep track of the versions :) >>>>> >>>> >>>> sure there is: >>>> click on the method >>>> in the text pane change the selector of the method and compile. >>>> >>> >>> I am kind of aware of that :) >>> >>> But for a new comer, it's not obvious at all. >>> And usually they first look in the menu and click on the first entry >>> "matching" the need >>> >>> Ben >>> >> >> What about restricting the rename to the current package or class? With, >> say, a box to tick to go system wide? >> >> (And a nice GUI, moose-like, showing on a color map how much of the system >> the rename will impact :)) >> >> Thierry >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> >> > > > -- > Mariano > http://marianopeck.wordpress.com

Feb. 23, 2013

Re: [Pharo-project] Weird behavior in Nautilus when doing a method rename

by Mariano Martinez Peck

I think all this topic should be quite easy. It should be similar to OB "scope". All refactors like method rename affects everything if the scope is the default. If you want to affect only a class/package do a "Browse scoped" to a class/package. And then the refactors should only affect that. Of course, we should explain this somewhere in Pharo doc. I think this is quite easy and enough for most cases. On Thu, Feb 21, 2013 at 6:45 AM, Goubier Thierry <thierry.goubier(a)cea.fr>wrote: > Le 20/02/2013 21:33, Benjamin a Ã©crit : > >> On Feb 20, 2013, at 8:43 PM, stephane ducasse <stephane.ducasse(a)free.fr >> <mailto:stephane.ducasse@free.**fr <stephane.ducasse(a)free.fr>>> wrote: >> >> >>> On Feb 20, 2013, at 1:07 PM, Benjamin >>> <benjamin.vanryseghem.pharo(a)**gmail.com<benjamin.vanryseghem.pharo(a)gmail.com> >>> <mailto:benjamin.vanryseghem.**pharo@gmail.com<benjamin.vanryseghem.pharo(a)gmail.com>>> >>> wrote: >>> >>> There is actually no simple way to simply rename a method. >>>> We should maybe add one which keep track of the versions :) >>>> >>> >>> sure there is: >>> click on the method >>> in the text pane change the selector of the method and compile. >>> >> >> I am kind of aware of that :) >> >> But for a new comer, it's not obvious at all. >> And usually they first look in the menu and click on the first entry >> "matching" the need >> >> Ben >> > > What about restricting the rename to the current package or class? With, > say, a box to tick to go system wide? > > (And a nice GUI, moose-like, showing on a color map how much of the system > the rename will impact :)) > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > > -- Mariano http://marianopeck.wordpress.com

Feb. 23, 2013

Re: [Pharo-project] Stack VM problem

by Camillo Bruni

is this exposed by a test? if not, it would be nice to add a test and then put it on the issue tracker (I guess cog for now..) On 2013-02-23, at 16:03, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > stack-mac-3.zip (latest on gforge) > VirtualMachine getSystemAttribute: 1008 => nil > > UndefinedObject(Object)>>doesNotUnderstand: #do: > WriteStream(Stream)>>nextPutAll: > WriteStream>>nextPutAll: > VirtualMachine class>>version in Block: [:s | ... > > Should VM issues be opened in the Pharo tracker, cog, or somewhere else? > > Cheers, > Sean > > > > -- > View this message in context: http://forum.world.st/Stack-VM-problem-tp4671675.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Feb. 23, 2013

[Pharo-project] Stack VM problem

by Sean P. DeNigris

stack-mac-3.zip (latest on gforge) VirtualMachine getSystemAttribute: 1008 => nil UndefinedObject(Object)>>doesNotUnderstand: #do: WriteStream(Stream)>>nextPutAll: WriteStream>>nextPutAll: VirtualMachine class>>version in Block: [:s | ... Should VM issues be opened in the Pharo tracker, cog, or somewhere else? Cheers, Sean -- View this message in context: http://forum.world.st/Stack-VM-problem-tp4671675.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 23, 2013