April 2018 - Pharo-users - lists.pharo.org

Updating a P7 image

by nacho

Hi, Sorry to ask this potentially stupid question I'm currently using P6.1, but started to take a look at P7. I've noticed that "Software Update" disappeared from the main menu. What is the correct way of updating the P7 image now? Thanks in advance Nacho ----- Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 16, 2018

Re: [Pharo-users] Pharo Launcher

by Ben Coman

On 17 April 2018 at 00:11, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > On Mon, Apr 16, 2018 at 12:30 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> On 16 April 2018 at 16:55, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >> Downloaded it. Installed it. Started it. Selected an image. Bam. >> The >> >> app vanished. >> > >> > As I've mentioned in several other threads, the way new images are >> opened >> > (the lib that executes the command) seems to be very unreliable and >> > sometimes opening image just doesn't work, and I have to open PL again >> and >> > try again. >> > >> > My guess is that there's a race condition and PL closes faster, and >> before >> > the subprocess manages to be disowned. >> >> I untick the box "Quit on Launch" >> > > > That just turns the problem of "I sometimes have to do extra steps" to "I > always have to do extra steps" (i.e. close PL) > You misunderstand. I *prefer* never to close PharoLauncher. Particularly when I dig deep into stuff that is likely to hang an Image, Needing to *again* click the start menu, then click PharoLauncher, to get to the Image I want are two extra steps I like to avoid. I guess thats why I added that feature to PharoLauncher ;) cheers -ben

April 16, 2018

Re: [Pharo-users] [Pharo-Launcher] call for tests on Windows

by Richard Sargent

I ran the launcher against my Windows 7 office computer and have created an issue with my feedback. https://github.com/pharo-project/pharo-launcher/issues/93 On Mon, Apr 16, 2018 at 7:13 AM, Christophe Demarey < christophe.demarey(a)inria.fr> wrote: > Hi, > > Regarding the various problems Pharo Launchers had on Windows, we worked > on a new installer based on Advanced Installer [1] to avoid UAC (User > Account Control) and write permissions problems. This new installer now > installs Pharo Launcher in the userâs local app data folder (where for > sure, he has write permissions). Pharo Launcher also now have its own icon > and use its own name instead of Pharo. Also, the uninstaller now works as > expected. Last but not least, the installer is now signed to avoid warning > of Windows Defender. > Thanks to Ben Coman who did the first version of the packaging using > Advanced Installer (was NSIS). > This version should also improve the launch of Pharo images on Windows. > > So, please could you install and test this new version: and report any > problem with it? http://files.pharo.org/pharo-launcher/win-alpha/ > We do not have windows users around so itâs hard to know if it works > outside our tests boxes. > > Thanks, > Christophe > > [1] https://www.advancedinstaller.com/ >

April 16, 2018

Re: [Pharo-users] UTF-8 encoding

by Sven Van Caekenberghe

