- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Where declared global reside... how can they be removed?

by Igor Stasenko

And few things about playing with morphs. Rather than doing this in workspace (and therefore inventing a ways how to get a reference to your morph), i think you'd better to do that in morph's inspector: Morph new inspect; openInWorld now, after you Doit the above, you'll have a new morph on screen and its inspector opened. In inspector's lower pane you can send any messages to morph using 'self' i.e.: instead of: MySquare color: Color yellow in workspace, write: self color: Color yellow in inspector. 2009/7/17 Igor Stasenko <siguctua(a)gmail.com>: > 2009/7/17 John Escobedo <letmeshowyou(a)gmail.com>: >> Hi everyone, >> >> I'm new to both Smalltalk and especially to Pharo (and this mailing list). >> I have a very basic question and would like to be directed to more >> info or a different mailing list if appropriate. >> >> For most tutorials (I'm using squeak tutorials), one does a lot of >> work in a workspace. >> >> If I make a new global variable such as: >> >> Â Â Â Â Â Â Â Â Â Â MySquare := Morph new >> >> ...once I define "MySquare" as a global variable I know I can send it >> many messages like: >> >> >> Â Â Â Â Â Â Â Â Â Â MySquare openInWorld >> Â Â Â Â Â Â Â Â Â Â MySquare color: Color yellow >> >> When I'm done and I close the workspace, save the image and save the >> image. Â When I open it again it will know what "MySquare" is known in >> any workspace. >> >> How do I remove "MySquare" and/or the associated object? >> How could I see or find other such global variables? >> > Smalltalk inspect - gives you all the globals :) > And to remove, as in any dictionary , use: > Smalltalk removeKey: #MyGlobal > but beware, if your global is a class, you'd better remove it using > tools (or specialized method for removing classes). > > My personal advice (or take it as a opinion) : > - NEVER USE any globals except from class names. > - try to avoid referencing "uncommon" globals directly in methods. > Better create an accessor method to it, and put a reference in there, > and then use this accessor in the rest of your methods. In this way, > if you would want to get rid of it, rename it, or refactor it - you > will know that all you need to do is to change a single method, rather > than 100000 of methods, which referencing this global. > > >> - John >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > -- Best regards, Igor Stasenko AKA sig.

July 17, 2009

Re: [Pharo-project] Where declared global reside... how can they be removed?

by Igor Stasenko

2009/7/17 John Escobedo <letmeshowyou(a)gmail.com>: > Hi everyone, > > I'm new to both Smalltalk and especially to Pharo (and this mailing list). > I have a very basic question and would like to be directed to more > info or a different mailing list if appropriate. > > For most tutorials (I'm using squeak tutorials), one does a lot of > work in a workspace. > > If I make a new global variable such as: > > Â Â Â Â Â Â Â Â Â Â MySquare := Morph new > > ...once I define "MySquare" as a global variable I know I can send it > many messages like: > > > Â Â Â Â Â Â Â Â Â Â MySquare openInWorld > Â Â Â Â Â Â Â Â Â Â MySquare color: Color yellow > > When I'm done and I close the workspace, save the image and save the > image. Â When I open it again it will know what "MySquare" is known in > any workspace. > > How do I remove "MySquare" and/or the associated object? > How could I see or find other such global variables? > Smalltalk inspect - gives you all the globals :) And to remove, as in any dictionary , use: Smalltalk removeKey: #MyGlobal but beware, if your global is a class, you'd better remove it using tools (or specialized method for removing classes). My personal advice (or take it as a opinion) : - NEVER USE any globals except from class names. - try to avoid referencing "uncommon" globals directly in methods. Better create an accessor method to it, and put a reference in there, and then use this accessor in the rest of your methods. In this way, if you would want to get rid of it, rename it, or refactor it - you will know that all you need to do is to change a single method, rather than 100000 of methods, which referencing this global. > - John > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

July 17, 2009

Re: [Pharo-project] Call for testers of a faster MC

by Douglas Brebner

