April 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [ANN] Prometheas : a Pharo wiki database

by Juraj Kubelka

Nice! Could you provide the database content using JSON REST API? We could then have this as a part of Help Browser. Cheers, Juraj -- Juraj Kubelka > El 14-04-2017, a las 09:30, Dimitris Chloupis <kilon.alios(a)gmail.com> escribiÃ³: > > Part of my Discord bot as a goal was to add the ability to create database entries so that people can quickly find documentation. > > It was quite a challenge for me because I had to learn how heroku works, PostgreSQL and all the other things but I did it!!! > > In any discord channel you have now 3 commands !doc , !docadd , !docremove > > 1) !doc <search_term> > search for a term in the documentation database > eg. !doc pharo > > 2) !docadd <search_term> <content> <tags> <links> > add a new entry to the documentation database > eg. !docadd "pharo" "Pharo is a modern implementation of Smalltalk" "{'smalltalk','live coding','language'}" "{'squeak','IDE'}" > > 3)!docremove <search_term> > remove a term from database > eg. !docremove pharo > > tags , is for more complex searches in the future, links for sending users to relevant documentation > > I am also planning to give access to pharo users to the database from inside the pharo image, if its easy enough to use PostgreSQL from inside Pharo. Currently the bot is fully coded in python. > > The goal is not to create a full documentation but rather quick help tips for fast pointing to the right direction. > > This is also an invite to experience pharo devs and newcomers to start adding to this database. > > The database is PostgreSQL , one of the most populars, I have nothing against MongoDB , its just that it works better with heroku where I host the database. But if in the future find a way to do it for free I can move to MongoDB, but no promises. > > Anyway this was an excuse for me to learn database programming that I had abandoned 25 years ago (DBASE). > > So have fun with this :)

April 15, 2017

best practices for using external files for testing

by Peter Uhnak

Hi, is there a common/best practice for using external files in tests? In my specific case I am interested in git-based projects, where I have a big (~1MB) file stored in repository and I would like to use it in my tests. For GitFileTree project I could presumably use the following to access it: 'OP-XMI' asPackage mcPackage workingCopy repositoryGroup remotes first directory / 'tests' / 'my-test-file.xmi' This will retrieve the MCPackage of the Package and then retireve where it the repo is actually stored on the disk. Are there better ways to do this? Could something similar be done with IceBerg? (p.s. in theory I could compile the entire file (e.g. 1MB) to a method, but that is very ugly to me) Thanks, Peter

April 15, 2017

Pharo 6.0 On windows crash while trying to run AthensFlakeDemo

by Ricardo Pacheco

I have been trying to run the AthensFlakeDemo in Pharo 6, updated as of today, in Windows 10 using this command: AthensFlakeDemo new openInWorld. Every time I run it, Pharo crashes. It looks to me like a bug, but before reporting a bug I want to ask you if I need to install/do something else prior to trying to run this demo. Thanks -- View this message in context: http://forum.world.st/Pharo-6-0-On-windows-crash-while-trying-to-run-Athens… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 15, 2017

Re: [Pharo-users] Pharo 6 snap install

by Luke Gorrie

On 15 April 2017 at 14:45, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > this belongs to pharo-dev, please continue there :) > Looks to me like I should make a small replacement for mvm that is for nix. Nix indeed does its own thing. The downside is that it's restricted: the build runs in a sandbox, can't touch the network, has to declare the sha256 of any dependencies that it needs. Nothing - not one byte - is allowed to change from one build to the next without being accounted for and that breaks the mvm script. On the plus side it will supply all of the dependencies, with exactly the expected version and exactly the expected build options, so that is less work for mvm to do i.e. the third-party stuff should be taken care of automatically. I'm taking a poke now. However, I must remind myself that this is a distraction, since I am trying to get a _stable_ VM for Pharo 5.0. Somehow I have been swept up in this enthusiasm for building the bleeding edge Pharo 6.0 VM that is not actually of any practical use to me :-) although it will be in the near future.

April 15, 2017

Re: [Pharo-users] Pharo 6 snap install

by Esteban Lorenzano

