April 2015 - Pharo-dev - lists.pharo.org

Aconcagua: 3 Repos on StHub
by Sean P. DeNigris April 24, 2015

April 24, 2015

Maxi confirmed that http://smalltalkhub.com/#!/~maxi/Aconcagua is canonical, but there is also http://smalltalkhub.com/#!/~BenoitAtruc/Aconcagua and http://smalltalkhub.com/#!/~HernanWilkinson/Aconcagua. Anyone know why the other two? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Aconcagua-3-Repos-on-StHub-tp4821715.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

1 0

Please Review 15395 ASAP
by Sean P. DeNigris April 24, 2015

April 24, 2015

If someone can review this quickly, there are a ton of packages touched as you can see below and I don't want to keep redoing the slice!!! Fix in inbox: SLICE-Issue-15395-Cleanup-1-SeanDeNigris.1 Various cleanups - most notable is applying the "a >= b and: [a <= c]" -> "a between: b and: c" everywhere; also fix typos in comments, etc. Dependencies: AsmJit-Extension-SeanDeNigris.9, AsmJit-Operands-SeanDeNigris.15, Balloon-SeanDeNigris.119, Collections-Native-SeanDeNigris.10, Collections-Sequenceable-SeanDeNigris.193, Collections-Streams-SeanDeNigris.169, FreeType-SeanDeNigris.698, Graphics-Primitives-SeanDeNigris.158, Kernel-SeanDeNigris.2014, Morphic-Widgets-List-SeanDeNigris.16, Morphic-Widgets-Pluggable-SeanDeNigris.45, Morphic-Widgets-Tree-SeanDeNigris.28, Morphic-Widgets-Windows-SeanDeNigris.48, Multilingual-OtherLanguages-SeanDeNigris.13, Network-UUID-SeanDeNigris.30, RPackage-Core-SeanDeNigris.384, System-Platforms-SeanDeNigris.62, System-Support-SeanDeNigris.1096, Text-Core-SeanDeNigris.32 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Please-Review-15395-ASAP-tp4821695.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 2

Playground and its current usability in Pharo4.0 Latest update: #40307
by Torsten Bergmann April 24, 2015

April 24, 2015

While I like that GTTools are in Pharo 4 now (thanks!!!) and allow all kind of neat things I basically ask myself if we forgot to remember usability on a few places: 1. the world menu item "Workspace" opens a window "Playground" including also a tab with the same name "Playground". => CONFUSING I would suggest that we rename the window "Workspace" and keep "Playground" for the initial tab. This is easy to fix and would also fulfill the expectation when a beginner grabbed an existing Smalltalk or Pharo book. 2. While in all UI interfaces (Windows, Linux, Mac) the order in the context menu is "Cut", "Copy", "Paste" the playground menu uses a different order "Copy", "Cut" "Paste". => CONFUSING again I would suggest to use the well known order "Cut","Copy","Paste". 3. When one uses "Inspect it" from the context menu it means - to run the code - and the resulting object is then "inspectable" in a new window On the other side "Do it and go" from the context menu means - to run the code - and the resulting object is then "inspectable" in a new pane (but same window) The intention of both menu items and also the result is the same, but the naming is different ("go" vs. "inspect"). But the only notable difference is that in one case the inspectable object is opening right to the existing pane in the other case a new window is opened. => CONFUSING and inconsistent This is harder to solve. Possible solutions are: 3a. We keep the "inspect" concept and name the menu items "Do and Inspect it" and "Inspect in new window" 3b. We keep "Do it" as before to run the code, also "Inspect it" which opens the new pane to the left in the same window. If someone wants to open a new inspector window he should keep SHIFT key pressed while running "Inspect it". This is a concept known from web browsers and other tools today, clicking on a link while pressing SHIFT opens a new window. 4. The icons in the context menu of Playground are not the same as the ones in the Pharo browsers. => CONFUSING and inconsistent They are just black and if one switches to the Pharo dark theme they stay black and therefore looking ugly and make nearly no sense on the dark grey menu background. For now we should use the known icons that we already have. Maybe currently they are hardcoded and may conflict with Moose vs. Pharo icons - but this could be solved with the Icon Theming. (In the long term I would like to see scalable icons in Pharo menues (instead of bitmaps) similar to "Fontawesome" in web browsers (two colors) or SVG based ones (more colors) as currently the icon does not scale when changing the menue font size). Sorry if it sound like a rant - but the intention of this mail is that we discuss (and hopefully fix) in order to improve. Maybe it is written too early after the initial integration, but I think the mentioned points should be easy to address. Unfortunately I'm additionally confused with the changed contribution process that has exceptions for specific packages like GT to fix it myself with the usualy bugs/slice cycle. Thanks T.

11 18

What's new on Pillar ?
by Cyril Ferlicot April 24, 2015

April 24, 2015

