- Pharo-users - lists.pharo.org

SystemVersion cleanup (or the return of the explicit build number) in latest Pharo 7
by Torsten Bergmann Oct. 5, 2017

Oct. 5, 2017

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…

1 0

Open Sourcing the Data Journalism Handbook with Grafoscopio
by Offray Vladimir Luna CÃ¡rdenas Oct. 5, 2017

Oct. 5, 2017

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: photo532578960227822324 photo5082366090373343168 Captura de pantalla del manual en Grafoscopio. Cheers, Offray

2 3

6.1 Stable 64 - Crash when loading repository
by JuliÃ¡n Maestri Oct. 5, 2017

Oct. 5, 2017

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

2 2

Pharo Launcher Source
by Steven R. Baker Oct. 5, 2017

Oct. 5, 2017

Heya, I'm trying to build a Pharo Launcher of my own, but I can't find the code. This says it's on SmalltalkHub: https://github.com/pharo-project/pharo-launcher, but the link doesn't show anything. I tried looking on CI for the build script, but I can't find the build script, just build results. What I'm looking for is how to check out, build, and run Pharo Launcher from scratch. Can someone help me with this? Thanks! -Steven

3 3

Reading a text file line by line
by Dirk Olmes Oct. 5, 2017

Oct. 5, 2017

Hi, I'm trying to get started with Pharo doing something really simple - at least that's what I thought ... I'm trying to read a text file line by line. If I use File named: '/tmp/linex.txt' readStream nextLine I'll get a debugger telling me that BinaryFileStream does not understand nextLine. Now I've tried my best to find a stream that may be reading plain text lines but to no avail ... Help! -dirk

6 15

[Demo] Creating Bloc widgets: A Color Panel
by Stephan Eggermont Oct. 5, 2017

Oct. 5, 2017

Bloc is ready for your experiments. Here is my second one. Please let me know what and how to improve. Bloc allows for the easy creation of beautiful widgets. Here is a simple color panel that allows custom colors to be added (using the current Morphic color selector dialog) and allows colors to be applied using drag-and-drop. https://vimeo.com/236419682 Stephan

2 1

Pharo 7 license question
by Jimmie Houchin Oct. 4, 2017

Oct. 4, 2017

Hello, Pharo 7 to my understanding fundamentally changes Pharo. It is my understanding that Pharo 7 starts with a core Pharo kernel and like many languages out there, imports or adds code from a variety of external sources to the image being built. With that understanding, I am curious if that would allow for inclusion of a specific library/module to be licensed as GPL? And it not affect the other code in the composed image? I am a big believer in the MIT/BSD license and not a big fan of the GPL. However, there is software out there that I have avoided looking at the source code or attempting to port it to Pharo because it is GPL. I would sincerely love if I could now port such a library and license it under the GPL as required, and it not affect any other code outside of that specific library. I am not a lawyer. Nor do I know any lawyers. Is is possible for someone to get a reasonably definitive answer on this question? I am sure I am not the only one who has had this desire. I am also sure that I am not the only one who will have this question in the future. So it would be nice to have a proper legal response that could possibly be explicitly stated somewhere on the website or on an FAQ or something. Regardless of the answer, yes or no. It does need to be a settled issue for Pharo. That way someone could know if GPL/LGPL or whatever software could be in the catalog. Just wanted to put that out there to the community. I look forward to the answer, should one be or become available. Thanks. Jimmie

13 41

execute a code block at a given time in pharo ?
by Daniel BLANC Oct. 4, 2017

Oct. 4, 2017

Hi All, I'm a very beginner with smalltalk. I am building a small seaside app for controlling wifi access of my teenagers kids. In this app I need to start or stop the wifi acces at a given time. For the moment I'm doing it with an infinite loop in a process, with this code: WifiController >> startScheduler ^ SchedulerProcess ifNil: [ SchedulerProcess := [ [ true ] whileTrue: [ self schedulerApplyAutoStartStopRules. 56 seconds wait ] ] forkNamed: 'DanWifiManagerScheduler' ] I'm wondering if there is a way to do this without this infinite loop ? May be there is a class in the standard pharo image that can execute a code block at a given time ? Thanks, Daniel

5 8

Iceberg and proxy
by Vitor Medina Cruz Oct. 4, 2017

Oct. 4, 2017

Hello! Iceberg donât work behind a proxy? I have made proper proxy configuration, if I use Zinc, for example, the proxy information is used, but that donât seems to be the case for Iceberg. Regards, Vitor

4 16

"Leaking" CommandLineHandler when running headless image
by Holger Freyther Oct. 3, 2017

Oct. 3, 2017

Hi, I am currently trying to run one of my images as non-root and related to that look into keeping changes in a different directory or not writing them at all. While looking at a write failure I saw some paths being logged that I used during CI to load code and should have been GCed. Observation: Pharo --headless My.image eval "Smalltalk garbageCollect. CommandLineHandler allSubInstances size" 84 Pharo --headfull My.image eval "Smalltalk garbageCollect. CommandLineHandler allSubInstances size" 2 As part of the CommandLineHandler allSubInstances there are eight LoadUpdatesCommandLineHandler still active. I would assume that a full GC should have collected them by now (some of them being created in May). In a headfull image they disappear quickly I varied the execution a bit: Pharo --headless RoamingHub.image eval --no-quit "[ Smalltalk garbageCollect. FileStream stdout print: CommandLineHandler allSubInstances size; lf. Smalltalk snapshot: false andQuit: true] fork" 0 Hypothesis: * Command line handlers call >>#snapshot:andQuit:. * Image resumes in this process * New session created * Command line handlers execute * Calls snapshot:andQuit: * Image resumes.. * New session created * Command line handlers execute ... Can this be true? I think the proposal to start the image differently would help here? Any comments/ideas? holger

4 3