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

Re: [Pharo-project] Nabble

by Mariano Martinez Peck

Thanks! we should update the website now :) On Mon, Jan 18, 2010 at 10:43 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > thanks a lot > > > Just added the Pharo Smalltalk Users mailing list to Nabble ... I prefer > the > > online forums over mailing lists. > > I can imagine > > > > > Just wondering whether Pharo Smaltalk Users should be under Pharo > Smalltalk > > or just under the top level Smalltalk category? > > top level smalltalk is good. > > Stef] > > > -- > > View this message in context: > http://n2.nabble.com/Nabble-tp4416405p4416405.html > > 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 >

Jan. 18, 2010

Re: [Pharo-project] Nabble

by Geert Claes

StÃ©phane Ducasse wrote: > > thanks a lot > No worries StÃ©phane Ducasse wrote: > > top level smalltalk is good. > > Stef] > I guess the Pharo Smalltalk Users link can be added to Pharo-Project.org -- View this message in context: http://n2.nabble.com/Nabble-tp4416405p4416461.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 18, 2010

Re: [Pharo-project] Nabble

by StÃ©phane Ducasse

thanks a lot > Just added the Pharo Smalltalk Users mailing list to Nabble ... I prefer the > online forums over mailing lists. I can imagine > > Just wondering whether Pharo Smaltalk Users should be under Pharo Smalltalk > or just under the top level Smalltalk category? top level smalltalk is good. Stef] > -- > View this message in context: http://n2.nabble.com/Nabble-tp4416405p4416405.html > 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

Jan. 18, 2010

Re: [Pharo-project] Nabble

by Geert Claes

http://n2.nabble.com/Smalltalk-f2356041.html http://n2.nabble.com/Smalltalk-f2356041.html Geert Claes wrote: > > Just added the Pharo Smalltalk Users mailing list to Nabble ... I prefer > the online forums over mailing lists. > > Just wondering whether Pharo Smaltalk Users should be under Pharo > Smalltalk or just under the top level Smalltalk category? > -- View this message in context: http://n2.nabble.com/Nabble-tp4416405p4416412.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 18, 2010

[Pharo-project] testing the linux vm of pharo-project

by StÃ©phane Ducasse

Hi bill can you let us know if the linux VM pointed to on the web site is working (normally it should not since it should be preclosure). Stef

Jan. 18, 2010

[Pharo-project] Nabble

by Geert Claes

Just added the Pharo Smalltalk Users mailing list to Nabble ... I prefer the online forums over mailing lists. Just wondering whether Pharo Smaltalk Users should be under Pharo Smalltalk or just under the top level Smalltalk category? -- View this message in context: http://n2.nabble.com/Nabble-tp4416405p4416405.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 18, 2010

Re: [Pharo-project] I think SmalltalkImage >> changeImageNameTo: is wrong

by Mariano Martinez Peck

hahahhahaha I didn't think about renaming the file from outside :) Thanks Igor. On Mon, Jan 18, 2010 at 10:31 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > 2010/1/18 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > > > > On Mon, Jan 18, 2010 at 5:50 PM, Igor Stasenko <siguctua(a)gmail.com> > wrote: > >> > >> I think the LastImageName is confusing. > >> It should be CurrentImageName or LastKnownImageName. > >> > >> In either way, this is not an image name, which were before you > >> setting a new using > >> #changeImageNameTo:, this is an image name, which you set. > >> > >> The thing is, that if you save an image, the value of this var will be > >> held within an image, > >> so if you rename the image and run squeak with it, > >> the #imageName will return you a file name, > >> while LastImageName is the name what was assigned last. > >> > >> This is how it works, if i'm not mistaken. However i don't see where > >> LastImageName could be useful. > >> > > > > Are you sure ? If LastImageName is what you say, it has few things I > see: > > > > - It has no sense and it is redudant, as I can always do "SmalltalkImage > > current imageName " which uses a primitive, not that global variable > > - the name is wrong from my point of view. If it is LastImageName I > imagine > > it is the previous one. I would rather call it CurrentImageName > > > > I even don't understand why it is a global. It cannot be a simple > variable? > > because I checked in code and it is only used in three methods, all from > > SmalltalkImage. > > > > And, for example, for me is useful in this case. Look SmalltalkImage >> > > saveImageInFileNamed: > > > > You see where it does a saveImageSegments ? Ok, inside that method, I > need > > both images name: the current and the future want. At that moment, I > already > > loose the original. Thus, I need to move it before changeImageNameTo: is > > call. I can do that (I guess), but suppose I cannot. What would I do ? > > > > If I understood you correctly, I would do: > > > > a) Remove completely the global, as I can always do SmalltalkImage > current > > imageName > > b) change everyplace (3 places) where it was used, and replace it by > > SmalltalkImage current imageName and then, change the semantic of > > LastImageName so that it is really the previous one. We can even call it > > PreviousImageName. And those who wants, can use it (right now, only that > > part of ImageSegment). > > > > You seem still confused. > The LastImageName is not a 'previous image name' , it is the file name > of image, when it was last saved to disk. > > so, if you save an image as 'myImage.image' > it will set the LastImageName to that value. > > But next, suppose you renamed an image file, outside of squeak to , > say 'myPharoimage.image' > and now, if you run this image you will get: > > self imageName ==> 'myPharoimage.image' > LastImageName ==> 'myImage.image' > > > What do you think ? > > > > > >> > >> 2010/1/18 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> > Look at SmalltalkImage >> changeImageNameTo: > >> > > >> > > >> > changeImageNameTo: t1 > >> > self imageName: t1 asSqueakPathName. > >> > LastImageName := self imageName > >> > > >> > > >> > Here, it is putting to LastImageName the new one. Shouldn't be in the > >> > other > >> > order, like this: > >> > > >> > changeImageNameTo: t1 > >> > LastImageName := self imageName > >> > self imageName: t1 asSqueakPathName. > >> > > >> > Maybe I misunderstood what LastImageName is > >> > > >> > Thoughts? > >> > > >> > Mariano > >> > > >> > > >> > _______________________________________________ > >> > 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. > >> > >> _______________________________________________ > >> 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 > > > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 18, 2010

