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

[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

MacOS headless but showing up in dock?
by Bernat Romagosa May 30, 2014

May 30, 2014

Hi list, is it possible to have Pharo run headless while still showing up in the dock? In the same direction, is it possible to add contextual menu items to the dock menu? Or for what matters, to the top system menu? Thanks! -- Bernat Romagosa.

3 8

Sending transactional emails from Pharo
by Esteban A. Maringolo May 30, 2014

May 30, 2014

What is the simplest way we have in Pharo to send emails? We're going to send a bunch of "no-reply@mydomain" style mails confirming transactions and similars. ~3000 mails. Anybody already doing this? Regards. Esteban A. Maringolo ps: This will be running in a DigitalOcean droplet, so I could install an email server, but I don't think it is the simplest solution :)

4 11

Re: [Pharo-users] the mystery of dirty package
by Stephan Eggermont May 30, 2014

May 30, 2014

Usman wrote: >It is second time in a week that I have to analyze a problem related to a package getting dirty because of loading another package. But when looking for changes, the >first package becomes clean again. A well-known reason can be found by taking a look in your package cache. If there are multiple versions of one package, there is a configuration problem. Lots of configurations refer to wrong versions of Grease & Magritte Stephan

1 0

the mystery of dirty package
by Usman Bhatti May 30, 2014

May 30, 2014

Hi, It is second time in a week that I have to analyze a problem related to a package getting dirty because of loading another package. But when looking for changes, the first package becomes clean again. One occurrence of the problem can be seen in the latest moose image: - download the latest image here:https://ci.inria.fr/moose/job/moose-5.0/ - monticello browser -> Collections-Abstract -> changes and the package becomes clean. Any idea how to determine which method(s) from the incoming package might be causing changes in the loaded package? Or generally, how to go about correcting this problem? usman

4 6

Wiki system for Pharo (smalltalk)?
by Mircea S. May 29, 2014

May 29, 2014

What Wiki systems are still around for Pharo (smalltalk)? Thank you.

4 3

deep into pharo(esug 2013) translate to korean draft version.
by peter yoo May 29, 2014

May 29, 2014

http://trans.onionmixer.net/mediawiki/index.php?title=DeepintoPharo this book translate to korean. but draft now. have a time then read and fix more. thanks for Alexandre Bergel, Damien Cassou, Stephane Ducasse, Jannik Laval..... and more smalltalkers. :D -- http://onionmixer.net | http://gentoo-kr.org peter yoo. ROK

4 13

Cloud Shoppie - App Contest Poll
by Thushar G R May 29, 2014

May 29, 2014

Hi All http://letsbuildkaec.challengepost.com/submissions/23789-cloud-shoppie This is an iOS/Android application with server developed in Pharo Smalltalk(Seaside-REST). There is a video explaining the application and a link to vote for the application. We are a start up with a team of 8 smalltalkers and would greatly appreciate your valuable support and feedback. Thanks In Advance. G R Thushar

3 5