- Pharo-users - lists.pharo.org

SystemVersion cleanup (or the return of the explicit build number) in latest Pharo 7

by Torsten Bergmann

Hi, as you all know Pharo 7 is built using sources from github and a new bootstrap process. The first Pharo 7 images [1] unfortunately were hard to distinguish - the initial problem was described in [2] Guille tried to address this by adding a build number again [3] but unfortunately he mixed it into the existing suffix of the class SystemVersion. There was also some other trouble afterwards: - the highestUpdate was still not set by the bootstrap process, which made some code unloadable (like Artefact who's config is checking if it is above a certain update number) - with Guilles fix the build number had to be parsed from the suffix string - one was still not able to distinguish 32/64 bit images - the SystemVersion class and the according tests were still ugly So I reviewed all this more deeply and cleaned SystemVersion as well as the tests while trying to stay as compatible as possible. Thanks a lot to Pavel and Esteban who helped me sorting things out, especially in git and the bootstrap process. How does it look now ==================== 1. Our system type is still called "Pharo" ;) SystemVersion current type -> 'Pharo' 2. we still continue with major and minor versioning (leaving out patch versions), so currently work is done for Pharo 7.0 SystemVersion current major -> 7 SystemVersion current minor -> 0 SystemVersion current majorMinorVersion -> 'Pharo7.0' 3. the identification string now has a "+" sign inside to separate the build meta informations following the given rule 10 from http://semver.org So the full image version now looks like this: SystemVersion current imageVersionString -> 'Pharo-7.0+alpha.build.168.sha.30fc9bbe79922877706ecd842f8aef6822cdcdd9 (32 Bit)' 4. the suffix is currently "alpha" and may be changed depending on release status SystemVersion current suffix -> 'alpha' 5. the build number is stored as an explicit ivar in SystemVersion now SystemVersion current build -> 168 Note that the build number is explicitly set during the bootstrap process from the outside and increased over time with each new build. It represents the CI build number of #development branch now, see [4] on CI server 6. the github SHA commit hash is accessible too: SystemVersion current commitHash -> '30fc9bbe79922877706ecd842f8aef6822cdcdd9' which corresponds in this case to the last commit in #development branch https://github.com/pharo-project/pharo/commit/30fc9bbe79922877706ecd842f8ae… 7. the version includes now also the 32/64 bit distinction: Pharo-7.0+alpha.build.168.sha.30fc9bbe79922877706ecd842f8aef6822cdcdd9 (32 Bit) or Pharo-7.0+alpha.build.168.sha.30fc9bbe79922877706ecd842f8aef6822cdcdd9 (64 Bit) Additionally ============ - the version is displayed in SystemReporter and the AboutBox (Screenshot attached), please use this to identify the image easily - the #highestUpdate is calculated dynamically with code in the image (but it is there only for compatibility reasons). SystemVersion current highestUpdate -> "70168" We might easily catch the 999 build mark now and then run into 71000 which might still be Pharo 7.0 instead of 7.1. (which means first two digits of update number will then NOT correspond to major/minor version anymore). So better avoid #highestUpdate as a meaningful number for loading code or other. - also note if you contribute with an own PR (in your own fork on github) the build number is the build number of you PR specific CI build. Once your PR is reviewed and merged it is the regular Pharo image build number again. - you can reuse SystemVersion for you own apps built on top of Pharo: "MyKillerApp-1.0+beta (64 Bit)" can be easily created with: (SystemVersion major: 1 minor: 0 suffix: 'beta') type: 'MyKillerApp'; yourself - if you report a bug on bugs.pharo.org it would be good to note down the full version of the image you used as found in the About box. This allows to better reproduce wrong behavior that only happens in a specific image Thanks T. [1] http://files.pharo.org/image/70/ [2] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2017-August/1309… [3] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2017-August/1310… [4] https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 5, 2017

Re: [Pharo-users] Brea wiki software

by H. Hirzel

Hello Offray Thank you for making the Brea wiki code available. I have read it and got some ideas out of it. My conclusion was that I do not have the capacity at the moment to continue working on it. So I went for Seaside though the library is large. It has a simple wiki as well. And with Pier are more elaborate version. Seaside is well documented. Regards Hannes On 9/6/17, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > Hi, > > > On 06/09/17 02:12, H. Hirzel wrote: >> So at the moment I am fine to get it up and running using a FossilRepo. >> Later on I will work on replacing it with a JSON data store. > > Please let me know if you need any permissions into the repository to > make JSON data store available in Brea. > >> >> On 9/6/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>> I understand that it makes a lot of sense to reuse the functions >>> implemented in the FossilRepo. >>> >>> Installation of the Fossil version control system seems to be very >>> simple, just put a single executable file into the pharo folder for >>> example >>> >>> https://fossil-scm.org/index.html/doc/trunk/www/index.wiki > > Yes. Fossil is simpler and self-contained. A lot of friendly and > powerful user experience without importing the external complexities of > other developer cultures, like the popular systems (*coff... Git). I use > the one provided by my package manager, but we have installed Fossil and > started to use in our workshops and is a lot easier to start being > productive without the almost always gratuitous extra complexities, > specially for non tekies. Fossil gives me and easy distributed wiki out > of the box. > >>> On 9/6/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>>> What I wanted to write is that the class FossilRepo is not included. >>>> >>>> And that the setup of the Teapot server should not be hidden in lazy >>>> initialisation method but made explicit with some methods in a method >>>> category called 'setup' or 'configuration'. > > Please update your ConfigurationOfBrea, which fixes this two issues. > >>>>> On 9/6/17, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> >>>>> wrote: >>>>>> Hi, Hannes, >>>>>> >>>>>> Sorry it took so long. >>>>> No problem. It was actually less than 14 days which is not long ..... >>>>> >>>>> :-) > > Despite of being just one week after I told you I would look at the > issue, because the first one I have not access to my computer, is kind > of a lot considering the good support times in this community (with rare > exceptions, like when I feedback GT Tools and get no response :-/). > > Cheers, > > Offray >

Oct. 5, 2017

Re: [Pharo-users] Deploying on Linux with LibC version < 2.15

by Holger Freyther

> On 5. Oct 2017, at 22:22, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > > Your instructions describes the steps for CentOS 6.x. Are they the > exact same steps for RHEL6? I don't have a RHEL subscription but I assumed they are similar but OBS even produces RHEL packages: https://download.opensuse.org/repositories/devel:/languages:/pharo:/stable/… > Also, I am trying this on a CentOS 6.0 virtual machine and I get this error : > > [centoslive@livecd test]$ yum-config-manager --add-repo > http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/C… > Loaded plugins: fastestmirror, refresh-packagekit > Usage: "yum-config-manager [options] [section] > > Command line error: no such option: --add-repo > [centoslive@livecd test]$ > > > Is there something else to install before? Not sure. Even the RHEL documentation mentions --add-repo exists. I assume you can download the .repo[1] file and put it in the right directory? holger [1] RHEL6: https://download.opensuse.org/repositories/devel:/languages:/pharo:/stable/… CentOS6: https://download.opensuse.org/repositories/devel:/languages:/pharo:/stable/…

Oct. 5, 2017

Re: [Pharo-users] Deploying on Linux with LibC version < 2.15

by Cyril Ferlicot

On 10/5/17, Holger Freyther <holger(a)freyther.de> wrote: > > Hi! > > > for a brief moment you really scared me. I thought you referred to RedHat > Linux 6 which was released in 1999 but you are referring to Red Hat > Enterprise Linux (RHEL). > > As it turns out we have "latest" (as soon as a commit is made to > pharo-vm.git) and hand curated "stable" (hand created source tarballs, > rebuilt from a git commit of opensmalltalk-vm) for RHEL6 and CentOS 6. > > CentOS 6.x: > > # Add the repo > $ yum-config-manager --add-repo > http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/C… > > OR (for stable): > > http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/C… > > # Install 32bit packages (with X11 dependency for *-ui or not) > > $ yum install pharo6-32-ui.i686 or pharo6-32.i386 > > # Install 64bit packages > > $ yum install pharo6-64-ui.x86_64 pharo6-64.x86_64 > > Thank you. Your instructions describes the steps for CentOS 6.x. Are they the exact same steps for RHEL6? Also, I am trying this on a CentOS 6.0 virtual machine and I get this error : [centoslive@livecd test]$ yum-config-manager --add-repo http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/C… Loaded plugins: fastestmirror, refresh-packagekit Usage: "yum-config-manager [options] [section] Command line error: no such option: --add-repo [centoslive@livecd test]$ Is there something else to install before? > > > > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Oct. 5, 2017

Re: [Pharo-users] Open Sourcing the Data Journalism Handbook with Grafoscopio

by Offray Vladimir Luna CÃ¡rdenas

Thanks Ben, Your words are encouraging as always. Is really worthy to count with people like you, that you care so much for the community and have always time for suggestions and support in several members projects and issues. Cheers, Offray On 05/10/17 08:50, Ben Coman wrote: > Great to hear every time your progress with this.Â That "Handbook > Hack" mentioned on the DJH site looks like a good place to promote > Grafoscopio. > > cheers -ben > > On Thu, Oct 5, 2017 at 10:14 AM, Offray Vladimir Luna CÃ¡rdenas > <offray.luna(a)mutabit.com <mailto:offray.luna@mutabit.com>> wrote: > > Upps... I copied and pasted parts of my original post in the Open > Knowedge Forum, so it seems that it got scrambled with some extra > information from there here. > > Anyway I hope the message is clear. > > Cheers, > > Offray > > > On 04/10/17 21:09, Offray Vladimir Luna CÃ¡rdenas wrote: >> >> Hi, >> >> Recently, in our local hackerspace <http://hackbo.co/>, we used, >> extended and adapted, Grafoscopio >> <http://mutabit.com/grafoscopio/index.en.html> to recreate the >> first open source version of the Data Journalism Handbook >> <http://datajournalismhandbook.org/>, in Spanish. Quoting from >> the project page: >> >> There are some interesting Free Cultural Works >> <http://freedomdefined.org/Definition> which are not open >> sourced. >> This means that, they are covered under pretty liberal licenses, >> allowing their remix, sale and modification, but the >> infrastructures >> which support the creation, modification and publishing of >> such works, >> donât allow wide participation and deep traceability of their >> history of >> such collective endeavors. >> >> This is our approach about alternative ways for creating such >> works, >> addressing the above problem, using the Data Journalism >> Handbook as an >> example (English <http://datajournalismhandbook.org/>, >> Spanish <http://interactivos.lanacion.com.ar/manual-data/>) >> and /pocket infrastructures/, which are simple, self >> >> contained, and work well on-line and off-line, like Fossil >> <http://fossil-scm.org/> and >> Grafoscopio <http://mutabit.com/grafoscopio/index.en.html>. >> Also we extended and adapted Grafoscopio, during this project, >> to make the tool suit the problem (and not the usual other >> way around). >> >> More information and downloadable files in the project source >> code repository: >> >> http://mutabit.com/repos.fossil/mapeda/ >> <http://mutabit.com/repos.fossil/mapeda/> >> >> This is also an example of the kind of books you can create now >> with/inside Grafoscopio (with Pandoc). >> >> And, of course, the customary screenshots: >> >> photo532578960227822324 >> >> photo5082366090373343168 >> >> Captura de pantalla del manual en Grafoscopio. >> >> >> Cheers, >> >> Offray >> >> > >

Oct. 5, 2017

Re: [Pharo-users] Open Sourcing the Data Journalism Handbook with Grafoscopio

by Ben Coman

Great to hear every time your progress with this. That "Handbook Hack" mentioned on the DJH site looks like a good place to promote Grafoscopio. cheers -ben On Thu, Oct 5, 2017 at 10:14 AM, Offray Vladimir Luna CÃ¡rdenas < offray.luna(a)mutabit.com> wrote: > Upps... I copied and pasted parts of my original post in the Open Knowedge > Forum, so it seems that it got scrambled with some extra information from > there here. > > Anyway I hope the message is clear. > > Cheers, > > Offray > > On 04/10/17 21:09, Offray Vladimir Luna CÃ¡rdenas wrote: > > Hi, > > Recently, in our local hackerspace <http://hackbo.co/>, we used, extended > and adapted, Grafoscopio <http://mutabit.com/grafoscopio/index.en.html> > to recreate the first open source version of the Data Journalism Handbook > <http://datajournalismhandbook.org/>, in Spanish. Quoting from the > project page: > > There are some interesting Free Cultural Works > <http://freedomdefined.org/Definition> which are not open sourced. > This means that, they are covered under pretty liberal licenses, > allowing their remix, sale and modification, but the infrastructures > which support the creation, modification and publishing of such works, > donât allow wide participation and deep traceability of their history of > such collective endeavors. > > This is our approach about alternative ways for creating such works, > addressing the above problem, using the Data Journalism Handbook as an > example (English <http://datajournalismhandbook.org/>, Spanish > <http://interactivos.lanacion.com.ar/manual-data/>) and *pocket > infrastructures*, which are simple, self > > contained, and work well on-line and off-line, like Fossil > <http://fossil-scm.org/> and > Grafoscopio <http://mutabit.com/grafoscopio/index.en.html>. Also we > extended and adapted Grafoscopio, during this project, > to make the tool suit the problem (and not the usual other way around). > > More information and downloadable files in the project source code > repository: > > http://mutabit.com/repos.fossil/mapeda/ > > This is also an example of the kind of books you can create now > with/inside Grafoscopio (with Pandoc). > > And, of course, the customary screenshots: > > [image: photo532578960227822324] > > [image: photo5082366090373343168] > > [image: Captura de pantalla del manual en Grafoscopio.] > > > Cheers, > > Offray > > > >

Oct. 5, 2017

Re: [Pharo-users] Deploying on Linux with LibC version < 2.15

by Holger Freyther

> On 5. Oct 2017, at 18:08, Bruce O'Neel <bruce.oneel(a)pckswarms.ch> wrote: > > Hi, Hi! > Well, our redhat 6.9 systems have 2.12, so, that qualifies. > > And yes, we still have RedHat 6, and 6.9 was released only 6 months ago! It will finish extended support in a mind-blowing 7 more years in 2024. > > Redhat 5, still supported for another 3 years till 2020 has glibc 2.5. for a brief moment you really scared me. I thought you referred to RedHat Linux 6 which was released in 1999 but you are referring to Red Hat Enterprise Linux (RHEL). As it turns out we have "latest" (as soon as a commit is made to pharo-vm.git) and hand curated "stable" (hand created source tarballs, rebuilt from a git commit of opensmalltalk-vm) for RHEL6 and CentOS 6. CentOS 6.x: # Add the repo $ yum-config-manager --add-repo http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/C… OR (for stable): http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/C… # Install 32bit packages (with X11 dependency for *-ui or not) $ yum install pharo6-32-ui.i686 or pharo6-32.i386 # Install 64bit packages $ yum install pharo6-64-ui.x86_64 pharo6-64.x86_64

Oct. 5, 2017

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by Ben Coman

Nice article. I like the way you've structured it and pushed the "updated" angle. I feel a bit too strong a claim is laid on Pharo producing the CogVM. Much of the Cog + Spur + 64bit VM work was originally done for Squeak with Pharo riding the coat-tails of that work. Lately Pharo community has been involved in improving VM with hotspot optimisation with Sista and moving towards making Pharo embeddable.. (@Clement, is "hotspot optimsation" fair as a short tagline for inter-language comparison?) So maybe say "the Pharo project has been involved in producing: ... * the 64-bit Spur/Cog VM (used also by Squeak, Cuis and Newspeak) * hotspot optimisation with Sista * working towards embedding Pharo as a game scripting language" (not sure on that last one) cheers -ben On Wed, Oct 4, 2017 at 6:30 PM, horrido <horrido.hobbies(a)gmail.com> wrote: > Behold Pharo: The Modern Smalltalk > <https://medium.com/smalltalk-talk/behold-pharo-the-modern- > smalltalk-38e132c46053> > > If you would like to suggest some edits, I'm all ears. Anything to improve > the impact of the article. > > Thanks. > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Oct. 5, 2017

Re: [Pharo-users] 6.1 Stable 64 - Crash when loading repository

by JuliÃ¡n Maestri

Sorry for the delay. $ uname -a Linux PC51 4.4.0-96-generic #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial On 4 October 2017 at 17:09, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hello Julian > > Thanks for the report. > on which OS are you? > > Stef > > On Wed, Oct 4, 2017 at 8:33 PM, JuliÃ¡n Maestri <serpi90(a)gmail.com> wrote: > > On a clean image from get.pharo.org/64/ > > Attempting to load the following repository > > > > Metacello new > > baseline: 'WillowBootstrap'; > > repository: 'github://ba-st/Willow-Bootstrap:master/source'; > > load. > > > > Consistently causes a VM crash (crash.dump in attatchment). > > > > This does not happen with the 32 bit image. > > > > Image + VM details > > > >> Image > >> ----- > >> /home/jmaestri/Pharo/workspace/Pharo.image > >> Pharo6.0 > >> Latest update: #60510 > >> Unnamed > >> Virtual Machine > >> --------------- > >> /home/jmaestri/Pharo/workspace/pharo-vm/lib/pharo/ > 5.0-201707201942/pharo > >> CoInterpreter VMMaker.oscog-eem.2254 uuid: > >> 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 > >> StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: > >> 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 > >> VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git > $ > >> Date: Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942 > >> https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > >> Unix built on Jul 20 2017 20:40:36 Compiler: 4.6.3 > >> VMMaker versionString VM: 201707201942 > >> https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Thu Jul > 20 > >> 12:42:21 2017 -0700 $ Plugins: 201707201942 > >> https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > >> CoInterpreter VMMaker.oscog-eem.2254 uuid: > >> 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 > >> StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: > >> 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 > > > > > > > > > >

Oct. 5, 2017

Re: [Pharo-users] SVG Icons

by Peter UhnÃ¡k

Hi, this is not really tested, but you can try to do the following (installation) a) install XMLParser from catalog b) in monticello browser open Pharo/Athens and load latest version of Athens-SVG package (usage) Then you import SVG XML using Converter and paint it on a surface, which you convert to Form. ``` contents := (ZnEasy get: 'https://s.cdpn.io/3/kiwi.svg') contents. xmlDoc := XMLDOMParser parse: contents. svg := AthensSVGConverter new importXMLDocument: xmlDoc. svg transform: 'scale(0.5)'. extent := 500 @ 500. surface := AthensCairoSurface extent: extent. surface drawDuring: [ :aCanvas | svg renderOn: aCanvas ]. surface asForm. ``` [image: Inline image 1] Peter On Thu, Oct 5, 2017 at 1:50 PM, Steven R. Baker <steven(a)stevenrbaker.com> wrote: > Heya folks! > > I need to load SVG images (for icons) in my application. I've searched > my 6.1 image for SVG, but haven't found anything. > > Is there a library for loading SVGs? I'd really like to get them > directly into instances of Form if possible, but I'm flexible. :) > > Thanks! > > -Steven > > > >

Oct. 5, 2017