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

How can I specify the bindings when evaluating an expression?
by stepharo May 9, 2015

May 9, 2015

I would like to be able to express Compiler new bindings: { a -> 3. b -> 4}; evaluate: 'a + b'; result and get 7 How can I do that? Stef

5 14

Pharo 4 & NeoCSV
by Andreas Wacknitz May 9, 2015

May 9, 2015

I miss the configuration of NeoCSV in the configuration browser of Pharo 4. Is there any reason for the lack of it? NeoJSON is available, thoughâ¦ Regards Andreas

6 7

Athens BitBlt bug?
by Nicolai Hess May 8, 2015

May 8, 2015

Anyone knows what this BitBlt bug is or was? 12818 <https://pharo.fogbugz.com/default.asp?12818> Last row missing 13236 <https://pharo.fogbugz.com/default.asp?13236> Fix 1 extra height for Cairo surface Because with the fix in 13236, it is not (easily) possible to make a repeating (vertical) pattern paint with 1 pixel height: 14813 <https://pharo.fogbugz.com/default.asp?14813> Wrong size for Athens surface pattern paint from a Form nicolai

3 4

PetitMarkdown
by Norbert Hartl May 3, 2015

May 3, 2015

I found markdown parsers in smalltalkhub and in the configuration browser. http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/ <http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/> and the one in the configuration browser PPMarkdown If I understand it correctly both are rooted into work Camillo did. The one in PharoExtras looks newer to me. So I assume the best would be to copy the ConfigurationOfPetitMarkdown from PharoExtras to MetacelloRepo and remove the ConfigurationOfPPMarkdown. Right? Or are there any objections? Norbert

16 31

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

[Reflectivity] simple #before and #after links working...
by Marcus Denker April 23, 2015

April 23, 2015

Hi, After loading this: https://pharo.fogbugz.com/f/cases/15196/Simple-before-and-after-links-with-… <https://pharo.fogbugz.com/f/cases/15196/Simple-before-and-after-links-with-…> Simple after and before MetaLinks are taken into account, with just one check in #visitNode of the ASTTranslator that is false when no links are there. (which means this slice should not impact anything) For now this is for very simple MetaLinks: no parameters, no condition, no reification, no #instead/around, no meta-level modelling. Here is a trivial example: 1) get a AST node from our example method: sendNode := (ReflectivityExamples>>#exampleMethod) ast body statements first value. 2) then we define a link that is just #halt: link := MetaLink new metaObject: Halt; selector: #now. 3) we set it: sendNode link: link. 4) when we now execute the method, we get a halt: ReflectivityExamples new exampleMethod 5) to get rid of it, uninstall the link: link uninstall. If you look at the byte code, you see that it compiles the link to the code: 25 <20> pushConstant: Halt 26 <D1> send: now Marcus

3 7

Ugly textrendering (vertical label)
by Nicolai Hess April 17, 2015

April 17, 2015

Someone knows, why the text on the completion morph is so ugly? For example, this text Morph ne will open a completion window for "Morph class". This name is a vertical label on the left. The text looks ugly when we are using a FT font. Can we do anything to make this look better ? I know that (smooth) text rendering is difficult for arbitrary rotated forms, but this rotation around n*90 degree works with StrikeFont. nicolai

3 3

Existing <script> <example> pragmas and new GT needs
by Torsten Bergmann April 10, 2015

April 10, 2015

Hi Tudor and all, to understand the issue one has to know: ------------------------------------------------------------------------------------------ There are two pragmas in Pharo 4 that were already introduced and integrated: <script> / <script:> - one can use this to mark methods (of any signature) as development scripts. One can use it on instance side and an class side methods to run the method or some code while developing without having to leave the browser. After completion Nautilus shows that the method finished Think of a class "MyKillerProjectDatabase" with a class side method "start". You can click this to run - but it does not serve as an example. A script is just "SOMETHING TO RUN". The code of the script may be too easy or to complicated to serve as an example. See also #14647, #14747 and #14995 for details. <example> - Nautilus in the past already honored class side exampleXXX methods to have a "play" icon to easily visually see examples and just run them. With the <example> pragma one can explicitly mark a method as an example method and we do not have to rely on the method name. So we can use #tryThisOutForExample as selector name as well now. It also allows to search for examples, build an example browser for newbees, ... An example shows the usage of a class or code (usually to get an initial idea). The pragma also only works on class side methods. Think of existing classes like EditableList or WidgetExamples that provide example methods starting with exampleXXX. The user sees in the browser directly that this is an example he can run or look at to understand the details because the author offered it as "SOMETHING TO LEARN FROM". See also #14646 and #15225 for details So (even only at the second look) there is a distinction between a "script" and an "example". Being a script does not automagically make a method an example. And yes: a method can also be both and both pragmas can be used. The history of these two is explained in https://pharo.fogbugz.com/f/cases/15225/useless-play-icon-in-nautilus and I already use this in several projects. -------------------------------------------------------------------------------------------- Now it looks like Tudor is in need of a pragma for GT tools to provide "example data". @Tudor: I do not understand why you now abuse/try to redefine the meaning of this existing <example> pragma for your special purposes/needs or try to exchange one against the other as in new issue #15229. According to your own comment in issue #15225 your definition of an "example" is something "to offer an initialized object that can be used for documentation or testing purposes." I have to strongly disagree on this as this is ONLY TRUE FOR A FEW CASES. Look at our image, look at how people write example (methods): NOT ALL class side example methods necessarily return an initialized objects but are still examples. I already explained in the above issue that there are lots of example methods that one just run (either from the comment or from Nautilus icon) like EditableListExampel(class)>>example, ... They DO NOT return an initialized instance. Look at the "examples" in class WidgetExamples or others. None of them provide an initialized instance! So the right definition for an "example" is: "to offer runnable code that can be used for documentation or testing purposes." So PLEASE if you are in need of such a new thing where only initialized instances are returned from code then DO NOT REDEFINE existing and used pragmas like the integrated <example> pragma. PLEASE use an OWN NEW PRAGMA for GT purposes like <exampleData>, <exampleInstance>, <gtExampleInstance> or whatever. I would also find an "exampleInstance" pragma name then more intention revealing. Thanks a lot in in advance! Bye T.

14 54

New Pharo-Launcher package for Mac and Windows
by Damien Cassou April 8, 2015

April 8, 2015

Hi, I've just updated the 2 installers for mac and windows. http://files.pharo.org/platform/launcher/Pharo_0.2.4.dmg http://files.pharo.org/platform/launcher/pharo_installer-0.2.4.exe - the windows installer should have the PharoV30.sources file that was missing - both installers now install the most recent Pharo launcher -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

9 21

April 8, 2015

Hi guys Do you know if there is a library somewhere in Smalltalk to deal with RTF writing/saving? Stef

7 10