- Pharo-users - lists.pharo.org

Re: [Pharo-users] Installing PharoJS

by Shaping

Thanks, Ben. From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Ben Coman Sent: Monday, 7 October, 2019 06:16 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] Installing PharoJS On Mon, 7 Oct 2019 at 09:57, Shaping <shaping(a)uurda.org <mailto:shaping@uurda.org> > wrote: File name or extension is too long, but length is 118, well under 260. Soâ¦. Failed to stat file? Is that supposed to be âstartâ? No. Its from the Cygwin stat() system call ... https://en.wikipedia.org/wiki/Stat_(system_call) cheer s-ben

Oct. 7, 2019

Re: [Pharo-users] Pharo: Git and GUI speed; JS widget reuse in PharoJS

by Shaping

I haven't used your latest "native widgets" (GTK) build, but as long as the UI isn't programmed to be as async as possible, then any non-UI related event will slowdown or micro-block the UI, causing the noticed latency. That's interesting. Yes, we need async updating without the microblocking dragging down the speed. Is the GTK build ready for testing now? I know I'm speaking the obvious to you here, but if you look at things like Android Architecture there is a lot to learn from, because mobile users expect significantly faster, non-blocking UIs that desktop, and not to mention web (although this is is changing too). It's a good point. Shaping

Oct. 7, 2019

Re: [Pharo-users] Installing PharoJS

by Shaping

Registry entries seem to specify directories for VMs and images after the Launcher is installed. These cause it to write the next image to the documents subdirectory instead of to the one into which I copied the initial Pharo directory contents, and then pointed the Launcher Settings to. Whatâs confusing is that we have, on the one hand, the installation directories in the registry, but, on the other, a potentially different set of folders in the 3 fields of Launcher Settings in an image (the Launcher image) that cannot be saved apparently. If someone knows a way to save it, please share. It warns you when you close, but there is no option for saving. There is the bigger issue of which set of folders becomes the reference structure of the install. The launcher image is not updating the registry entries. And I canât save the Launcher image anyway. In particular, there is no way to move sources.list to the new directory and reference it from Launcher Settings, without causing major breakage in the Launcher Settings window (directory field turns red with a big X). Can we make a more flexible installer? If someone knows how to make this move from the documents subfolder happen with the existing Launcher, please share the details. There is no way to specify where the initial install goes in the Launcher installer. It defaults to the userâs documents directory. -------------------- Correction length is 264. The debugger abbreviates the string with an ellipsis. Registry entry removes the 260-character limit. Not sure why this does not work: 'C:/Users/Crypto/Documents/Pharo/images/PharoJS in 7.0 64-bit/pharo-local/iceberg/bouraqadi/PharoJS/CordovaExamples/Counter/node_modules/cordova-ios/tests/spec/unit/fixtures/ios-config-xml/SampleApp/Images.xcassets/LaunchImage.launchimage/Default-568h(a)2x~iphone.png' size "264" Iâve installed PharoLauncher on the root of C. I need to move the images to the root too or to my RAID. Iâm not able to move the folder from documents to another drive with a shorter path, without doing folder surgery. Also, I donât see a way to save the launcher image after Iâve tweaked the settings to point to the new directories. Further when I specify the new directory, the specific image folder is moved (or regenerated) but no new /image folder is created. Do the new directory location does not reflect the old folder structure (in the user documents folder), and requires manual work to be synced. We probably donât want that. Is there a more convenient and reliable way to have Launcher just move all images and VMs to a new folder? -------------- File name or extension is too long, but length is 118, well under 260. Soâ¦. Failed to stat file? Is that supposed to be âstartâ? From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Christopher Fuhrman Sent: Sunday, 6 October, 2019 11:34 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] Installing PharoJS Hello, The screenshot cuts off the error, but it may be the problem with file names that are too long in libgit2. It's a controversial problem in libgit2 for at least six years. https://github.com/libgit2/libgit2/issues/1899 Hitting this problem is what drove me to install WSL on Windows 10 and use Pharo that way, effectively not using Windows 10 for Pharo. Other workarounds exist, including a short image name in the launcher, putting image folders at the root level, telling Pharo to put iceberg repos in a fixed directory closer to the root, etc. You want a way to prevent a Pharo file path that's longer than 260 chars. Cheers, Cris On Sun, Oct 6, 2019, 10:52 Shaping <shaping(a)uurda.org <mailto:shaping@uurda.org> > wrote: All you need to do is evaluating the following expression in a playground. I suggest you do it in a fresh image. Metacello new baseline: 'PharoJS'; repository: 'github://bouraqadi/PharoJS'; load That was one of the tests mentioned. See the screenshot below. The problem seems Git-related: Shaping On 6 Oct 2019, at 14:49, Shaping <shaping(a)uurda.org <mailto:shaping@uurda.org> > wrote: Hi. Can someone explain exactly how to install the latest version of PharoJS, and verify that the proedure really works? I've tried: 1) cloning the PharoJS repo in Pharo 8.0 with Iceberg, and get a Not Loaded final state for the repo. 2) loading into Pharo 7, 6.1, and 5 using Metacello new baseline: 'PharoJS'; repository: 'github://bouraqadi/PharoJS'; load All tries fail with a walkback. 3) loading into Pharo 4.0 using Gofer it smalltalkhubUser: 'noury' project: 'PharoJS'; addPackage: #ConfigurationOfPharoJS ; loadStable. The walkback here mentions missing dependency RBGlobalNode. Suggestions are welcome. Thanks. Shaping