this belongs to pharo-dev, please continue there :) > On 15 Apr 2017, at 14:25, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > On Sat, Apr 15, 2017 at 02:14:26PM +0200, Luke Gorrie wrote: >> On 15 April 2017 at 11:53, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> (actually, I'm not sure why you're bothering since 6 should >> be out before the end of the month, but that's your choice :-)). >> >> >> I just want something stable and reasonably modern for running existing >> applications and building new ones. >> >> If that means waiting for Pharo 6.0 release then that is okay with me. >> >> >> The (V6) linux install relies on a number of bash scripts to launch pharo >> (bin/pharo, bin/pharo-ui and bin/pharo-vm/pharo). How are you producing >> these, or are you doing something else? >> >> >> Here is where those scripts are generated in the existing pharo-vm packaging: >> https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/pharo/vm/ >> build-vm.nix#L50-L70 > > Ahh, so Nix is doing its own thing, not using the ZeroConf scripts. > > >> (I didn't write the nix packaging code but I have volunteered to maintain it so >> if it's out of date then I should fix that.) > > It will be for V6. Esteban has changed the scripts to ensure that Pharo > versions of libraries are loaded (from memory)(this is also partly why I > would like to use the full build process). > > >> git clone https://github.com/pharo-project/pharo-vm.git <https://github.com/pharo-project/pharo-vm.git> >> git checkout <the stable code...> >> cd pharo-vm/opensmalltalk-vm/build.linux64x64/pharo.cog.spur/build >> ./mvm >> -- >> >> BTW: HEAD is currently eaf13db484ac87720d8454e66b5ce92f51c01036, and my >> experience is that it is significantly less stable than the latest >> binary, which is from 1c38b03fb043a2962f30f080db5b1292b5b7badb >> >> >> This is really the bleeding edge :-) both of those commits were pushed within >> the past three days! > > Yep, V6 is still in testing. :-) > > Cheers, > Alistair

April 15, 2017

Re: [Pharo-users] Pharo6 ombu-session files in pharo-local

by Stephane Ducasse

Yes this is what we want to do to help the deployment aspect of Pharo. But this is work in perspective. Once we will have something we will ask you to try and let us know if this is working for you. Laste year I started to check because I wanted a silent Pharo: no hidden writing on files but the changes got lost. On Sat, Apr 15, 2017 at 10:24 AM, Holger Freyther <holger(a)freyther.de> wrote: > Hi, > > as part of moving a test image from Pharo5 to Pharo6 I also noticed that > on each start a new "ombu-session" folder will be created (and never > cleaned up). For a server-side deployment this is quite unfortunate as I > want/need to use a fixed amount of disk space. > > I think Norbert has similar concerns with this feature. We are using > "image-launch" to run the image and then either > systemd|monit|runit|kubernetes will execute (and re-execute) image-launch. > So potentially many many folders are created and never used. > > On deployments with many images, it is rare to make online changes and > even more rare to try to recover them. Would it be possible to create the > underlying storage or disable it completely? > > > thank you > holger >

April 15, 2017

Re: [Pharo-users] How can I set the SmaccDebugParser in Moose

by Stephane Ducasse

John? How do we activate the Smacc debugger in moose? On Fri, Apr 14, 2017 at 10:36 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Not exactly sure how to do to it because I never used it. > From what I see in SmaCCParserDebugger>>handlesContext: if you have in > the stack a context created by SmaCCParser>>parse you should have a > 'SmaCCParser' button at the top right of the window. But maybe John can > provide you with more details. > > Cheers, > Andrei > > > On Fri, Apr 14, 2017 at 2:45 PM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> Andrei? >> Help? >> >> >> >> On Fri, Apr 7, 2017 at 3:14 PM, Stephane Ducasse <stepharo.self(a)gmail.com >> > wrote: >> >>> Hi >>> >>> I found the SmaCCParserDebugger and I found the debug menu in the Smacc >>> tool. >>> Now I get a GT and byteCode debugger but I do not find a way to make the >>> new debugger actif. >>> >>> Stef >>> >> >> >

April 15, 2017

Re: [Pharo-users] Pharo 6 snap install

by Alistair Grant

On Sat, Apr 15, 2017 at 02:14:26PM +0200, Luke Gorrie wrote: > On 15 April 2017 at 11:53, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > (actually, I'm not sure why you're bothering since 6 should > be out before the end of the month, but that's your choice :-)). > > > I just want something stable and reasonably modern for running existing > applications and building new ones. > > If that means waiting for Pharo 6.0 release then that is okay with me. > > > The (V6) linux install relies on a number of bash scripts to launch pharo > (bin/pharo, bin/pharo-ui and bin/pharo-vm/pharo). How are you producing > these, or are you doing something else? > > > Here is where those scripts are generated in the existing pharo-vm packaging: > https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/pharo/vm/ > build-vm.nix#L50-L70 Ahh, so Nix is doing its own thing, not using the ZeroConf scripts. > (I didn't write the nix packaging code but I have volunteered to maintain it so > if it's out of date then I should fix that.) It will be for V6. Esteban has changed the scripts to ensure that Pharo versions of libraries are loaded (from memory)(this is also partly why I would like to use the full build process). > git clone https://github.com/pharo-project/pharo-vm.git > git checkout <the stable code...> > cd pharo-vm/opensmalltalk-vm/build.linux64x64/pharo.cog.spur/build > ./mvm > -- > > BTW: HEAD is currently eaf13db484ac87720d8454e66b5ce92f51c01036, and my > experience is that it is significantly less stable than the latest > binary, which is from 1c38b03fb043a2962f30f080db5b1292b5b7badb > > > This is really the bleeding edge :-) both of those commits were pushed within > the past three days! Yep, V6 is still in testing. :-) Cheers, Alistair

April 15, 2017

Re: [Pharo-users] Pharo 6 snap install

by Luke Gorrie

On 15 April 2017 at 11:53, Alistair Grant <akgrant0710(a)gmail.com> wrote: > (actually, I'm not sure why you're bothering since 6 should > be out before the end of the month, but that's your choice :-)). > I just want something stable and reasonably modern for running existing applications and building new ones. If that means waiting for Pharo 6.0 release then that is okay with me. The (V6) linux install relies on a number of bash scripts to launch pharo > (bin/pharo, bin/pharo-ui and bin/pharo-vm/pharo). How are you producing > these, or are you doing something else? > Here is where those scripts are generated in the existing pharo-vm packaging: https://github.com/NixOS/nixpkgs/blob/master/pkgs/ development/pharo/vm/build-vm.nix#L50-L70 (I didn't write the nix packaging code but I have volunteered to maintain it so if it's out of date then I should fix that.) git clone https://github.com/pharo-project/pharo-vm.git > git checkout <the stable code...> > cd pharo-vm/opensmalltalk-vm/build.linux64x64/pharo.cog.spur/build > ./mvm > -- > > BTW: HEAD is currently eaf13db484ac87720d8454e66b5ce92f51c01036, and my > experience is that it is significantly less stable than the latest > binary, which is from 1c38b03fb043a2962f30f080db5b1292b5b7badb > This is really the bleeding edge :-) both of those commits were pushed within the past three days! I will take a look at the ./mvm script now.

April 15, 2017

Re: [Pharo-users] Pharo 6 snap install

by Alistair Grant

On Sat, Apr 15, 2017 at 09:53:49AM +0000, Alistair Grant wrote: > > If you just want to build a single V6 pharo executable (no scripts, > linux 64 bit in the example below): > > -- > #!/bin/bash > set -e > > git clone https://github.com/pharo-project/pharo-vm.git > git checkout <the stable code...> > cd pharo-vm/opensmalltalk-vm/build.linux64x64/pharo.cog.spur/build > ./mvm > -- And remembered that this will produce dragons, hopefully this will work: -- #!/bin/bash set -e git clone https://github.com/pharo-project/pharo-vm.git git checkout <the stable code...> cd pharo-vm ../genVersion.sh cd opensmalltalk-vm/build.linux64x64/pharo.cog.spur/build ./mvm -- where genVersion.sh is: -- #! /bin/bash echo "`cat opensmalltalk-vm/platforms/Cross/vm/sqSCCSVersion.h | opensmalltalk-vm/.git_filters/RevDateURL.smudge`" > opensmalltalk-vm/platforms/Cross/vm/sqSCCSVersion.h echo "`cat opensmalltalk-vm/platforms/Cross/plugins/sqPluginsSCCSVersion.h | opensmalltalk-vm/.git_filters/RevDateURL.smudge`" > opensmalltalk-vm/platforms/Cross/plugins/sqPluginsSCCSVersion.h -- In case the mailer does formatting: there are only two lines of code, each beginning with echo. Cheers, Alistair

April 15, 2017