- Pharo-users - lists.pharo.org

Re: [Pharo-users] deep into pharo(esug 2013) translate to korean draft version.

by Damien Cassou

On Fri, May 23, 2014 at 5:42 PM, peter yoo <onionmixer(a)gmail.com> wrote: > hm.... really? can then i want. but really ok? sorry, I don't understand. I propose to add an url to your document on our website. If you are interested, no problem. Even if your translation is work in progress. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

May 24, 2014

Re: [Pharo-users] [smallwiki] Pillar annotations for Latex

by Damien Cassou

On Sat, May 24, 2014 at 10:51 AM, Ben Coman <btc(a)openinworld.com> wrote: > 'dothis' = anAnnotatedParagraph annotation asLowercase > ifTrue: > [ canvas newLine. "<----THIS LINE ADDED" > > ^ canvas command > name: 'dothis' ; > parameter: [ super visitAnnotatedParagraph: > anAnnotatedParagraph ] > ]. > > which seems better, but maybe still not the best. that's the right way I guess, thank you for your contribution. Please add related unit tests. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

May 24, 2014

Re: [Pharo-users] [smallwiki] Pillar annotations for Latex

by stepharo

Really nice! > > @@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. :)

May 24, 2014

Re: [Pharo-users] Pillar annotations for Latex

by stepharo

thanks for your help improving pillar because we are busy. Stef On 22/5/14 18:09, Ben Coman wrote: > The Pillar documentation [1] says... > "An annotated paragraph starts a line with @@ followed by either > todo or note. For example, > @@note this is a note annotation. > generates > Note: this is a note annotation. > And, > @@todo this is a todo annotation > generates a todo annotation that is not visible in the output." > > However this does not work when rendering to LaTex. > * The notes do not start with "Note:" > * The todos are visible > > This seemed to be handled by... > PRMarkdownWriter>>visitAnnotatedParagraph: anAnnotatedParagraph > "Pier seams to lack consistensy here ..." needsABreak ifTrue: [ > canvas addInvisibleSeparator ]. > > anAnnotatedParagraph annotation asLowercase = 'todo' > ifTrue: [ ^ self visitCommentedLine: anAnnotatedParagraph ]. > > self nest: [ :brush | brush > name: '' > with: [ :nestedStream | > self writeRawDuring: [ > nestedStream << 'Note: '. > nestedStream << anAnnotatedParagraph text > trimBoth ] ] ]. needsABreak := true. > > but that there is no equivalent PRLaTexWriter>>visitAnnotatedParagraph: > and the following is used by default... > PRVisitor>>visitAnnotatedParagraph: aDocument > self visitParagraph: aDocument > > > In seeking to fix this for LaTex I found... > * /needsABreak/ is an ivar of PRMarkdown and I guess not applicable to > LaTex > * #nest: and the /nest/ ivar it references belong to PRMarkdown, and > I'm not sure of their purpose. > > So I cut those out, which left the following... > PRLaTexWriter>>visitAnnotatedParagraph > anAnnotatedParagraph annotation asLowercase = 'todo' > ifTrue: [ ^ self visitCommentedLine: anAnnotatedParagraph ]. > > self writeRawDuring: [ > nestedStream << 'Note: '. > nestedStream << anAnnotatedParagraph text trimBoth ]. > > ...which works well enough for the usage I see so far in > PharoLaserGameTutorial. [2] > > Now is there any important function missing, or is there a better way > to do this? > I also want add an annotation type, which I'll describe in a following > post. > > cheers -ben > > [1] https://github.com/pillar-markup/pillar-documentation > [2] https://github.com/bencoman/PharoLaserGameTutorial > >

May 24, 2014

Re: [Pharo-users] [smallwiki] Pillar annotations for Latex

by Ben Coman

Ben Coman wrote: > >> 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 I discovered that instead of modifying PRLaTeXCommand>>name: , that in PRLaTeXWriter>>visitAnnotatedParagraph: I could do... 'dothis' = anAnnotatedParagraph annotation asLowercase ifTrue: [ canvas newLine. "<----THIS LINE ADDED" ^ canvas command name: 'dothis' ; parameter: [ super visitAnnotatedParagraph: anAnnotatedParagraph ] ]. which seems better, but maybe still not the best. cheers -ben

May 24, 2014

[smallwiki] Pillar annotations for Latex

by Ben Coman

> 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.

May 24, 2014