Keith Hodges wrote: > Stef if you want to load the source code direct from an mcz, Installer > can do it as in the following example. > > scriptUpgradeMonticelloBootstrap > > (Installer url: 'http://www.squeaksource.com/mc/PackageInfo-Base') > fileInSource. > (Installer url: > 'http://www.squeaksource.com/mc/System-PasswordManager') fileInSource. > (Installer url: 'http://www.squeaksource.com/mc/', self class > configMCVersion,'.mcz') fileInSource. > > This is available in Installer install: 'UpgradeMonticelloBootstrap'. > > Damien loads MC1.5 via... > > Installer install: 'LevelPlayingField' > > this doesnt include Installer-Launcher which causes the above problem. > > > I was able to load it in a 10379 image after upgrading Installer. Preferences enable: #allowBlockArgumentAssignment. Preferences disable: #raiseDepreciatedWarnings. Installer upgrade upgrade. Installer install: 'UpgradeMonticelloBootstrap'. Thanks to Keith :)

July 17, 2009

[Pharo-project] Where declared global reside... how can they be removed?

by John Escobedo

Hi everyone, I'm new to both Smalltalk and especially to Pharo (and this mailing list). I have a very basic question and would like to be directed to more info or a different mailing list if appropriate. For most tutorials (I'm using squeak tutorials), one does a lot of work in a workspace. If I make a new global variable such as: MySquare := Morph new ...once I define "MySquare" as a global variable I know I can send it many messages like: MySquare openInWorld MySquare color: Color yellow When I'm done and I close the workspace, save the image and save the image. When I open it again it will know what "MySquare" is known in any workspace. How do I remove "MySquare" and/or the associated object? How could I see or find other such global variables? - John

July 17, 2009

Re: [Pharo-project] Call for testers of a faster MC

by Keith Hodges

StÃ©phane Ducasse wrote: > thanks mariano and kirtai. > > On Jul 16, 2009, at 10:39 PM, Mariano Martinez Peck wrote: > > >> Stef....Kirtai was looking you in IRC >> >> [16:39] <Kirtai> is stephanes problem with loading mc due to non- >> atomicloading changing a method then using it before another method >> it depends on is compiled? >> [17:06] <marianopeck> Kirtai: stef isn't in IRC most of the time >> [17:07] <marianopeck> it would be better to send him an email >> [17:07] <Kirtai> I'm just lookin at the problem >> [17:07] <Kirtai> seems that MCMethodDefinition>>actualClass is >> calling MCMethodDefinition>>actualClassIn: after actualClass is >> recompiled but before actualClassIn: is installed >> > > argh! > LPF files in the source first as a file in, then as an mc package Keith

July 17, 2009

Re: [Pharo-project] Call for testers of a faster MC

by Keith Hodges

