- Pharo-dev - lists.pharo.org

Simple benchmark RBParser vs. Shout
by Marcus Denker April 25, 2015

April 25, 2015

Hi, I want to get a feeling of how much faster Shout is compared to RBParser. This is a very simplistic bench: [Morph methods do: [:method | RBParser parseFaultyMethod: method sourceCode ]] bench. "'3.197 per second'" [Morph methods do: [ :method | SHTextStylerST80 new rangesIn: method sourceCode setWorkspace: false.]] bench "'2.797 per secondâ" This means that parsing performance alone is actually not bad with RBâ¦ (it would be interesting to look at edge casesâ¦) And then of course the next thing to do is the highlighting itself. Marcus

2 2

GitHub CI organization
by Sean P. DeNigris April 25, 2015

April 25, 2015

I may be missing something, but why are pharo-build-scripts and pharo-minimal-scripts not in the pharo-ci repository? ----- Cheers, Sean -- View this message in context: http://forum.world.st/GitHub-CI-organization-tp4821620.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

3 3

Monkey Office Hours
by Sean P. DeNigris April 25, 2015

April 25, 2015

She doesn't seem to be at work. No review for https://pharo.fogbugz.com/default.asp?15395 . BTW where is the code for the monkey, and is there any way to interact with her? E.g. manually force a review, see if she's working... Thanks. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Monkey-Office-Hours-tp4821722.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

3 2

Re: [Pharo-dev] Rubric and Bloc are now in PharoExtras
by Sean P. DeNigris April 24, 2015

April 24, 2015

Thank you!!! Quick question. What is our procedure about contributing to projects which we own but are not part of Core? Should we commit to the inbox or directly to the project repo? At the moment, I'm thinking of non-controversial things like fixing comment typos... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Rubric-and-Bloc-are-now-in-PharoExtras-tp4820182p4820… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

5 6

Re: [Pharo-dev] Rubric and Bloc are now in PharoExtras
by Sean P. DeNigris April 24, 2015

April 24, 2015

Pharo Smalltalk Developers mailing list wrote > done. Thanks, I will take another look :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Rubric-and-Bloc-are-now-in-PharoExtras-tp4820182p4821… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

1 0

Improving the documentation model
by stephan April 24, 2015

April 24, 2015

TL;DR: Some roadmap ideas. Looks like a lot of work. Comments and improvements welcome: We should replace the Pillar document format by a better one, suitable for WYSIWYG editing and creating long documents. --- The current documentation model for Pharo is Pillar. Pillar is the document model from the Pier CMS and provides exports to (a.o) html and LaTeX. It is a simplified form of the LaTeX document model without a WYSIWYG UI. In the research world two documentation systems dominate: LaTeX and Word. Word and its clones dominate areas where ease of use for small papers without maths are important, LaTeX the other fields. From personal experience I know that the lack of abstraction in Word and clones makes it very expensive to create large, consistently formatted documents. In addition, the typographical quality of the resulting documents is much lower than that achievable with LaTeX. On the other hand, repurposing LaTeX to generate anything other than PDF/paper documentation is difficult because of the underlying language that LaTeX is written in, and there is no easy to use WYSIWYG UI for LaTeX. It pains me to see the return of text based formatting with primitive formats like markdown. At least in LaTeX you can preserve semantics level content, in markdown we are back at html 1.0. The program I liked best for creating longer documents was Framemaker. That provided the needed abstractions in an efficient WYSIWYG UI. Framemaker was sold from 1986, so the performance of current hardware should be enough to run something similar in smalltalk. I used versions 5.5 and 6, and had to abandon it when Adobe stopped development and it was never migrated from PowerPC. Framemaker was fast enough to create books with hundreds and even thousands of pages. It had working versions of the long document features Word claimed to have. With Athens and TxText we now have low level abstractions for dealing with cursor and selection, fonts, rendering glyphs and having both on-screen and PDF output. On top of TxText we could add a model somewhat like the attached figure UML diagram of document structure A book consists of a number of named documents. This is essential for dealing with longer material, as in a wysiwyg system we want to avoid having to re-layout too much after a key is pressed. Across documents we only need to remember the starting page/section numbers. Each document consists of pages. On a page there can be fixed content and content that is dependent on the text flow. Most pages of a document have a similar layout, so each page refers to a masterpage that defines the default content. A document can have separate masterpages for first, left and right pages, and rotated or extra large ones. A masterpage can define fixed items and calculated ones (pagenumbers and current chapter). A textframedefinition describes the textframes and the textflow for each textframe. The text (and other in-line contents) of the document are stored in paragraphs, which are stored in textflows. The paragraphstyle of a paragraph knows how to layout it in a textframe, and how to deal with the end of a textframe. The paragraphstyle knows how to paginate, how to number or provide other autotext at the beginning of a paragraph and if the paragraph text should be part of a table of contents. A textframe is a (rectangular) area on a page. The characterstyle of a paragraph is responsible for the font family, size and style. The characterstyle can be overridden by a specific paragraph or by a textrange. With a model like this (and adding maths, tables, notes, figures and references) we should be able to use Pharo to create both high-quality documentation, and write research articles (and books) in-image. Stephan

13 29

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