Re: [Pharo-project] I think SmalltalkImage >> changeImageNameTo: is wrong

by Igor Stasenko

2010/1/18 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > On Mon, Jan 18, 2010 at 5:50 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> I think the LastImageName is confusing. >> It should be CurrentImageName or LastKnownImageName. >> >> In either way, this is not an image name, which were before you >> setting a new using >> #changeImageNameTo:, this is an image name, which you set. >> >> The thing is, that if you save an image, the value of this var will be >> held within an image, >> so if you rename the image and run squeak with it, >> the #imageName will return you a file name, >> while LastImageName is the name what was assigned last. >> >> This is how it works, if i'm not mistaken. However i don't see where >> LastImageName could be useful. >> > > Are you sure ?Â If LastImageName is what you say, it has few things I see: > > - It has no sense and it is redudant, as I can always do "SmalltalkImage > current imageName "Â Â which uses a primitive, not that global variable > - the name is wrong from my point of view. If it is LastImageName I imagine > it is the previous one. I would rather call it CurrentImageName > > I even don't understand why it is a global. It cannot be a simple variable? > because I checked in code and it is only used in three methods, all from > SmalltalkImage. > > And, for example, for me is useful in this case. Look SmalltalkImage >> > saveImageInFileNamed: > > You see where it does a saveImageSegments ? Ok, inside that method, I need > both images name: the current and the future want. At that moment, I already > loose the original. Thus, I need to move it before changeImageNameTo:Â is > call. I can do that (I guess), but suppose I cannot. What would I do ? > > If I understood you correctly, I would do: > > a) Remove completely the global, as I can always do SmalltalkImage current > imageName > b) change everyplace (3 places) where it was used, and replace it by > SmalltalkImage current imageNameÂ and then, change the semantic of > LastImageName so that it is really the previous one. We can even call it > PreviousImageName. And those who wants, can use it (right now, only that > part of ImageSegment). > You seem still confused. The LastImageName is not a 'previous image name' , it is the file name of image, when it was last saved to disk. so, if you save an image as 'myImage.image' it will set the LastImageName to that value. But next, suppose you renamed an image file, outside of squeak to , say 'myPharoimage.image' and now, if you run this image you will get: self imageName ==> 'myPharoimage.image' LastImageName ==> 'myImage.image' > What do you think ? > > >> >> 2010/1/18 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> > Look at SmalltalkImage >> changeImageNameTo: >> > >> > >> > changeImageNameTo: t1 >> > Â Â Â self imageName: t1 asSqueakPathName. >> > Â Â Â LastImageName := self imageName >> > >> > >> > Here, it is putting to LastImageName the new one. Shouldn't be in the >> > other >> > order, like this: >> > >> > changeImageNameTo: t1 >> > Â Â LastImageName := self imageName >> > Â Â self imageName: t1 asSqueakPathName. >> > >> > Maybe I misunderstood what LastImageName is >> > >> > Thoughts? >> > >> > Mariano >> > >> > >> > _______________________________________________ >> > 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. >> >> _______________________________________________ >> 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 > -- Best regards, Igor Stasenko AKA sig.