Oct. 7, 2019

Re: [Pharo-users] JS charting widgets in PharoJS

by Noury Bouraqadi

I'm not aware of anyone doing it. Noury > On 7 Oct 2019, at 06:44, Shaping <shaping(a)uurda.org> wrote: > > Does anyone have experience with JS financial charting widgets like > > https://app.fintatech.com/demo <https://app.fintatech.com/demo> > > in PharoJS? > > > Shaping

Oct. 7, 2019

Re: [Pharo-users] Installing PharoJS

by Noury Bouraqadi

Some of my students reported similar errors with gitlib on Windows on other projects (not PharoJS). Removing spaces from the image name helps. Noury > On 7 Oct 2019, at 14:23, Shaping <shaping(a)uurda.org> wrote: > > Correction length is 264. The debugger abbreviates the string with an ellipsis. Registry entry removes the 260-character limit. Not sure why this does not work: > > 'C:/Users/Crypto/Documents/Pharo/images/PharoJS in 7.0 64-bit/pharo-local/iceberg/bouraqadi/PharoJS/CordovaExamples/Counter/node_modules/cordova-ios/tests/spec/unit/fixtures/ios-config-xml/SampleApp/Images.xcassets/LaunchImage.launchimage/Default-568h(a)2x~iphone.png' size "264" > > > Iâve installed PharoLauncher on the root of C. > > I need to move the images to the root too or to my RAID. > > Iâm not able to move the folder from documents to another drive with a shorter path, without doing folder surgery. Also, I donât see a way to save the launcher image after Iâve tweaked the settings to point to the new directories. Further when I specify the new directory, the specific image folder is moved (or regenerated) but no new /image folder is created. Do the new directory location does not reflect the old folder structure (in the user documents folder), and requires manual work to be synced. We probably donât want that. Is there a more convenient and reliable way to have Launcher just move all images and VMs to a new folder? > > > -------------- > File name or extension is too long, but length is 118, well under 260. Soâ¦. > > Failed to stat file? Is that supposed to be âstartâ? > > <image001.png> > > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Christopher Fuhrman > Sent: Sunday, 6 October, 2019 11:34 > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] Installing PharoJS > > Hello, > > The screenshot cuts off the error, but it may be the problem with file names that are too long in libgit2. > > It's a controversial problem in libgit2 for at least six years. https://github.com/libgit2/libgit2/issues/1899 <https://github.com/libgit2/libgit2/issues/1899> > > Hitting this problem is what drove me to install WSL on Windows 10 and use Pharo that way, effectively not using Windows 10 for Pharo. > > Other workarounds exist, including a short image name in the launcher, putting image folders at the root level, telling Pharo to put iceberg repos in a fixed directory closer to the root, etc. You want a way to prevent a Pharo file path that's longer than 260 chars. > > Cheers, > > Cris > > On Sun, Oct 6, 2019, 10:52 Shaping <shaping(a)uurda.org <mailto:shaping@uurda.org>> wrote: >> All you need to do is evaluating the following expression in a playground. >> I suggest you do it in a fresh image. >> >>> Metacello new >>> baseline: 'PharoJS'; >>> repository: 'github://bouraqadi/PharoJS'; >>> load >>> >> >> That was one of the tests mentioned. See the screenshot below. The problem seems Git-related: >> >> >> >> >> >> Shaping >> >> >>> On 6 Oct 2019, at 14:49, Shaping <shaping(a)uurda.org <mailto:shaping@uurda.org>> wrote: >>> >>> Hi. >>> >>> Can someone explain exactly how to install the latest version of PharoJS, >>> and verify that the proedure really works? >>> >>> I've tried: >>> >>> 1) cloning the PharoJS repo in Pharo 8.0 with Iceberg, and get a Not Loaded >>> final state for the repo. >>> 2) loading into Pharo 7, 6.1, and 5 using >>> >>> Metacello new >>> baseline: 'PharoJS'; >>> repository: 'github://bouraqadi/PharoJS'; >>> load >>> >>> All tries fail with a walkback. >>> >>> 3) loading into Pharo 4.0 using >>> >>> Gofer it >>> smalltalkhubUser: 'noury' project: 'PharoJS'; >>> addPackage: #ConfigurationOfPharoJS ; >>> loadStable. >>> >>> The walkback here mentions missing dependency RBGlobalNode. >>> >>> >>> Suggestions are welcome. >>> >>> Thanks. >>> >>> >>> Shaping >>>