> On 16 Apr 2018, at 17:25, Benoit St-Jean <bstjean(a)yahoo.com> wrote: > > "You cannot do that, that is using a null encoding, which is almost always wrong." > > Well, that is exactly what happens when translating my "home" path on Windows 10 ! Then you probably found a bug. As the comment says, the assumption is that the string parameter is something that it is not, it seems to be already decoded. Or it was/is in Latin1. Question remains: how did it get there (from which primitive) ? I am guessing from environment variables. Maybe there is a decoding error there ? > See attached image > > > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > > > On Monday, April 16, 2018, 11:12:58 a.m. EDT, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > > > On 16 Apr 2018, at 17:06, Benoit St-Jean via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > > > > From: Benoit St-Jean <bstjean(a)yahoo.com> > > Subject: UTF-8 encoding > > Date: 16 April 2018 at 17:06:28 GMT+2 > > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > Reply-To: Benoit St-Jean <bstjean(a)yahoo.com> > > > > > > Regarding the problems I have with my firstname and file paths and utf-8 encoding, I found something weird in the UTF-8 encoding. In fact, to be more precise, I found something strange when converting a String to a ByteArray (which UTF-8 encoders convert from) > > > > If I look at the example in the comment of ByteArray>>utf8Decoded, 'Les Ã©lÃ¨ves franÃ§ais' is encoded as: > > > > #[76 101 115 32 195 169 108 195 168 118 101 115 32 102 114 97 110 195 167 97 105 115] > > > > NOW, if I take that very same string, 'Les Ã©lÃ¨ves franÃ§ais' , and convert it to a ByteArray, I get : > > 'Les Ã©lÃ¨ves franÃ§ais' asByteArray printString. > > You cannot do that, that is using a null encoding, which is almost always wrong. > > Please read (the first part) of > > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > > carefully. > > > #[76 101 115 32 233 108 232 118 101 115 32 102 114 97 110 231 97 105 115] > > > > The 2 don't match! > > > > By the way, this problem exists on Pharo 5.1, 6.1 and 7.1 (on Windows 10 ) > > > > Can anyone confirm/infirm on another platform to see if this is Windows-specific? > > This behaviour is not-windows specific, it is like that on all platforms, and it is correct ;-) > > > > ----------------- > > BenoÃ®t St-Jean > > Yahoo! Messenger: bstjean > > Twitter: @BenLeChialeux > > Pinterest: benoitstjean > > Instagram: Chef_Benito > > IRC: lamneth > > Blogue: endormitoire.wordpress.com > > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > > > > > <ByteArrayError.JPG>

April 16, 2018

Re: [Pharo-users] Pharo Launcher

by Peter UhnÃ¡k

On Mon, Apr 16, 2018 at 12:30 PM, Ben Coman <btc(a)openinworld.com> wrote: > On 16 April 2018 at 16:55, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> Downloaded it. Installed it. Started it. Selected an image. Bam. > The > >> app vanished. > > > > As I've mentioned in several other threads, the way new images are opened > > (the lib that executes the command) seems to be very unreliable and > > sometimes opening image just doesn't work, and I have to open PL again > and > > try again. > > > > My guess is that there's a race condition and PL closes faster, and > before > > the subprocess manages to be disowned. > > I untick the box "Quit on Launch" > That just turns the problem of "I sometimes have to do extra steps" to "I always have to do extra steps" (i.e. close PL)

April 16, 2018

Re: [Pharo-users] UTF-8 encoding

by Benoit St-Jean

"You cannot do that, that is using a null encoding, which is almost always wrong." Well, that is exactly what happens when translating my "home" path on Windows 10 ! See attached image ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein) On Monday, April 16, 2018, 11:12:58 a.m. EDT, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > On 16 Apr 2018, at 17:06, Benoit St-Jean via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Benoit St-Jean <bstjean(a)yahoo.com> > Subject: UTF-8 encoding > Date: 16 April 2018 at 17:06:28 GMT+2 > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Reply-To: Benoit St-Jean <bstjean(a)yahoo.com> > > > Regarding the problems I have with my firstname and file paths and utf-8 encoding, I found something weird in the UTF-8 encoding.Â In fact, to be more precise, I found something strange when converting a String to a ByteArray (which UTF-8 encoders convert from) > > If I look at the example in the comment of ByteArray>>utf8Decoded, 'Les Ã©lÃ¨ves franÃ§ais' is encoded as: > > #[76 101 115 32 195 169 108 195 168 118 101 115 32 102 114 97 110 195 167 97 105 115] > > NOW, if I take that very same string, 'Les Ã©lÃ¨ves franÃ§ais' , and convert it to a ByteArray, I get : > 'Les Ã©lÃ¨ves franÃ§ais' asByteArray printString. You cannot do that, that is using a null encoding, which is almost always wrong. Please read (the first part) of https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… carefully. > #[76 101 115 32 233 108 232 118 101 115 32 102 114 97 110 231 97 105 115] > > The 2 don't match! > > By the way, this problem exists on Pharo 5.1, 6.1 and 7.1 (on Windows 10 ) > > Can anyone confirm/infirm on another platform to see if this is Windows-specific? This behaviour is not-windows specific, it is like that on all platforms, and it is correct ;-) > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein) > >

