February 2019 - Pharo-users

Re: [Pharo-users] Quality assistant

by Denis Kudriashov

Hi Hilaire Use following script to disable it: ClyCriticBrowserPlugin disable Ð¿Ñ, 15 ÑÐµÐ²Ñ. 2019 Ð³. Ð² 19:56, Hilaire <hilaire(a)drgeo.eu>: > So, no option to turn it off I guess? > > Hilaire > > Le 14/02/2019 Ã 12:03, Hilaire a Ã©crit : > > How to turn off the quality assitant in the calypso browser? > > > > I don't find anymore the option in the settings browser. > > -- > Dr. Geo > http://drgeo.eu > > > >

Feb. 15, 2019

Re: [Pharo-users] Stability of Pharo 7 vs 6?

by Hilaire

Depends on what you are doing, I guess. I am using the same P7 32bits image on linux since June 2018, but I am doing bare bone smalltalk, and I don't use iceberg. It could be the source of your problem as it is still new, or it could be the 64bits image/vm. You could give a try for the 32bits version for a few days.. Le 15/02/2019 Ã 12:11, Tim Mackinnon a Ã©critÂ : > Iâm not sure if this is born out by others - but Iâm finding that Pharo 7 is a bit less stable than Pharo 6 - Iâm seeing quite a few seg-faults where the vm dies and terminates - both when the image is left running for a while, but also in fresh images where I do an Iceberg load of my projects. Iâve also seen a lot of weird things like corrupted fonts and keyboard focus/cursor keys not working properly. -- Dr. Geo http://drgeo.eu

Feb. 15, 2019

Monticello diff between image and tonel repo

by Hilaire

Hi, I think I already report it but I still see this issue. From Monticello when I request changes between image and my tonel repo I got wrong diff report.Â It is a bit scarry. Will code be lost? You are not sure about what really change. Or do I misunderstand something? See screenshot Hilaire -- Dr. Geo http://drgeo.eu

Feb. 15, 2019

Re: [Pharo-users] im using pharo 7 with linux env. but cannot input korean.

by Hilaire

In your trad. chinese app were you able to key in chinese? A taiwanese friend of mine will be interested to know. Hilaire Le 15/02/2019 Ã 19:06, Sean P. DeNigris a Ã©critÂ : > Will you say more about your issue (e.g. steps to reproduce)? Make sure you > use a font that contains Korean characters. When I wrote a Chinese > (traditional) app, the default Pharo font did not and I had to change to > "Arial Unicode MS" -- Dr. Geo http://drgeo.eu

Feb. 15, 2019

Re: [Pharo-users] Quality assistant

by Hilaire

So, no option to turn it off I guess? Hilaire Le 14/02/2019 Ã 12:03, Hilaire a Ã©critÂ : > How to turn off the quality assitant in the calypso browser? > > I don't find anymore the option in the settings browser. -- Dr. Geo http://drgeo.eu

Feb. 15, 2019

Re: [Pharo-users] im using pharo 7 with linux env. but cannot input korean.

by Sean P. DeNigris

peter yoo wrote > cannot input korean. Will you say more about your issue (e.g. steps to reproduce)? Make sure you use a font that contains Korean characters. When I wrote a Chinese (traditional) app, the default Pharo font did not and I had to change to "Arial Unicode MS" ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 15, 2019

Iceberg working with forks - can it be easier?

by Tim Mackinnon

Hi guys - Iâve spent a few hours scratching my head trying to understand why some of my Pull Requests to a project I had forked kept showing my previous commits when I thought I was all caught up. It suddenly dawned on me, that when I had forked, and then done some work and then submitted a PR, and then applied it upstream that my fork is now no longer in sync with its upstream counterpart. Having not done this in ages, it took me a while to then realise I have to do some git stuff to get it back in sync e.g. (and I think Iâve got this right) git fetch upstream (or whatever name you gave it) Git checkout master Git merge upstream/master So I guess my question is - wouldnât it be helpful if this was a command in Iceberg? It seems quite common to fork a project (I think this is still recommended for pharo itself isnât it?) - and then at some point you need to catchup with that origin again? Or am I missing something? I guess lots of stuff can go wrong - but if it does - youâd still get the same problems on the command line. It just seems that for normal situations - it would be handy to run this straight in Pharo. Thoughts from the git experts? Tim

Feb. 15, 2019

im using pharo 7 with linux env. but cannot input korean.

by peter yoo

hello~.. im using pharo 7 with linux env. but cannot input korean. and.. already start shell script file open and add "--compositioninput". but any receive data from XIM(fcitx). who know for this issue? thanks. -- http://lookandwalk.com http://looknw.com | http://onionmixer.net peter yoo(Jonghwa Yoo). ROK

