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

Re: [Pharo-dev] [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-dev] Pharo Launcher on Windows > Failing

by Benoit St-Jean

Downloaded PharoLauncher (the latest installer at http://files.pharo.org/pharo-launcher/win-alpha/, bleedingedge and signed). Installed it without problem in the directory I wanted (as opposed to defaulting to my Documents folder as it was previously). I installed PL in a directory without "funky" characters. But it bombs when PL (class PhLDirectoryBasedImageRepository) assumes my images are located in C:\Users\BenoÃ®St-Jean\Documents\Pharo\images The path is not correctly encoded (the Ã®) and it breaks. No window opens, I get a blank screen and a debugger.Â Screenshot & fuel stack attached. Reported the issue on GitHub: #92 ----------------- 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 Thursday, April 12, 2018, 11:19:44 a.m. EDT, Vincent.Blondeau(a)lamresearch.com <Vincent.Blondeau(a)lamresearch.com> wrote: Hi Phil, Â I can help you to fix this issue. Can you tell me the list of the files in the folder that is designed by the error? And in the parent folder, there should be a zip file with the same name, can you check if Pharo.exe is here and if the file list is the same? It will be nice if you can serialize the stack and send it to me / post it in a new github issue:https://github.com/pharo-project/pharo-launcher/issues .

April 16, 2018

Re: [Pharo-dev] Esteban's ChangeLog week of 9 April 2018

by Sean P. DeNigris

EstebanLM wrote > 13 April 2018â¦ I just promoted new VMs as stable. Weren't those reverted? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

April 16, 2018

Re: [Pharo-dev] [ANN] New VM stables promoted

by Sean P. DeNigris

Sean P. DeNigris wrote >> but you can always use vmLatest instead stable > Is anyone using vmLatest 32-bit on Mac for Pharo 6.1/7? Any problems? I > would like to upgradeâ¦ Bump :) I am eager to upgrade if save, but have some mission critical things I don't want interrupted. Thanks! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

April 16, 2018

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

by Eliot Miranda

Hi Phil, > On Apr 16, 2018, at 8:16 AM, philippe.back(a)highoctane.be <philippe.back(a)gmail.com> wrote: > > I guess that it is what I installed and it works fine on my Win 10 system. > > Nice icon BTW. > > Now there is an issue with the mouse pointer in the launcher and all pther images (so maybe a VM problem). > > The cursor is all black and tiny and has no white surroundings. In a dark theme the cursor is close to invisible. > > Also the cursor is not obeying the magnification setting of Windows. It worked before. > > > I guess that the cursor masks are not applied properly + other new stuff. Is the manifest (Pharo.exe.manifest ?) being installed? > > That is ruining the whole Pharo experience for me (and I guess newcomers). > > > Phil > >> On Mon, Apr 16, 2018, 16:14 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-dev] [Pharo-Launcher] call for tests on Windows

by philippe.back＠highoctane.be

I guess that it is what I installed and it works fine on my Win 10 system. Nice icon BTW. Now there is an issue with the mouse pointer in the launcher and all pther images (so maybe a VM problem). The cursor is all black and tiny and has no white surroundings. In a dark theme the cursor is close to invisible. Also the cursor is not obeying the magnification setting of Windows. It worked before. I guess that the cursor masks are not applied properly + other new stuff. That is ruining the whole Pharo experience for me (and I guess newcomers). Phil On Mon, Apr 16, 2018, 16:14 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

[Pharo-Launcher] call for tests on Windows

by Christophe Demarey

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-dev] File path encoding

by Ben Coman