Douglas Brebner wrote: > Douglas Brebner wrote: > >> Stephane, if you set the following preferences >> raiseDepreciatedWarnings=disabled (causes problems due to the Author >> initials depreciation) >> allowBlockArgumentAssignment=enabled (Breaks a method called >> #unloadTraits. A convenience method that isn't used and isn't in the >> image after the install is finished) >> >> then you can load MC 1.5 (with updated Installer) by using Keiths LPF >> script. >> >> After setting the prefs, do the following: >> >> HTTPSocket httpFileIn: 'ftp.squeak.org/3.11/scripts/LPF.st'. >> >> and it should just work. >> >> > I know it's bad form to reply to my own mail but there's minor breakage > in that ProjectLauncher>>#startUpAfterLogin throws a DNU by sending > #setupFlaps when you first click on the world after restarting the image. > > Stef if you want to load the source code direct from an mcz, Installer can do it as in the following example. scriptUpgradeMonticelloBootstrap (Installer url: 'http://www.squeaksource.com/mc/PackageInfo-Base') fileInSource. (Installer url: 'http://www.squeaksource.com/mc/System-PasswordManager') fileInSource. (Installer url: 'http://www.squeaksource.com/mc/', self class configMCVersion,'.mcz') fileInSource. This is available in Installer install: 'UpgradeMonticelloBootstrap'. Damien loads MC1.5 via... Installer install: 'LevelPlayingField' this doesnt include Installer-Launcher which causes the above problem. Keith

July 17, 2009

Re: [Pharo-project] Pharo-Dev/web Image slowness

by Douglas Brebner

StÃ©phane Ducasse wrote: > Ok we will fix that for 1.0 > right now we are not even in beta. > > As a minor point, running Pharo on a network drive is *horrifically* slow so don't do that :)

July 16, 2009

Re: [Pharo-project] Call for testers of a faster MC

by Douglas Brebner

Douglas Brebner wrote: > Stephane, if you set the following preferences > raiseDepreciatedWarnings=disabled (causes problems due to the Author > initials depreciation) > allowBlockArgumentAssignment=enabled (Breaks a method called > #unloadTraits. A convenience method that isn't used and isn't in the > image after the install is finished) > > then you can load MC 1.5 (with updated Installer) by using Keiths LPF > script. > > After setting the prefs, do the following: > > HTTPSocket httpFileIn: 'ftp.squeak.org/3.11/scripts/LPF.st'. > > and it should just work. > I know it's bad form to reply to my own mail but there's minor breakage in that ProjectLauncher>>#startUpAfterLogin throws a DNU by sending #setupFlaps when you first click on the world after restarting the image.

July 16, 2009

Re: [Pharo-project] KnownLands: a Class dependency explorer

by Nicolas Cellier

2009/7/16 David Goehrig <dave(a)nexttolast.com>: > > I've got few more images up on my blog with my off the cuff impressions of > what is going on. > http://blog.dloh.org/2009/07/visualizing-squeak.html > HopefullyÂ tomorrowÂ I'llÂ findÂ someÂ timeÂ toÂ polishÂ offÂ theÂ methodÂ <->Â classÂ linkingÂ code,Â andÂ polishÂ itÂ upÂ enoughÂ thatÂ otherÂ peopleÂ couldÂ importÂ itÂ intoÂ theirÂ imagesÂ andÂ startÂ playing.Â Â I'mÂ currentlyÂ relyingÂ onÂ aÂ fewÂ languageÂ extensionsÂ inÂ myÂ imageÂ thatÂ aren'tÂ suitableÂ forÂ generalÂ consumption.Â Â (Â likeÂ implicitÂ symbols,Â super-overloadedÂ comma, > and default DNU returns nil). > Yeah, we have to find someone not caring too much for his shoes to kick these ball of mud! Nicolas

July 16, 2009

Re: [Pharo-project] Call for testers of a faster MC

by Douglas Brebner

StÃ©phane Ducasse wrote: > thanks mariano and kirtai. > > On Jul 16, 2009, at 10:39 PM, Mariano Martinez Peck wrote: > > >> Stef....Kirtai was looking you in IRC >> >> [16:39] <Kirtai> is stephanes problem with loading mc due to non- >> atomicloading changing a method then using it before another method >> it depends on is compiled? >> [17:06] <marianopeck> Kirtai: stef isn't in IRC most of the time >> [17:07] <marianopeck> it would be better to send him an email >> [17:07] <Kirtai> I'm just lookin at the problem >> [17:07] <Kirtai> seems that MCMethodDefinition>>actualClass is >> calling MCMethodDefinition>>actualClassIn: after actualClass is >> recompiled but before actualClassIn: is installed >> > > argh! > Stephane, if you set the following preferences raiseDepreciatedWarnings=disabled (causes problems due to the Author initials depreciation) allowBlockArgumentAssignment=enabled (Breaks a method called #unloadTraits. A convenience method that isn't used and isn't in the image after the install is finished) then you can load MC 1.5 (with updated Installer) by using Keiths LPF script. After setting the prefs, do the following: HTTPSocket httpFileIn: 'ftp.squeak.org/3.11/scripts/LPF.st'. and it should just work.

July 16, 2009