January 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Corrupted fonts in P7 after loading Glamorous Toolkit

by Tim Mackinnon

It looks like this: And this: > On 25 Jan 2019, at 15:55, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - I just noticed that when I loaded the Glamorous toolkit and was playing around, when I went to look in the Pharo menus they are all corrupted (the odd character is some type of glyph). Opening a playground and doing some code completion shows that method names have the same random character glyphed. > > Anyone else seen this? Is is it something about loading GT? > > This is on OSX > > Tim

Jan. 25, 2019

Corrupted fonts in P7 after loading Glamorous Toolkit

by Tim Mackinnon

Hi - I just noticed that when I loaded the Glamorous toolkit and was playing around, when I went to look in the Pharo menus they are all corrupted (the odd character is some type of glyph). Opening a playground and doing some code completion shows that method names have the same random character glyphed. Anyone else seen this? Is is it something about loading GT? This is on OSX Tim

Jan. 25, 2019

Re: [Pharo-users] [VIDEO TUTORIAL] How to use external code editors to code in Pharo

by Tim Mackinnon

> On 25 Jan 2019, at 13:36, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > I think this feature is so convenient that it should not only be > visible, but have a menu item of its own. It did originally have a menu entry - however when PRâd I agreed with Denis to take it out as it kind of cluttered the context menu. The old Nautilus had a keystrokes menu that listed them all for you - but I think we have lost that in Calypso? There are some that appear in the settings, but Iâm not sure its all of them. Tim

Jan. 25, 2019

Re: [Pharo-users] macOS VM builds with AddressSanitizer/LeakSanitizer

by Manuel Leuenberger

Hi Ben, Thanks for the pointer, I subscribed to those two mailing lists as well. Cheers, Manuel > On 25 Jan 2019, at 14:25, Ben Coman <btc(a)openinworld.com> wrote: > > Hi Manuel, > > This level question would be better handled on pharo-dev and vm-dev mail lists (forwarded a copy). > http://lists.pharo.org/mailman/listinfo/pharo-dev_lists.pharo.org <http://lists.pharo.org/mailman/listinfo/pharo-dev_lists.pharo.org> > http://lists.squeakfoundation.org/mailman/listinfo/vm-dev <http://lists.squeakfoundation.org/mailman/listinfo/vm-dev> > > On Fri, 25 Jan 2019 at 16:09, Manuel Leuenberger <leuenberger(a)inf.unibe.ch <mailto:leuenberger@inf.unibe.ch>> wrote: > Hi, > > Anybody has experience building the VM (pharo.cog.spur) on macOS with custom compiler and flags? > > I am observing a memory leak on macOS Sierra/Pharo 7/GToolkit. I cannot precisely locate the issue, e.g. I cannot reliably reproduce the problem. So I tried to use AddressSanitizer/LeakSanitizer with custom debug builds of the VM and libMoz2D (used by GToolkit). As building on Linux is easier than on macOS, I got myself some help from a colleague and we managed to build those two artifacts on Linux by sprinkling "-g3 -O0 -fsanitize=leak -fsanitize-memory-track-origins" into the CFLAGS wherever they appear or are picked up. This works fine on Debian 9 with "CC=clang-6.0 CXX=clang++-6.0 ./mvm -d" and some on-the-fly patches for other breaking things. > > Unfortunately, I cannot reproduce the problem on Linux, so it seems to be platform specific. Even more so, I seem to be the only one observing the issue. Other GToolkit users do not report this issue. As these kind of issues are freaking me out, I cannot let go and need to learn what causes them. So, here I am, trying to build the VM on macOS Sierra and miserably failing to include the sanitizer tags with Clang and giving me those tasty leak reports on VM shutdown. > > The leak is not observable in the image memory, i.e. the image size reported by the VM is not growing, I am suspecting FFI, possibly in Moz2D, to leak. > The FFI registry in the VM also does not report many or large surviving objects, so I would assume the problem to be either on the plugin or VM side. > > My two concrete questions are: > 1. Is it even feasible to detect leaks with this approach? E.g., how does the VM behave on shutdown? Will the leaks show up in the report or will they not be covered, as the VM actually frees everything before shutting down? > 2. How do I swap compiler and inject flags on macOS builds? On Linux it was fairly easily done by replacing some variables. But on macOS, Xcode seems to like to mess with me. I got myself Clang-6.0 on macOS from MacPorts, the same as version as I took on Linux. I can build the VM with this, but it there is no leak report on VM shutdown. Anybody has an idea how to debug the build? > > Bonus question: Can the VM provide an inspectable view of all the allocated memory to the image? That would be perfect. I think Luke Gorrie does some magic like this in his Studio for core dumps etc. > > Cheers, > Manuel > >