Oct. 7, 2019

Re: [Pharo-users] Pharo: Git and GUI speed; JS widget reuse in PharoJS

by Noury Bouraqadi

> On 7 Oct 2019, at 05:12, Shaping <shaping(a)uurda.org> wrote: > > How does PharoJS deal with the JS reuse issue? There are lots of JS widgets out there that we would just like to use, but we donât want to read JS if we donât have to. There are many wheels to reinvent, or at least recode in DSL, if I understand the PharoJS scheme correctly, but I may not. > PharoJS allows to reuse existing JS libraries. Just reference constructors as you reference Pharo classes. Below is a link to an example, where we reuse the physics engine MatterJS https://pharojs.github.io/Demos/MatterJsDemo/ Noury

Oct. 7, 2019

Re: [Pharo-users] Installing PharoJS

by pmissech

On 07/10/2019 14:23, Shaping wrote: > > Correction length is 264.Â The debugger abbreviates the string with an > ellipsis.Â Â Â Registry entry removes the 260-character limit.Â Â Not > sure why this does not work: > > 'C:/Users/Crypto/Documents/Pharo/images/PharoJS in 7.0 > 64-bit/pharo-local/iceberg/bouraqadi/PharoJS/CordovaExamples/Counter/node_modules/cordova-ios/tests/spec/unit/fixtures/ios-config-xml/SampleApp/Images.xcassets/LaunchImage.launchimage/Default-568h(a)2x~iphone.png' > size "264" > > Iâve installed PharoLauncher on the root of C. > > I need to move the images to the root too or to my RAID. > > Iâm not able to move the folder from documents to another drive with a > shorter path, without doing folder surgery. Also, I donât see a way to > save the launcher image after Iâve tweaked the settings to point to > the new directories.Â Â Further when I specify the new directory, the > specific image folder is moved (or regenerated) but no new /image > folder is created.Â Do the new directory location does not reflect the > old folder structure (in the user documents folder), and requires > manual work to be synced.Â We probably donât want that.Â Is there a > more convenient and reliable way to have Launcher just move all images > and VMs to a new folder? > open settingsÂ (bottom left of the launcher) -Pharo Launcher settings --Locations of your images Â -> change the path Pierre

Oct. 7, 2019

Re: [Pharo-users] Installing PharoJS

by Shaping