April 16, 2018

Re: [Pharo-users] UTF-8 encoding

by Sven Van Caekenberghe

> On 16 Apr 2018, at 17:06, Benoit St-Jean via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Benoit St-Jean <bstjean(a)yahoo.com> > Subject: UTF-8 encoding > Date: 16 April 2018 at 17:06:28 GMT+2 > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Reply-To: Benoit St-Jean <bstjean(a)yahoo.com> > > > Regarding the problems I have with my firstname and file paths and utf-8 encoding, I found something weird in the UTF-8 encoding. In fact, to be more precise, I found something strange when converting a String to a ByteArray (which UTF-8 encoders convert from) > > If I look at the example in the comment of ByteArray>>utf8Decoded, 'Les Ã©lÃ¨ves franÃ§ais' is encoded as: > > #[76 101 115 32 195 169 108 195 168 118 101 115 32 102 114 97 110 195 167 97 105 115] > > NOW, if I take that very same string, 'Les Ã©lÃ¨ves franÃ§ais' , and convert it to a ByteArray, I get : > 'Les Ã©lÃ¨ves franÃ§ais' asByteArray printString. You cannot do that, that is using a null encoding, which is almost always wrong. Please read (the first part) of https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… carefully. > #[76 101 115 32 233 108 232 118 101 115 32 102 114 97 110 231 97 105 115] > > The 2 don't match! > > By the way, this problem exists on Pharo 5.1, 6.1 and 7.1 (on Windows 10 ) > > Can anyone confirm/infirm on another platform to see if this is Windows-specific? This behaviour is not-windows specific, it is like that on all platforms, and it is correct ;-) > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > >

April 16, 2018

UTF-8 encoding

by Benoit St-Jean

Regarding the problems I have with my firstname and file paths and utf-8 encoding, I found something weird in the UTF-8 encoding.Â In fact, to be more precise, I found something strange when converting a String to a ByteArray (which UTF-8 encoders convert from) If I look at the example in the comment of ByteArray>>utf8Decoded, 'Les Ã©lÃ¨ves franÃ§ais' is encoded as: #[76 101 115 32 195 169 108 195 168 118 101 115 32 102 114 97 110 195 167 97 105 115] NOW, if I take that very same string, 'Les Ã©lÃ¨ves franÃ§ais' , and convert it to a ByteArray, I get : 'Les Ã©lÃ¨ves franÃ§ais' asByteArray printString. #[76 101 115 32 233 108 232 118 101 115 32 102 114 97 110 231 97 105 115] The 2 don't match! By the way, this problem exists on Pharo 5.1, 6.1 and 7.1 (on Windows 10 ) Can anyone confirm/infirm on another platform to see if this is Windows-specific? ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein)

April 16, 2018

Re: [Pharo-users] Some random musings

by Benoit St-Jean

"Float randomBetween: -4.1 and: 2.5 would be the most descriptive and compliant to your signature ;-)" I also prefer #randomBetween:and: . "Going to the class side of Float makes sense because you create a new instance." But I'm not so sure about putting this on the class side. In fact, right now #atRandom is on the instance side and it's been that way since the beginning.Â It would be akward to have one method of generating random numbers on the class side and all others on the instance side.Â And moving everything on the class side would break tons of code and legacy code.Â Besides, random numbers have always been seen and/or dealt with as streams : the intent was to get "the next one" in the stream, not create "a new instance" ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein)

April 16, 2018

Re: [Pharo-users] Some random musings

by Benoit St-Jean

"Any interest to introduce a method to produce random float numbers in an interval in Pharo ?" Yes, that would definitely be useful !!!!Â And it would not only be useful for Float but for all numbers.Â Would save us from the usual "#truncated and +1" trick we always have to write!! ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein)

April 16, 2018