February 2019 - Pharo-users

Re: [Pharo-users] What does the Package and Sub-Package comment do?

by Tim Mackinnon

Anyone have any thoughts on this? Not sure whether to report a bug or not. > On 22 Feb 2019, at 14:48, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - I notice that you can sort of put comments on packages - but Iâm not sure if this is working or if its supposed to work? > > When I type something it seems to create and extra Manifest tag, and then the comment that I type seems to be the same for the package and all of its sub tags? > > Is this a work in progress? Should Calypso even show a comment for the tags (or is it read only for them - as its the parent). > > Iâm just not clear on what it does, and whether I can programmatically add stuff to it or not? (I was thinking for exercism to store exercise information there - but maybe I will stick to the test class comment) > > Tim

Feb. 25, 2019

Re: [Pharo-users] Pharo Launcher update installation issues

by Christophe Demarey

Hi, > Le 24 fÃ©vr. 2019 Ã 06:33, Sanjay Minni <sm(a)planage.com> a Ã©crit : > > Hi, > > I am trying to install Pharo Launcher 1.6 (.msi) in Windows 10 > it says "a more ecent version is already installed" and does not proceed > but the version installed is 1.5.1 > > also > in 1.5.1 the left panel shows in the Distributions list 7.0 as "Development > version" - should it not change to Â« Stable" There was an issue : https://github.com/pharo-project/pharo-launcher/issues/310 If you download latest launcher version, it should be fixed. http://pharo.org/download Regards, Christophe

Feb. 25, 2019

instantiate Sparta canvas?

by David Richards

canvas := SpartaCanvas extent: 400@250 This fails even though the documentation says: ''I am an abstract class and should not be instantiated. However, the best way to create an instance of sparta canvas is to send extent: message.'' !! Example: Create an empty canvas of size 400@250: [[[language=smalltalk canvas := SpartaCanvas extent: 400@250. ]]] So, how do instantiate and display a Sparta canvas? Where can I find good documentation about Sparta? Thanks. David

Feb. 25, 2019

Re: [Pharo-users] Why is #findString: in accessing?

by Tim Mackinnon

Hi Sven, thanks for kicking in - yes I do resort to that Finder (and I keep meaning to learn how to port that example search to spotter somehow) - however it only works for non-keyword selectorsâ¦ (another one to investigate to see if it could potentially let you specify a parameter for its search). I still wonder however if a category for âsearchingâ might be way more approachable - as accessing is far to broad on collection classes? Tim > On 25 Feb 2019, at 11:40, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Tim, > > It always takes effort to learn a new language/environment/library. You can't expect it to be the same to what you know, or for things to be where you expect them. > > String is also one of the most overloaded classes in the system, it will never be clean. > > Lots of things fall under 'accessing', that finding something is classified as such, does not really surprise me. > > Did you know about the Finder 'by example search' ? Here is how to find your selector: > > <Screenshot 2019-02-25 at 12.36.15.png> > > HTH, > > Sven > >> On 25 Feb 2019, at 12:19, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> >> I always struggle (even after years of casually using smalltalk) to find the String methods that do the heavy lifting (and are comparable to other languages). The methods are normally there, but they often have names that donât compare well with other languages. >> >> I think that what doesnât help is the categorisation of methods in String - for example - if I want to do some searching in a String - why is #findString: in âaccessingâ - I totally didnât think to look in there. To be honest, I really wanted a protocol called âsearchingâ - but its not there? >> >> I find the protocols in the system to be pretty bad in all honesty. Its a good idea, but I donât think its clear on whether its protocol, or category. And if the former - where are the tools to help ensure things conform to a protocol? If the latter - where are the useful, commonly used categories? >> >> Are there any plans to do anything in this area - or is it just a lump it scenario? >> >> Tim >

Feb. 25, 2019

Re: [Pharo-users] Why is #findString: in accessing?

by Sven Van Caekenberghe