Jan. 25, 2019

Re: [Pharo-users] [VIDEO TUTORIAL] How to use external code editors to code in Pharo

by Esteban Maringolo

El vie., 25 ene. 2019 a las 10:36, Esteban Maringolo (<emaringolo(a)gmail.com>) escribiÃ³: > > El vie., 25 ene. 2019 a las 8:01, Sven Van Caekenberghe > (<sven(a)stfx.eu>) escribiÃ³: > > > On 25 Jan 2019, at 11:34, Tim Mackinnon <tim(a)testit.works> wrote: > > > > Similarly, you might not also realise that can also use META-2 to intelligently select wider portions of code > > WOW, wow, very nice ! > But what key is "Meta-2" in Windows? Answering myself it is not "meta two" (as I read it), but is "Meta+2", which in Windows it is [Ctrl]+[2] Regards!

Jan. 25, 2019

Re: [Pharo-users] [VIDEO TUTORIAL] How to use external code editors to code in Pharo

by Esteban Maringolo

El vie., 25 ene. 2019 a las 8:01, Sven Van Caekenberghe (<sven(a)stfx.eu>) escribiÃ³: > > On 25 Jan 2019, at 11:34, Tim Mackinnon <tim(a)testit.works> wrote: > > Similarly, you might not also realise that can also use META-2 to intelligently select wider portions of code - which is great for refactoring or correcting a mistake (e.g. put your cursor inside a comment and press META-2). Repeatedly doing this will expand the selection (great inside a block of code). Again - this is the power of an intelligent environment. It also doesnât take a lot of code and it was something I taught myself because our environment is so discoverable. > > WOW, wow, very nice ! This is so convenient! In particular when dealing with nested blocks for rendering Seaside tags. :) But what key is "Meta-2" in Windows? I think this feature is so convenient that it should not only be visible, but have a menu item of its own. > There are so many hidden gems inside Pharo that it is impossible to keep track. People should not only add such features, but also continuously advocate/advertise them, it really takes a long time before everybody knows about new stuff. We need a cheatsheet of some sort :)

Jan. 25, 2019

Re: [Pharo-users] macOS VM builds with AddressSanitizer/LeakSanitizer

by Ben Coman

Hi Manuel, This level question would be better handled on pharo-dev and vm-dev mail lists (forwarded a copy). http://lists.pharo.org/mailman/listinfo/pharo-dev_lists.pharo.org http://lists.squeakfoundation.org/mailman/listinfo/vm-dev On Fri, 25 Jan 2019 at 16:09, Manuel Leuenberger <leuenberger(a)inf.unibe.ch> wrote: > Hi, > > Anybody has experience building the VM (pharo.cog.spur) on macOS with > custom compiler and flags? > > I am observing a memory leak on macOS Sierra/Pharo 7/GToolkit. I cannot > precisely locate the issue, e.g. I cannot reliably reproduce the problem. > So I tried to use AddressSanitizer/LeakSanitizer with custom debug builds > of the VM and libMoz2D (used by GToolkit). As building on Linux is easier > than on macOS, I got myself some help from a colleague and we managed to > build those two artifacts on Linux by sprinkling "-g3 -O0 -fsanitize=leak > -fsanitize-memory-track-origins" into the CFLAGS wherever they appear or > are picked up. This works fine on Debian 9 with "CC=clang-6.0 > CXX=clang++-6.0 ./mvm -d" and some on-the-fly patches for other breaking > things. > > Unfortunately, I cannot reproduce the problem on Linux, so it seems to be > platform specific. Even more so, I seem to be the only one observing the > issue. Other GToolkit users do not report this issue. As these kind of > issues are freaking me out, I cannot let go and need to learn what causes > them. So, here I am, trying to build the VM on macOS Sierra and miserably > failing to include the sanitizer tags with Clang and giving me those tasty > leak reports on VM shutdown. > > The leak is not observable in the image memory, i.e. the image size > reported by the VM is not growing, I am suspecting FFI, possibly in Moz2D, > to leak. > The FFI registry in the VM also does not report many or large surviving > objects, so I would assume the problem to be either on the plugin or VM > side. > > My two concrete questions are: > 1. Is it even feasible to detect leaks with this approach? E.g., how does > the VM behave on shutdown? Will the leaks show up in the report or will > they not be covered, as the VM actually frees everything before shutting > down? > 2. How do I swap compiler and inject flags on macOS builds? On Linux it > was fairly easily done by replacing some variables. But on macOS, Xcode > seems to like to mess with me. I got myself Clang-6.0 on macOS from > MacPorts, the same as version as I took on Linux. I can build the VM with > this, but it there is no leak report on VM shutdown. Anybody has an idea > how to debug the build? > > Bonus question: Can the VM provide an inspectable view of all the > allocated memory to the image? That would be perfect. I think Luke Gorrie > does some magic like this in his Studio for core dumps etc. > > Cheers, > Manuel > > >

