- 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

Re: [Pharo-users] STON on ScaledDecimal?
by Joachim Tuchel May 31, 2014

May 31, 2014

Hi, Sounds good. But I think the Scale should be streamed as well: 12345.678s3 Joachim JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> schrieb: >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

2 1

[smallwiki] Pillar annotations for Latex
by Ben Coman May 31, 2014

May 31, 2014

> Hi Ben, > > On Thu, May 22, 2014 at 6:09 PM, Ben Coman<btc(a)openinworld.com> wrote: > > Now is there any important function missing, or is there a better way to do > > this? > > thank you for your contribution. > > I would try to generate this instead: > > \begin{note} > foo bar baz > \end{note} > > This environment is meant for this. To output the \begin and \end parts, use > > canvas environment > > (look at the senders of #environment in the PRLaTeXWriter class for examples) > > To output the text, you can just write > > super visitAnnotatedParagraph: aParagraph > > > > I also want add an annotation type, which I'll describe in a following post. > > > I should we should think a bit how these should be handled. In the > meantime, you can just hack around :-). And please add unit tests. > > -- > Damien Cassou So I determined that the following works well... PRLaTeXWriter>>visitAnnotatedParagraph: anAnnotatedParagraph "Pier seams to lack consistency here ..." 'todo' = anAnnotatedParagraph annotation asLowercase ifTrue: [ ^ self visitCommentedLine: anAnnotatedParagraph ]. canvas environment name: 'note' ; with: [ super visitAnnotatedParagraph: anAnnotatedParagraph ]. to process Pillar markup... @@note Pay attention to the class definition for your new ""==BlankCellTest=="". It must be a subclass of the class ""==TestCase=="". This is easy to overlook. If you did it wrong already, no problem, just go back and correct it now and then save the code again. Within a class, methods are organised into "protocols" that are shown in the third browser pane from the left of Figure *testCellStateShouldBeOffEmpty*. We will group our "tests" inside a protocol of the same name. to produce this nice looking PDF showing the note indented with dividing lines... Now that was real easy to do!! Thanks for making Pillar accessible. I can't imagine making a similar change as easy in a Markdown processor in some other language. --------------- Next, in common.tex [1] I found... { \newcommand{\dothisicon}{\raisebox{-.5ex}{\includegraphics[height=1.2em]{pharo}}} \newcommand{\dothis}[1]{% \medskip \noindent\dothisicon \ifx#1\empty\else\quad\emph{#1}\fi \par\smallskip\nopagebreak} } and discovered I could do this in the Pillar markup... Before defining a class we should define a package to contain our classes. When we save a package all the classes will be saved together. It is a good practice to group together classes that work together. {{{latex: \dothis{Right-click on the background and open a System Browser.} \dothis{In the package list of the System Browser, choose "add package" to add a new package. Use the name "LaserG }}} to produce in the PDF two Pharo icons on separate lines... But that is awkward and verbose to do each time, and I though it would be nice for Pillar to handle this as an annotation like this... Before defining a class we should define a package to contain our classes. When we save a package all the classes will be saved together. It is a good practice to group together classes that work together. @@dothis Right-click on the background and open a System Browser. @@dothis In the package list of the System Browser, choose "add package" to add a new package. Use the name "LaserGame-Model". so I found I could do that by added the following hack to PRLaTeXWriter>>visitAnnotatedParagraph: ... 'dothis' = anAnnotatedParagraph annotation asLowercase ifTrue: [ ^ self writeRawDuring: [ stream newLine. stream << '\dothis{' . stream << anAnnotatedParagraph text trimBoth . stream << '} ' . ]. ]. However changing this to be less of a hack like this... 'dothis' = anAnnotatedParagraph annotation asLowercase ifTrue: [ ^ canvas command name: 'dothis' ; parameter: [ super visitAnnotatedParagraph: anAnnotatedParagraph ] ]. doesn't quite work, since the first Pharo icon runs onto the previous line... That can be fixed as follows.... PRLaTeXCommand>>name: aString stream newLine. "<---THIS LINE ADDED" stream << $\ << aString but I don't know if that is the right thing to do. Maybe there are times when you want commands to run on from a line. What would be the right thing? Also, is it reasonable to add this new annotation type? i.e. might it be integrated soon ? :) :) . This would really help with the Laser Game tutorial. [1] https://github.com/bencoman/PharoLaserGameTutorial/blob/master/common.tex cheers -ben P.S. This is my first post to the mail list using PostBox on OSX. Let me know if you notice any issues with it being not plain text and if you have any advice ensure plain text posts in PostBox.

3 6

Re: [Pharo-users] ical on pharo 2
by Paul DeBruicker May 30, 2014

May 30, 2014

Hi Jesus Mari, Thanks for spotting and fixing those bugs. The missing methods are because I overrode them in a package Iâm using and forgot about that when I saved some changes to iCal. I did not notice the problem with the timeZone because Iâm in the habit of only using UTC dates and times in the image and converting them to timeZone specific formats for display. Good find. Re: #isValidForDate: Iâm not sure about your solution. I think it depends on whether December 31st 2014 is the important part or whether the overlapping timespan of one date between two timezones is important. And to know that Iâd have to read the ical spec. Which is here: http://tools.ietf.org/html/rfc5545 and I donât have time to go through in any detail. Do you want/have write access to upload your repairs? Thanks again Paul On May 30, 2014, at 4:03 AM, Jesus Mari Aguirre <jmariaguirre(a)gmail.com> wrote: > I have tried to run the Test package in Pharo 2.0 and I have found some problems. > * You use String #subString method that is deprecated. > * There are several methods missed in your new packages, I'm not sure why... > ICConversion class #dateAndTimeClass, #dateClass, #timeSpanClass #timeClass. I have added to the ICal-SqueakPharo-Core package copied from the first version in the repository. > * methods ICEvent isValidForDate: aDate and ICTodo isValidForDate: aDate do not take care about the timeZone, then several tests fail. These tests are successful if you set the date offset to 0 hour, but maybe what you try to do with the method is returning all the events and todos currently actives. > > Could be this method the right solution? > > ICEvent isValidForDate: aDate > > ^self start asDate start<= aDate end and: [self end asDate end>= aDate start]. > > ICTodo isValidForDate: aDate > > ^self due asDate start<= aDate end and: [self due asDate end >= aDate start]. > > I hope this information will be useful for you. > keep contact > JesÃºs MarÃ > >

1 0

[ANN] iStoa 14.06
by Hilaire Fernandes May 30, 2014

May 30, 2014

Hi, If you have young kids (around 5-6 years old) and a linux workstation, you may want ot give a try to latest iStoa. https://launchpad.net/istoa/trunk/14.06 I translated it in French as well ;) If interest to translate in other languages (including asian ones) let me know. Hilaire -- Dr. Geo http://drgeo.eu

3 3