Tim, It always takes effort to learn a new language/environment/library. You can't expect it to be the same to what you know, or for things to be where you expect them. String is also one of the most overloaded classes in the system, it will never be clean. Lots of things fall under 'accessing', that finding something is classified as such, does not really surprise me. Did you know about the Finder 'by example search' ? Here is how to find your selector: HTH, Sven > On 25 Feb 2019, at 12:19, Tim Mackinnon <tim(a)testit.works> wrote: > > I always struggle (even after years of casually using smalltalk) to find the String methods that do the heavy lifting (and are comparable to other languages). The methods are normally there, but they often have names that donât compare well with other languages. > > I think that what doesnât help is the categorisation of methods in String - for example - if I want to do some searching in a String - why is #findString: in âaccessingâ - I totally didnât think to look in there. To be honest, I really wanted a protocol called âsearchingâ - but its not there? > > I find the protocols in the system to be pretty bad in all honesty. Its a good idea, but I donât think its clear on whether its protocol, or category. And if the former - where are the tools to help ensure things conform to a protocol? If the latter - where are the useful, commonly used categories? > > Are there any plans to do anything in this area - or is it just a lump it scenario? > > Tim

Feb. 25, 2019

Why is #findString: in accessing?

by Tim Mackinnon

I always struggle (even after years of casually using smalltalk) to find the String methods that do the heavy lifting (and are comparable to other languages). The methods are normally there, but they often have names that donât compare well with other languages. I think that what doesnât help is the categorisation of methods in String - for example - if I want to do some searching in a String - why is #findString: in âaccessingâ - I totally didnât think to look in there. To be honest, I really wanted a protocol called âsearchingâ - but its not there? I find the protocols in the system to be pretty bad in all honesty. Its a good idea, but I donât think its clear on whether its protocol, or category. And if the former - where are the tools to help ensure things conform to a protocol? If the latter - where are the useful, commonly used categories? Are there any plans to do anything in this area - or is it just a lump it scenario? Tim

Feb. 25, 2019

(no subject)

by Raymond Brinzer

zz P

Feb. 24, 2019

Re: [Pharo-users] Mac OS X test [ smaller image ]

by Hilaire

Thanks Sven, It looks like the same VM I used with the previous bundle. md5sum on the Pharo executable produced the same check sum. Still I packaged one with this bundle, this time I preserved the plugin lib symlink in the zip archive, if you want to give a try. https://www.dropbox.com/s/me1z6prfln1pbe8/DrGeo-mac-19.03a.zip?dl=0 Le 24/02/2019 Ã 20:32, Sven Van Caekenberghe a Ã©critÂ : > Yes, it depends on the platform on which you execute that expression. > > It resolved to > > http://files.pharo.org/get-files/70/pharo-mac-stable.zip -- Dr. Geo http://drgeo.eu

Feb. 24, 2019

Re: [Pharo-users] Mac OS X test [ smaller image ]

by Sven Van Caekenberghe

Yes, it depends on the platform on which you execute that expression. It resolved to http://files.pharo.org/get-files/70/pharo-mac-stable.zip > On 24 Feb 2019, at 20:26, Hilaire <hilaire(a)drgeo.eu> wrote: > > I know. Last summer I give a try to the 64bits version, but there was a > show stopper issue, the PNG image decoder on 64bits architecture. > > Hilaire > > Le 24/02/2019 Ã 13:26, Sven Van Caekenberghe a Ã©crit : >> Note that on macOS and Linux, 64 bit is the default and 32 bit is the >> exception that will be harder to get running. > > -- > Dr. Geo > http://drgeo.eu > > >

Feb. 24, 2019

Re: [Pharo-users] Mac OS X test [ smaller image ]

by Hilaire

I know. Last summer I give a try to the 64bits version, but there was a show stopper issue, the PNG image decoder on 64bits architecture. Hilaire Le 24/02/2019 Ã 13:26, Sven Van Caekenberghe a Ã©critÂ : > Note that on macOS and Linux, 64 bit is the default and 32 bit is the > exception that will be harder to get running. -- Dr. Geo http://drgeo.eu

Feb. 24, 2019