Hi everyone ! I'm currently working on Pillar ! It's been a little while now so I wanted to share what's new. --> First of all, with Stephane we created a new project, Cocoon, based on the configuration system of Pillar. And now Pillar uses Cocoon for his configurations. http://smalltalkhub.com/#!/~PharoExtras/Cocoon --> Pillar unit tests weren't working on Windows before --> With Damien we also added two new abstractions: --> The transformers: They take the Pillar tree and modify it. For exemple we have a transformer which evaluates the scripts with a "eval=true" parameter. --> The annotations: They let the writer specify many different things in their document using just 1 syntax (see below for an example) --> We now have our first annotation tag: the inclusion tag ! If you add this: ${inputFile:test.pillar}$ or ${inputFile:folder/test.pillar}$ into your Pillar file, that will include the content of test.pillar. I recommend for now to use it at the root of the pillar file and not inside a paragraph. That still needs some improvement. --> We now have a transformer which adds an anchor after each title. The anchor will have the text of the title. This still needs some improvement, it's really simple for now. For exemple we need to consider the case where we have 2 titles with the same text (like 'introduction'). --> Now you can add 'lineNumber=true' as parameter for a Script. This will add a numerotation at your script, usefull if we want to explain a long code. --> I did some refactorisation on the parameters used by pillar to clean the code. --> I did some refactorisation of the template system, the old one was really ugly and changed the baseDirectory. Now template are managed by a stream and not a file. --> I improved a little the configuration --> Now if you want to change the baseDirectory you can pass a FileReference, a relative path or an absolute path. --> Now we look for the inputFiles from the baseDirectory and not the working directory like before. You can also pass a FileReference, a relative path or an absolute path. --> I added some tests to Pillar. --> I added some doc to EnterprisePharo https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… --> To help the users I improved the error reports. Before we had really few errors specific to Pillar. For this one you can help me ! If you found a weird error or something really not easy to deal with, send me your problem ! -- Cheers Cyril Ferlicot

2 1

Configuration Browser: Refresh doesn't add new configs
by Sean P. DeNigris April 24, 2015

April 24, 2015

1. Open a Configuration Browser 1.5 (not sure if this matters) I had switched the metaRepo to my own 2. Add a config to the currently shown repo 3. Choose Refresh from the context menu The new config will not appear. Should I open an issue? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Configuration-Browser-Refresh-doesn-t-add-new-configs… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

1 0

Pharo on Centos/RHEL/ 7.1
by nacho April 24, 2015

April 24, 2015

Hi, I noticed that in Pharo's homepage now there is a link to a Centos build. However, the necessary 32bits libs are not mentioned. Here is the list of the libs needed. May be it would be a good idea to put it there in the page, somewhere. Or at least inside the README.txt that comes in the zip. I would append something like: "As the Pharo virtual machine is still 32bits you will need some 32bit libraries. You can get them by executing the following command as root: sudo yum install alsa-lib.i686 glibc-devel.i686 mesa-libGLU.i686 libICE-devel.i686 libSM-devel.i686 freetype.i686 And after that Pharo should run perfectly." Cheers Nacho ----- Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- View this message in context: http://forum.world.st/Pharo-on-Centos-RHEL-7-1-tp4821602.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

3 5

Release with Dark Theme
by Sean P. DeNigris April 24, 2015

April 24, 2015

Why didn't/don't we make it the default for 4.0? Everyone seems to love it, and people are commenting that the UI looks dated. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Release-with-Dark-Theme-tp4821496.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

12 28

Updated WebDoc
by Guillermo Polito April 24, 2015

April 24, 2015

Hi guys, I started yesterday to update WebDoc to work on latest Pharo. I share with you my progress since yesterday: - Now it loads in latest pharo4 :) - fixed javascript errors and render issues - a little of love to the css styles - removed unused/not working features - made it work well when exporting not the full image - ci job is again green [1] you can see the result of applying webdoc to webdoc as the result of the ci job here [2]. If you use it further, you'll see there are still of course some problems, but I feel it is better than before :). If you want to check it out, instructions in [3]. Download: Gofer it smalltalkhubUser: 'PharoExtras' project: 'WebDoc'; package:'ConfigurationOfWebDoc'; load. (#ConfigurationOfWebDoc asClass project version: #development) load. Export: (WebDocExporter packages: {RPackageOrganizer default packageNamed: 'YourProject'}) title: 'YourProject'; exportTo: './doc' asFileReference. Guille [1] https://ci.inria.fr/pharo-contribution/job/WebDoc/ [2] https://ci.inria.fr/pharo-contribution/job/WebDoc/PHARO=40,VERSION=developm… [3]http://www.smalltalkhub.com/#!/~PharoExtras/WebDoc

10 15

TDD and BDD
by Christophe Demarey April 24, 2015

April 24, 2015

Hi, With BDD a current test practice is to start method names with 'should'. It is not yet possible in Pharo but easily do-able (update of TestCase and some Nautilus methods). I would like that Pharo detects tes methods all methods of a class subclassing (directly or not) TestCase AND starting with either 'test' or 'should'. I also would like to add 'deny' to not use 'shouldNot' but here I'm not sure. WDYT? Christophe.

8 20

RPackage: 'accessing' vs 'all accessing' Protocol
by Sean P. DeNigris April 24, 2015

April 24, 2015

What is the distinction of 'all accessing'? ----- Cheers, Sean -- View this message in context: http://forum.world.st/RPackage-accessing-vs-all-accessing-Protocol-tp482146… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 2