Jan. 18, 2010

Re: [Pharo-project] I think SmalltalkImage >> changeImageNameTo: is wrong

by Mariano Martinez Peck

On Mon, Jan 18, 2010 at 5:50 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > I think the LastImageName is confusing. > It should be CurrentImageName or LastKnownImageName. > > In either way, this is not an image name, which were before you > setting a new using > #changeImageNameTo:, this is an image name, which you set. > > The thing is, that if you save an image, the value of this var will be > held within an image, > so if you rename the image and run squeak with it, > the #imageName will return you a file name, > while LastImageName is the name what was assigned last. > > This is how it works, if i'm not mistaken. However i don't see where > LastImageName could be useful. > > Are you sure ? If LastImageName is what you say, it has few things I see: - It has no sense and it is redudant, as I can always do "SmalltalkImage current imageName " which uses a primitive, not that global variable - the name is wrong from my point of view. If it is LastImageName I imagine it is the previous one. I would rather call it CurrentImageName I even don't understand why it is a global. It cannot be a simple variable? because I checked in code and it is only used in three methods, all from SmalltalkImage. And, for example, for me is useful in this case. Look SmalltalkImage >> saveImageInFileNamed: You see where it does a saveImageSegments ? Ok, inside that method, I need both images name: the current and the future want. At that moment, I already loose the original. Thus, I need to move it before changeImageNameTo: is call. I can do that (I guess), but suppose I cannot. What would I do ? If I understood you correctly, I would do: a) Remove completely the global, as I can always do SmalltalkImage current imageName b) change everyplace (3 places) where it was used, and replace it by SmalltalkImage current imageName and then, change the semantic of LastImageName so that it is really the previous one. We can even call it PreviousImageName. And those who wants, can use it (right now, only that part of ImageSegment). What do you think ? > 2010/1/18 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > Look at SmalltalkImage >> changeImageNameTo: > > > > > > changeImageNameTo: t1 > > self imageName: t1 asSqueakPathName. > > LastImageName := self imageName > > > > > > Here, it is putting to LastImageName the new one. Shouldn't be in the > other > > order, like this: > > > > changeImageNameTo: t1 > > LastImageName := self imageName > > self imageName: t1 asSqueakPathName. > > > > Maybe I misunderstood what LastImageName is > > > > Thoughts? > > > > Mariano > > > > > > _______________________________________________ > > 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. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 18, 2010

Re: [Pharo-project] Mercury bar [WAS] Search in Pharo (and other Smalltalkices) what is out there?

by Mariano Martinez Peck

Instead of do that, I would improve Algernon or WorkingSet to fit your requirements. On Mon, Jan 18, 2010 at 9:56 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > may be having it as floating window that populate a (the current) browser > on the fly could be fun? > > On Jan 18, 2010, at 9:42 PM, Simon Denier wrote: > > > > > On 18 janv. 2010, at 19:50, Lukas Renggli wrote: > > > >>> Thanks Lukas. Indeed, it worked and that was the difference between to > >>> images. I will set it again for next image. I think it is useful and it > was > >>> in the previous images. It was my mistake. > >>> > >>> Anyway, you don't use PharoDev images ;) > >>> > >>> Now...what's "screen state" ?? > >> > >> estate, an area or amount of land or property, in particular > >> > >> Some people never use the mercury panel, some never use the annotation > >> panel, some never use the button panel. For them, the panels they > >> never use, is a waste of space and time. > >> > >> The question is if anybody is really using and understanding it (other > >> than just typing a class name)? If I remember correctly it is planned > >> to remove the code from OB. > >> > > > > Yes I use it all the time. I find it more usable than Algernon or even > Working Set when I'm looking for class refs/method users. > > In O2, there is a help text by default which sums up the syntax: > > - AClass (starting with upper case) when looking for a class > > - aMethod (starting with lower case) when looking for a method > > - #AClass, references to AClass > > - #aMethod, senders of aMethod > > - 'hello world', look for substring 'hello world' in method strings > > > > Of course it is also completion-enabled :) > > > > It would be cool if it had a shorcut for Siblings, like in WorkingSet > > - !AClass > > - !aMethod > > > > > > > > It's also true that it eats space for each browser. I think it's should > be easy to put a unique search field in a task bar. As part of my Morphic > experiments, I played a bit with this idea. As an example, you can perform > the following in a workspace (unfortunately it opens two browsers, but > should be difficult to tweak). > > > > (OBMercuryQuery from: '''hello''' panel: (OBPanel new browser: > SystemBrowser default browserClass open model)) find > > > > > > -- > > Simon > > > > > > > > _______________________________________________ > > 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 >

Jan. 18, 2010