June 2014 - Pharo-users - lists.pharo.org

Bug in Nautilus... (Pharo 3)
by JosÃ© ComesaÃ±a June 2, 2014

June 2, 2014

If I try to "move to another package" a class I always get an exception. Try moving any class present in the standard Pharo 3 to AST-Core, for example... Anyway, thanks for the great work you are doing. Regards JosÃ©

2 1

[SummerTalk] Refactoring in Pharo
by Mark Rizun June 2, 2014

June 2, 2014

Hi guys! I'm happy to announce you, that I will be working on SummerTalk project entitled "Refactoring in Pharo" with RMoD. Obviously, it's about refactoring system in Pharo. The goal of this project is to improve existing refactrings in Pharo and add some new ones. If you are interested in this topic please visit my blog for more details: http://myfuncoding.blogspot.com/ After some work is done, I'll publish info here and on my blog. Also, source code will be available on my smalltalkhub, and it's going to be soon ;) Thoughts and feedback are welcome. Cheers, Mark

4 4

Some TDD Coding Kata videos
by Attila Magyar June 2, 2014

June 2, 2014

I'd like to share some videos about TDDing codeing katas. http://smalltalkhub.com/#!/~zeroflag/TDD-Kata Most of them are solved in a "TDD as if you meant it" style, so the code is written in the test at first, and factored out later. During this I tried to use as much refactoring as possible, instead of editing texts. After doing some tweaks, I was able to do most of the work without using the mouse too much. -- View this message in context: http://forum.world.st/Some-TDD-Coding-Kata-videos-tp4761315.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

2 1

STON on ScaledDecimal?
by JosÃ© ComesaÃ±a June 2, 2014

June 2, 2014

Wouldn't it be good if STON could save ScaledDecimals as 12345.678s?. That way, we could read them back again as ScaledDecimal, instead of Float. I have tried and it seems quite useful. Regards

3 12

Mac keyboard bindings
by Stephan Eggermont June 2, 2014

June 2, 2014

Take a look at the Keymapping package. There is a documentation chapter on the ci server https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ Stephan

4 6

PIllar >> #visitAnnotatedParagraph:
by Ben Coman June 1, 2014

June 1, 2014

PRMarkdownWriter >>visitAnnotatedParagraph: says "Pier seems to lack consistency here ...". Indeed, for #visitAnnotatedParagraph: we currently have: * PRPillarWriter outputs all annotations unchanged * PRMarkdownWriter * prepends the the annotationLabel to the annotationText * has special handling for @@todo by calling #visitCommentedLine: * indicates it does some kind of nesting in a custom way; but I can't work out the semantics; and it interrupts nested list numbering similar to what I reported for comments. * PRVisitor * throws away the annotationLabel by just calling #visitParagraph * knows nothing about @@todo * knows nothing about nesting * PRHTMLWriter has no definition inheriting from PRVisitor * PRLaTeXWriter has no definition inheriting from PRVisitor * PRTextWriter has no definition inheriting from PRVisitor To bring some consistency I propose to... 1. Prepend annotationLabel for all the xxWriters 2. Change PRMarkdownWriter to use the code I implemented for nested comments. Have all xxWriters use this also. 3. Drop the @@todo from PRMarkdownWriter, since if you want ToDos to be hidden like a comment, you should just use a comment, e.g." %todo ..." . However this change would alter the semantics of existing users of Pier. So what is the process for such changes? Announce here and wait some period? For consideration, there are currently no tests for annotated paragraphs, so this could be considered outside the existing API ;) - and so I'll add tests, which will be simpler without @@todo. cheers -ben

2 2