Feb. 15, 2019

Re: [Pharo-users] Stability of Pharo 7 vs 6?

by Sven Van Caekenberghe

I have been running Pharo 7.0[.1] for months on macOS 10.14.3 64-bit downloaded with ZeroConf and I have had no stability issues. I leave one or more images open going in and out of sleep on my MacBook Pro. I don't run full-screen, just semi-full-screen (Option-Click the green grow bullet, which leaves the menu bar visible). But YMMV, it all depends on what you are exactly doing. One (external) library, one different behaviour, one UI change can make a difference. > On 15 Feb 2019, at 12:11, Tim Mackinnon <tim(a)testit.works> wrote: > > Iâm not sure if this is born out by others - but Iâm finding that Pharo 7 is a bit less stable than Pharo 6 - Iâm seeing quite a few seg-faults where the vm dies and terminates - both when the image is left running for a while, but also in fresh images where I do an Iceberg load of my projects. Iâve also seen a lot of weird things like corrupted fonts and keyboard focus/cursor keys not working properly. > > From memory - I saw a lot less of this in Pharo 6 when I first moved to it. > > Possibly my usage is a bit different (although Iâm not sure) - but in all the cases above Iâm using OSX (HighSierra - so the same Mac OS as Pharo 6) - with the 64bit vm and running full screen. > > One thing that seems to help (but this is an early empirical observation) - if I save my image to a new name - this seems to help. So Iâm wondering if there might be something in the build process that has changed and is causing some sort of instability? > > I havenât done this long enough to really comment - but from all of the above, having a Pharo.1.image seemed to stop my problems. > > Possibly Iâve been unlucky - but of 7 images Iâve used in the last 2 weeks - 5 of them have had issues. I did notice that half of these images were the rc1 build 1436 setup (as I hadnât noticed that the blessed 7.0 stable image has a different version number (previously, the last builds in PL Pharo 7 development - was the stable version - unless work then went forward for a Pharo 7.1. I liked to nab the dev version so that I know the build number to report it. I now see the about Pharo in the image also lists this number). Also some of my images were retrieved via zeroConf in the terminal (again, not sure if this makes a difference - but did that a lot with P6 too). > > This isnât a complaint per se - as we need to move the platform forward and forge new approaches. So I really mention it to try and help diagnose the issues - or possibly understand if Iâm doing something weird. > > Tim

Feb. 15, 2019

Re: [Pharo-users] Stability of Pharo 7 vs 6?

by Alexandre Bergel

Personally, when I leave P7 open for a few hours, it slows down significantly. I have to save the image and open it back to not have any slug. Cheers, Alexandre http://bergel.eu > Le 15 fÃ©vr. 2019 Ã 08:11, Tim Mackinnon <tim(a)testit.works> a Ã©crit : > > Iâm not sure if this is born out by others - but Iâm finding that Pharo 7 is a bit less stable than Pharo 6 - Iâm seeing quite a few seg-faults where the vm dies and terminates - both when the image is left running for a while, but also in fresh images where I do an Iceberg load of my projects. Iâve also seen a lot of weird things like corrupted fonts and keyboard focus/cursor keys not working properly. > > From memory - I saw a lot less of this in Pharo 6 when I first moved to it. > > Possibly my usage is a bit different (although Iâm not sure) - but in all the cases above Iâm using OSX (HighSierra - so the same Mac OS as Pharo 6) - with the 64bit vm and running full screen. > > One thing that seems to help (but this is an early empirical observation) - if I save my image to a new name - this seems to help. So Iâm wondering if there might be something in the build process that has changed and is causing some sort of instability? > > I havenât done this long enough to really comment - but from all of the above, having a Pharo.1.image seemed to stop my problems. > > Possibly Iâve been unlucky - but of 7 images Iâve used in the last 2 weeks - 5 of them have had issues. I did notice that half of these images were the rc1 build 1436 setup (as I hadnât noticed that the blessed 7.0 stable image has a different version number (previously, the last builds in PL Pharo 7 development - was the stable version - unless work then went forward for a Pharo 7.1. I liked to nab the dev version so that I know the build number to report it. I now see the about Pharo in the image also lists this number). Also some of my images were retrieved via zeroConf in the terminal (again, not sure if this makes a difference - but did that a lot with P6 too). > > This isnât a complaint per se - as we need to move the platform forward and forge new approaches. So I really mention it to try and help diagnose the issues - or possibly understand if Iâm doing something weird. > > Tim

Feb. 15, 2019