>> On 16 Apr 2018, at 13:05, Ben Coman <btc(a)openinworld.com> wrote: >> >> On 16 April 2018 at 18:52, Ben Coman <btc(a)openinworld.com> wrote: >>> On 16 April 2018 at 17:51, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> Hi, >>>> >>>> Some people raise issues with file path encoding with non-ASCII characters. >>>> >>>> The following works fine for me (macOS, Pharo 7, using new File class): >>>> >>>> "works" >>>> >>>> (FileLocator temp / 'foo' , 'txt') writeStreamDo: [ :out | out << 'Les Ã©lÃ¨ves FranÃ§ais' ; crlf ]. >>>> >>>> (FileLocator temp / 'foo' , 'txt') readStreamDo: [ :in | in upToEnd ]. >>>> >>>> "works" >>>> >>>> (FileLocator temp / 'benoÃ®t' , 'txt') writeStreamDo: [ :out | out << 'Les Ã©lÃ¨ves FranÃ§ais' ; crlf ]. >>>> >>>> (FileLocator temp / 'benoÃ®t' , 'txt') readStreamDo: [ :in | in upToEnd ]. >>>> >>>> "works" >>>> >>>> (FileLocator temp / 'benoÃ®t') ensureCreateDirectory. >>>> >>>> (FileLocator temp / 'benoÃ®t' / 'benoÃ®t' , 'txt') writeStreamDo: [ :out | out << 'Les Ã©lÃ¨ves FranÃ§ais' ; crlf ]. >>>> >>>> (FileLocator temp / 'benoÃ®t' / 'benoÃ®t' , 'txt') readStreamDo: [ :in | in upToEnd ]. >>>> >>>> >>>> Can Linux/Windows users confirm that it works on their platform ? >>> >>> Thanks for attacking this. All three work on Windows 10 English locale. >>> I'd hope it wasn't different with French locale, but wait for a report on that. >>> >>> cheers -ben >> >> I unzipped a fresh download of http://files.pharo.org/platform/Pharo6.1-win.zip >> * into C:\Temp\Pharo6.1 >> and immediately copied that directory >> * into C:\Temp\Pharo6.1.benoÃ®t >> >> Double-clicking on Pharo.exe >> * in the former, opens Pharo an expected. >> * in the latter, does nothing. On 16 April 2018 at 19:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Ben, > > On my machine, macOS 10.13.4, > > $ pwd > /tmp/benoÃ®t > > $ curl get.pharo.org/70+vm | bash > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 100 3036 100 3036 0 0 38694 0 --:--:-- --:--:-- --:--:-- 38923 > Downloading the latest 70 Image: > http://files.pharo.org/get-files/70/pharo.zip > Pharo.image > Downloading the latest pharoVM: > http://files.pharo.org/get-files/70/pharo-mac-stable.zip > pharo-vm/Pharo.app/Contents/MacOS/Pharo > Creating starter scripts pharo and pharo-ui > > $ ./pharo Pharo.image printVersion > [version] 'Pharo7.0' 'Pharo-7.0+alpha.build.769.sha.244850d3ffc1b49ab716c8093f4bcd9af3917be6 (32 Bit)' > > $ ./pharo Pharo.image eval 'FileLocator image resolve' > File @ /private/tmp/benoÃ®t/Pharo.image > > And the UI version works too. > > So we're back at 'it is a Windows problem' (but maybe it is only visible on Windows). > > Can you see what is going on ? > > Technically, at the File (FilePlugin) level we seem to be able to handle paths with strange characters, even on Windows, but somehow, somewhere a bogus call is made during image startup. I tried logging the startup like this... WorkingSession >> runStartup: isImageStarting 'C:\Temp\StartupLog.txt' asFileReference writeStreamDo: [ :log | log nextPutAll: log className; flush. self runList: manager startupList do: [ :each | log nextPutAll: each printString; nextPutAll: String crlf; flush. each startup: isImageStarting ]. self executeDeferredStartupActions: isImageStarting ] which worked in the former and with the latter(benoÃ®t) nothing. But poking around I bumped into an interesting symptom. The following does nothing.... C:\Temp\Pharo6.1.benoÃ®t> pharo but the following successfully opens the Image... C:\Temp\Pharo6.1.benoÃ®t> pharo Pharo6.1.image Not sure where to go from there. Maybe needs a Windows Debug-VM, but I'm out of time for now. cheers -ben

April 16, 2018

Re: [Pharo-dev] File path encoding

by Sven Van Caekenberghe

> On 16 Apr 2018, at 14:51, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Sven, > > On 16 April 2018 at 13:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Technically, at the File (FilePlugin) level we seem to be able to handle paths with strange characters, even on Windows, but somehow, somewhere a bogus call is made during image startup. > > I'm not going to have time to look at this in the next few days, sorry. > > But I have a vague memory that some of the other primitives outside > FilePlugin don't add the "\\?\" prefix, so they possibly also don't do > wide character conversion. Then I hope some other Windows user/developer can have a look. Hell, I believe we got a few French people working on Pharo, n'est pas ? > Cheers, > Alistair >

April 16, 2018

Re: [Pharo-dev] File path encoding

by Alistair Grant

Hi Sven, On 16 April 2018 at 13:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Technically, at the File (FilePlugin) level we seem to be able to handle paths with strange characters, even on Windows, but somehow, somewhere a bogus call is made during image startup. I'm not going to have time to look at this in the next few days, sorry. But I have a vague memory that some of the other primitives outside FilePlugin don't add the "\\?\" prefix, so they possibly also don't do wide character conversion. Cheers, Alistair

April 16, 2018