Correction length is 264. The debugger abbreviates the string with an ellipsis. Registry entry removes the 260-character limit. Not sure why this does not work: 'C:/Users/Crypto/Documents/Pharo/images/PharoJS in 7.0 64-bit/pharo-local/iceberg/bouraqadi/PharoJS/CordovaExamples/Counter/node_modules/cordova-ios/tests/spec/unit/fixtures/ios-config-xml/SampleApp/Images.xcassets/LaunchImage.launchimage/Default-568h(a)2x~iphone.png' size "264" Iâve installed PharoLauncher on the root of C. I need to move the images to the root too or to my RAID. Iâm not able to move the folder from documents to another drive with a shorter path, without doing folder surgery. Also, I donât see a way to save the launcher image after Iâve tweaked the settings to point to the new directories. Further when I specify the new directory, the specific image folder is moved (or regenerated) but no new /image folder is created. Do the new directory location does not reflect the old folder structure (in the user documents folder), and requires manual work to be synced. We probably donât want that. Is there a more convenient and reliable way to have Launcher just move all images and VMs to a new folder? -------------- File name or extension is too long, but length is 118, well under 260. Soâ¦. Failed to stat file? Is that supposed to be âstartâ? From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Christopher Fuhrman Sent: Sunday, 6 October, 2019 11:34 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] Installing PharoJS Hello, The screenshot cuts off the error, but it may be the problem with file names that are too long in libgit2. It's a controversial problem in libgit2 for at least six years. https://github.com/libgit2/libgit2/issues/1899 Hitting this problem is what drove me to install WSL on Windows 10 and use Pharo that way, effectively not using Windows 10 for Pharo. Other workarounds exist, including a short image name in the launcher, putting image folders at the root level, telling Pharo to put iceberg repos in a fixed directory closer to the root, etc. You want a way to prevent a Pharo file path that's longer than 260 chars. Cheers, Cris On Sun, Oct 6, 2019, 10:52 Shaping <shaping(a)uurda.org <mailto:shaping@uurda.org> > wrote: All you need to do is evaluating the following expression in a playground. I suggest you do it in a fresh image. Metacello new baseline: 'PharoJS'; repository: 'github://bouraqadi/PharoJS'; load That was one of the tests mentioned. See the screenshot below. The problem seems Git-related: Shaping On 6 Oct 2019, at 14:49, Shaping <shaping(a)uurda.org <mailto:shaping@uurda.org> > wrote: Hi. Can someone explain exactly how to install the latest version of PharoJS, and verify that the proedure really works? I've tried: 1) cloning the PharoJS repo in Pharo 8.0 with Iceberg, and get a Not Loaded final state for the repo. 2) loading into Pharo 7, 6.1, and 5 using Metacello new baseline: 'PharoJS'; repository: 'github://bouraqadi/PharoJS'; load All tries fail with a walkback. 3) loading into Pharo 4.0 using Gofer it smalltalkhubUser: 'noury' project: 'PharoJS'; addPackage: #ConfigurationOfPharoJS ; loadStable. The walkback here mentions missing dependency RBGlobalNode. Suggestions are welcome. Thanks. Shaping

Oct. 7, 2019

Re: [Pharo-users] Pharo: Git and GUI speed; JS widget reuse in PharoJS

by Esteban Lorenzano