Re: [Pharo-users] storeOn:/readFrom: symmetrical?

by stepharo

On 23/5/14 19:58, Rick Kitts wrote: > Hi. A basic question I hope someone can answer. This works: > > â cut here --- > | stream aInt | > > stream := (String new:20) writeStream. > aInt := 23. > (aInt storeOn:stream) = (aInt class readFrom:(stream contents)) > > â cut here --- > > This doesnât (generates an error): > > â cut here --- > | stream aTime | > > stream := (String new:20) writeStream. > aTime := Time now. > (aTime storeOn:stream) = (aTime class readFrom:(stream contents)) > > â cut here --- > > To the question then. Assuming the second case isnât wrong in some > fashion I donât understand, is it the case that storeOn:/readFrom: is > supposed to be symmetrical for all classes? I ask it that way because > there are a couple of Kernel classes where Iâve seen this to not be > the case. It would be nice that they get symmetric. because the goal of storeOn: is to recreate the same object. So if you have a fix please - sign the license agreement - open a bug entry - publish the fix. > > TIA, > âRick > > > >

May 24, 2014

Re: [Pharo-users] Initializing a class with a Dictionary

by stepharo

Hi sergio what do you want to do? Object subclass: #MyClass instanceVarNames: 'dict' MyClass>>initialize [ super initialize. dict := Dictionary new. ] MyClass>>atKey: aKey put: aVal [ dict at: aKey put: aVal ] MyClass>>atKey: aKey [ ^ dict at: aKey ] let you manage the key/val that you want? Let me know if this answers your question. Stef On 22/5/14 19:37, sergio_101 wrote: > > is it possible to initialize a class with a dictionary? my first > thought would be to create a method like: > > intializeWithDictionary: aDictionary > > then, loop through the elements and do something like: > > instVarNamed: key put: value > > but the book says: > > Caveat: Although these methods are useful for building development > tools, using them to develop conventional applications is a bad idea: > these reflective methods break the encapsulation boundary of your > objects and can there- fore make your code much harder to understand > and maintain.-- > > should i avoid this? > > > ---- > peace, > sergio > photographer, journalist, visionary > #BitMessage BM-2D8VWUJSS41RFKh1ec83preVabHrnniExa > > http://www.Village-Buzz.com > http://www.ThoseOptimizeGuys.com > http://www.CodingForHire.com > http://www.coffee-black.com > http://www.painlessfrugality.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101

May 23, 2014

Re: [Pharo-users] deep into pharo(esug 2013) translate to korean draft version.

by stepharo

Thanks a lot for your effort and time!! Stef On 23/5/14 07:09, peter yoo wrote: > Deep into Pharo make use xetex. > > im dont have latex file. make from my templete. > > > need more touch. but can use. > > thank you for all authur~ > > > > look here please. > > http://ta.onionmixer.net/wordpress/?attachment_id=265 > > ps. have a little problem. because.... wiki2latex using then need > check for some special chracters (ex:^ or *) have a time then check more.

May 23, 2014

Re: [Pharo-users] Downloading tweets

by Arturo Zambrano

Hi Steph, it is in pdf.. that's why we need more practical documentation ;-) Gofer new url: 'http://smalltalkhub.com/mc/arturozambrano/TwitterRoassalPlayGround/main'; package: 'TwitterÂConnection'; load. there are other packages but they are other parts of our twitter thing, I think they are not useful for the community. best regards On Fri, May 23, 2014 at 3:45 PM, stepharo <stepharo(a)free.fr> wrote: > Hello Arturo > > nice to see you more and more on this list :). > Where is the code? > So that we can advertize it > > Stef > > > On 23/5/14 03:39, Arturo Zambrano wrote: > >> Hi All, >> you can now download some code for downloading tweets using REST and >> Streaming Twitter APIs. >> It is far from complete but do the job we need for now. >> >> Besides tweets downloading you can also: >> - get users information. >> - retrieve the profile picture of users. >> - ask for the relationship of the two users >> >> Please find attached some info regarding dependencies (no metacello >> config for now), and manual login procedure for the first time you connect >> to twitter. >> >> >> We will work on tests, completion and more practical documentation soon. >> At the same time, when the visualization part of our Twitter thing is >> ready, we will communicate it. >> >> Thanks Rosario for her help, and Sven for advice on the streaming feature >> of Zinc. >> >> regards >> art >> > > >

May 23, 2014