On 13 April 2018 at 17:07, Benoit St-Jean via Pharo-users < pharo-users@lists.pharo.org> wrote:
---------- Forwarded message ---------- From: Benoit St-Jean <bstjean@yahoo.com> To: Any question about pharo is welcome <pharo-users@lists.pharo.org>, Esteban Lorenzano <estebanlm@gmail.com> Cc: Bcc: Date: Fri, 13 Apr 2018 09:07:16 +0000 (UTC) Subject: Re: [Pharo-users] Where do we go now ? "You cannot take an alpha version and expect production quality."
I'm on Windows 10, using Pharo 7.0 alpha 32 bit.
Can I at least expect to be able to save code in my local Monticello repository ? It bombs. I just reported a bug!
Can I expect the Windows installer for Pharo Launcher to work on Windows? It doesn't : it crashes.
It works fine for me on Windows 10. There were some issues that depended on how PharoLauncher was installed. The installer (NSIS) being used at that time doesn't handle non-Admin installs very well. Prior to PharoLauncher being promoted as the main download, I guess people on Windows using PharoLauncher either ran it as Admin, or worked around it like me - on Windows I would just roll my own from a fresh Pharo 6 and the Project Catalog. To be clear, the problem was heavily influenced by the constraints of an external tool. Get PharoLauncher installed in the right location and it works like a dream. Did you try the proof-of-concept installer I posted previously to the list... http://www.mediafire.com/file/3g579bmzqspt8e1/BCPharoLauncher.msi
Can I expect Pharo Launcher (not installed from the .exe installer) to work on Windows? It just doesn't. I get all kinds of error related to WindowsStore, bad UTF-8 encoding and other things... (see https://twitter.com/smalltalkdev/status/978973863332798464)
Yes most people can expect it works perfectly on Windows. But as always it depends. There is always the chance something in your environment triggers a bug. like maybe non-ascii characters in you username/path?
Can I expect that when looking for implementors of a method things still work? I get duplicates (see attached file).
Do you mean only the duplicate "Traited class >> isTrait" in your screenshot? I just tried this in "Pharo-7.0+alpha.build.762.sha.0e0fe47c5ccef" by typing "isTrait" into the Playground, selecting it and pressing Ctrl-M, and I don't get the duplicate. Which build of Pharo are you using?
Can I expect reading input from the console to work on Windows? It doesn't.
Bit hard to understand your problem from that one-liner.
Can I expect to be able to test my stuff on Windows? That's kinda hard when Windows is always 6 months to 1 year behind VM-wise.
I'm not whining about the effort people put into this project : I'm mostly
whining about duplication of effort and code and *very poor* Windows support...
AFAIK, Pharo 6.1 32-bit VM is up to date with the other platforms. Regarding 64-bit Windows. Yes it is behind. The specific companies interested in 64-bit Linux support put money on the table to get it done. No one has stepped up to do the same for Windows 64-bit, so realistically it lags behind. btw, lately it gets harder to run 32-bit apps on Linux and OSX, but there is no reason to stop using 32-bits VM on Windows.
Can I expect to be able to contribute ? That is kinda sad but all the cool scripts out there are .sh files.
huh?
Just spend 2 weeks working with Pharo on Windows. You can start with version 5.1 if you want and let me know how it goes... Brace yourself, I'm telling you, you're off for a wild & unpleasant ride.
Its been a while since I worked with Pharo on Windows, but I've been using it the last few weeks with no problems. Pharo 6.1 and Pharo 7. cheers -ben
"To be clear, the problem was heavily influenced by the constraints of an external tool.Get PharoLauncher installed in the right location and it works like a dream.Did you try the proof-of-concept installer I posted previously to the list... http://www.mediafire.com/file/3g579bmzqspt8e1/BCPharoLauncher.msi " Downloaded it. Installed it. Started it. Selected an image. Bam. The app vanished. Also tried on a brand-new-and-fresh-Windows-10-machine-with-nothing-previously-installed and same thing. The app doesn't even show in the task manager. And no error file was created. If that helps, both machines have Windows in French installed. ----------------- 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 16 April 2018 at 02:52, Benoit St-Jean <bstjean@yahoo.com> wrote:
"To be clear, the problem was heavily influenced by the constraints of an external tool. Get PharoLauncher installed in the right location and it works like a dream. Did you try the proof-of-concept installer I posted previously to the list... http://www.mediafire.com/file/3g579bmzqspt8e1/BCPharoLauncher.msi "
Downloaded it. Installed it.
What path did you install to? cheers -ben
Started it. Selected an image. Bam. The app vanished.
Also tried on a brand-new-and-fresh-Windows-10-machine-with-nothing-previously-installed and same thing.
The app doesn't even show in the task manager.
And no error file was created.
If that helps, both machines have Windows in French installed.
"What path did you install to?" The installer put it in: C:\Users\Benoît St-Jean\AppData\Local\Programs\Pharo\BCPharoLauncher> ----------------- 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 16 April 2018 at 06:02, Benoit St-Jean <bstjean@yahoo.com> wrote:
"What path did you install to?"
The installer put it in:
C:\Users\Benoît St-Jean\AppData\Local\Programs\Pharo\BCPharoLauncher>
To work around the special character in your path, try copying that whole folder to C:\BCPharoLauncher and directly double-click Pharo.exe. Then click the Settings tool icon and change the Image & VM paths. Hopefully that will get you going for now, until we sort out a proper fix. cheers -ben
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. Peter On Mon, Apr 16, 2018 at 3:39 AM, Ben Coman <btc@openinworld.com> wrote:
On 16 April 2018 at 06:02, Benoit St-Jean <bstjean@yahoo.com> wrote:
"What path did you install to?"
The installer put it in:
C:\Users\Benoît St-Jean\AppData\Local\Programs\Pharo\BCPharoLauncher>
To work around the special character in your path, try copying that whole folder to C:\BCPharoLauncher and directly double-click Pharo.exe. Then click the Settings tool icon and change the Image & VM paths.
Hopefully that will get you going for now, until we sort out a proper fix.
cheers -ben
On 16 April 2018 at 16:55, Peter Uhnák <i.uhnak@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" cheers -ben
On Mon, Apr 16, 2018 at 12:30 PM, Ben Coman <btc@openinworld.com> wrote:
On 16 April 2018 at 16:55, Peter Uhnák <i.uhnak@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)
On 17 April 2018 at 00:11, Peter Uhnák <i.uhnak@gmail.com> wrote:
On Mon, Apr 16, 2018 at 12:30 PM, Ben Coman <btc@openinworld.com> wrote:
On 16 April 2018 at 16:55, Peter Uhnák <i.uhnak@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
Ben Coman wrote
I *prefer* never to close PharoLauncher.
That's the way I work as well, especially because I found that on Mac apparently you have to close all open images before Launcher will open again from the Dock. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
sean I do not have this behavior. I can use the launcher to open multiple images from the launcher. On Tue, Apr 17, 2018 at 1:00 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:
Ben Coman wrote
I *prefer* never to close PharoLauncher.
That's the way I work as well, especially because I found that on Mac apparently you have to close all open images before Launcher will open again from the Dock.
----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
A while ago I experienced similar behavior, but I'm not on Mac at the moment. Maybe it depends on OS version? cheers -ben On 19 April 2018 at 04:35, Stephane Ducasse <stepharo.self@gmail.com> wrote:
sean
I do not have this behavior. I can use the launcher to open multiple images from the launcher.
On Tue, Apr 17, 2018 at 1:00 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:
Ben Coman wrote
I *prefer* never to close PharoLauncher.
That's the way I work as well, especially because I found that on Mac apparently you have to close all open images before Launcher will open again from the Dock.
----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
I'm in 10.12.6 On Wed, Apr 18, 2018 at 11:34 PM, Ben Coman <btc@openinworld.com> wrote:
A while ago I experienced similar behavior, but I'm not on Mac at the moment. Maybe it depends on OS version?
cheers -ben
On 19 April 2018 at 04:35, Stephane Ducasse <stepharo.self@gmail.com> wrote:
sean
I do not have this behavior. I can use the launcher to open multiple images from the launcher.
On Tue, Apr 17, 2018 at 1:00 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:
Ben Coman wrote
I *prefer* never to close PharoLauncher.
That's the way I work as well, especially because I found that on Mac apparently you have to close all open images before Launcher will open again from the Dock.
----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
participants (5)
-
Ben Coman -
Benoit St-Jean -
Peter Uhnák -
Sean P. DeNigris -
Stephane Ducasse