> On 7 Oct 2019, at 12:39, Shaping <shaping(a)uurda.org> wrote: > > I haven't seen is the instability of the VM you mention, it has worked pretty well for my average use, although the UX is not straightforward. > > Yes, lots of redirection and extra steps. Many degrees of freedom. Seemingly no good default âhappyâ path to simplify things a little before you start to investigate the variations/choices. > > > The other thing that keeps me planted firmly in VW is the sheer speed of it. > > I don't know if there are recent benchmarks, but I've felt Pharo to be really fast compared to VW when it comes to computing. > > Iâve donât plenty of informal comparative testing mostly with the GUI. Iâve used VW continuously for 29 years and Pharo on and off since 2006. (Iâm really trying to port, but I keep failing to do it; getting closer). VW is still noticeably quicker in GUI responsiveness, in most cases. One big difference is the Pharo HTTP client, with all those wonderful primitives. Itâs about twice as fast as VWâs. Bravo. I meant to tell that to Sven recently, and forgot. > > > Pharo looks generally much better, but itâs mushy, and thatâs a problem. VW is not. > > Working regularly with VW or VAST when I go back to Pharo the "mushiness" is significantly noticeable, but if you open a Pharo 3 image (or even Pharo 4) you'll feel it really "snappy", but of course you'll lose all the improvements since then; and that's the current tradeoff.â > > Yeah, I guess all the new slick GUIs are a bit heavier. This machine is just okay for speed â2.7 GHz Xeon, but VW feels okay. Pharo tends to put me slowly to sleep with the tiny but noticeable lags here and there. Iâm very fond of GT. Beautiful. Not sure what to do go get the GUI quickness back. Maybe you guys are waiting for the new GUI framework(s) to firm up? I tried Cuis, and was not impressed. Itâs too lean/Spartan and still not very fast (slower in some ways than Pharo). I like the Pharo creature-comforts (who wouldnât?). > > I never understood the reason for the incremental slowdown, it is even present in "modern" tools such as GTToolkit. > > Yes, itâs like a creeping disease. Lol > > Another thing I miss enough to want to implement (or fake-out somehow) is Alt-tabbing as a way to get around thru your browsers. Usually I have 4 to 6 up at once, if Iâm behaving, and as many as 20 if Iâm not. Looking about for the tabs at the bottom to click is not nearly as fun as Alt-Tabbing. Maybe I could emulate Alt-Tab with Alt-Shift-Tabâa bit of a finger twister, but it might work. > > > Gestural dynamics are very quick, well under 100 ms latency, often less than 20 ms. > > Iâm seeing 100, 150, and 200 ms regularly in Pharo. Itâs too mushy, and that slows the mind. > > Any developer understands this, whether he talks about it or not. > > This is true, below 20ms is ideal, and top-notch CLI terminals are benchmarking this as a selling point (using stuff like https://github.com/pavelfatin/typometer <https://github.com/pavelfatin/typometer>), Sublime, TextEdit, Notepad++ measure sub 10ms latency. > > Indeed. > > My whole nervous system definitely feels this speed effect and starts to thought-glide better below these tiny latencies. Iâm sure many reading this have had similar experiences. Something similar happens when you are fortunate enough to use a machine with extremely fast striped SSD drives, where you literally donât wait for anything, except the bloody internet. This doesnât just change the speed at which you do the work. It reorganizes your mind and skills in ways you had not anticipated because you can flow so much more quickly, making connections further forward and backward in your thought stream. My point is that if the speed and low-latencies are made a priority, we can attract users just on this basis alone. Even I would be working harder at improving Pharo (and complaining less) if everything were snappy. I would probably just get on with doing the needed tasks. Interesting how that works. Speed: it changes you. It changes the whole game. > > > So Iâm wondering when the Pharo GUI will snap as well as VW. > > Maybe with native widgets there will be a significant speedup, although I don't know whether the lag comes from rendering time or from something else. > > I would like to know more about the native widgets in Pharo. Does anyone know when this is likely to happen? I know, since Iâm doing it :) Native widgets (more like âgtk widgetsâ. This is technically just native under linux, but Gtk3 works very well both in Windows and Mac (you just has to ship it) will be available for development in Pharo 8. Now, moving the whole Pharo into it will take a bit longer, and we hope to be able to have a âPharo Gtk experienceâ for Pharo 9 (lots of tools to migrate to Spec2). Esteban > > But VW event model is not better than Pharo's, so it might be something else. > > Iâve not looked into the details, but I will sometimes just repeatedly click on a method name and watch how long the code pane takes to render in VW and Pharo, and I donât get what Pharo could be doing to make that time so long. Both are indexing into the sources file or the changes file to get some text, and then there is the TT-font rendering, which is probably where the CPU cycles are going. I should look into if further, but Iâm sure someone reading this knows enough about the rendering path to say where the bottleneck is. > > > Cheers, > > Shaping

Oct. 7, 2019

Re: [Pharo-users] Installing PharoJS

by Ben Coman

On Mon, 7 Oct 2019 at 09:57, Shaping <shaping(a)uurda.org> wrote: > File name or extension is too long, but length is 118, well under 260. > Soâ¦. > > > > Failed to *stat* file? Is that supposed to be âstartâ? > No. Its from the Cygwin stat() system call ... https://en.wikipedia.org/wiki/Stat_(system_call) cheer s-ben

Oct. 7, 2019