Jan. 25, 2019

Re: [Pharo-users] [VIDEO TUTORIAL] How to use external code editors to code in Pharo

by eftomi

That's what I'm talking about! I doesn't have to be heavy resources, just a directed evolution What's the proverb? - The laziness is the greatest inventor Can you suggest any starting points to discover these background concepts for a novice like me? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 25, 2019

Re: [Pharo-users] [VIDEO TUTORIAL] How to use external code editors to code in Pharo

by Sven Van Caekenberghe

> On 25 Jan 2019, at 11:34, Tim Mackinnon <tim(a)testit.works> wrote: > > As an aside - we can all make the editing tools better (e.g. borrow things from VIM or Emacs) - I know I added a small feature in P7 (that possibly not many realise) where you can now click anywhere on message (and not have to highlight all of it) and browse senders/implementers (e.g. meta-M). This is made possible because our tools are not simply text (like VIM/Emacs) - you have the full AST at hand and can reason on the code and your cursor locations. > > Similarly, you might not also realise that can also use META-2 to intelligently select wider portions of code - which is great for refactoring or correcting a mistake (e.g. put your cursor inside a comment and press META-2). Repeatedly doing this will expand the selection (great inside a block of code). Again - this is the power of an intelligent environment. It also doesnât take a lot of code and it was something I taught myself because our environment is so discoverable. WOW, wow, very nice ! Thank you. There are so many hidden gems inside Pharo that it is impossible to keep track. People should not only add such features, but also continuously advocate/advertise them, it really takes a long time before everybody knows about new stuff.

Jan. 25, 2019

Re: [Pharo-users] [VIDEO TUTORIAL] How to use external code editors to code in Pharo

by Tim Mackinnon

> On 25 Jan 2019, at 09:24, eftomi <tomaz.turk(a)ef.uni-lj.si> wrote: > > When there is a question about editing the code, we can look for the > philosophies of other editors/IDEs. For instance, authors of VSCode are > saying <https://code.visualstudio.com/docs/editor/whyvscode <https://code.visualstudio.com/docs/editor/whyvscode>> "First and > foremost, it is an editor that gets out of your way. The delightfully > frictionless edit-build-debug cycle means less time fiddling with your > environment, and more time executing on your ideas." > > How far away from this idea is Pharo, if we compare both worlds? Pharo is an > OS, IDE, editor and a language - but can we make it to get out of our way in > the sense of developers' effort expectancy? We can of course argue about all of this for a long time - I think Sven nailed it though - people can do what they want (its OSS and its ours). You donât have to use the editor in Pharo and you can edit Tonel in a text editor and commit it via git (I have to confess, when messing around with a pet project hooked up to a GitLab CI system, this was convenient when using an iPhone on the train for quick tweaks to try out an idea without a laptop. I donât think I would want to program this way all the time though). HOWEVER - I donât think we have the resources necessary to do a great job of a traditional environment and an awesome job on a future looking environment (the latter being where we have the hearts and minds, and also really differentiate ourselves). Of course - if there are folks that are passionate enough to go away and do this really well - then I donât think anyone would stop them. BUT I wouldnât want to see some of our best resources spend time on this. I would like to improve the tools weâve got (Iâm loving the inspiration for the Feenk guys). I would prefer the we make our integrated editor better, as well as keep pressing on Calypso (its better but still needs more work), and keep improving git integration as well as the compiler and some of the reification of things that we keep doing. As an aside - we can all make the editing tools better (e.g. borrow things from VIM or Emacs) - I know I added a small feature in P7 (that possibly not many realise) where you can now click anywhere on message (and not have to highlight all of it) and browse senders/implementers (e.g. meta-M). This is made possible because our tools are not simply text (like VIM/Emacs) - you have the full AST at hand and can reason on the code and your cursor locations. Similarly, you might not also realise that can also use META-2 to intelligently select wider portions of code - which is great for refactoring or correcting a mistake (e.g. put your cursor inside a comment and press META-2). Repeatedly doing this will expand the selection (great inside a block of code). Again - this is the power of an intelligent environment. It also doesnât take a lot of code and it was something I taught myself because our environment is so discoverable. I do think we can extend Calypso to show code in a less confined way - I too am not so keen on seeing only one method or flipping between class/instance - but again our tools are malleable and great at exploring these ideas (and I believe the Calypso model actually supports this experimentation - but I will find out, as that is the itch I want to scratch next). Tim

Jan. 25, 2019