April 2019 - Pharo-users - lists.pharo.org

Pharo developer needed
by Serge Stinckwich April 19, 2019

April 19, 2019

Nicolas Becu is looking urgently for a Pharo developer for 4 months, based in La Rochelle, France. Please see the file attached (in French). Regards, -- Serge Stinckwic h Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) Sorbonne University (SU) French National Research Institute for Sustainable Development (IRD) U niversity of YaoundÃ© I, Cameroun "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich

1 0

[ANN] Next Pharo Sprint: April 26
by Marcus Denker April 18, 2019

April 18, 2019

We will organize a Pharo sprint / Moose dojo April 26, starting at 10:00am. (Local Time Paris). Goals of this sprint: - Pharo 8: Fix issues from tracker https://github.com/pharo-project/pharo/issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 Known Local Sprint meetings Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come

1 0

Re: [Pharo-users] NewWave - WorkflowEngine
by TomaÅ¾ Turk April 17, 2019

April 17, 2019

This is excellent, thanks! For busness applications, getting the tools for process-driven development is essential. Some emails ago there was an announcement on Netstyle's engine available here https://github.com/Netstyle/Workflow. Best wishes, Tomaz ------ Original Message ------ From: "Sebastijan Kaplar" <s.kaplar1(a)outlook.com> To: "pharo-users(a)lists.pharo.org" <pharo-users(a)lists.pharo.org> Sent: 17. 04. 2019 15:03:23 Subject: [Pharo-users] NewWave - WorkflowEngine >Hello everyone, > >we've been working on a workflow engine written in Pharo. You can check >it out at: https://github.com/skaplar/NewWave >It is still in the early development and we discussed about making it >public so everyone interested can join, take a look or provide any kind >of feedback. I'm also at discord so you can contact me @skaplar. > >Best regards, >Sebastijan Kaplar

1 0

Migration from VW to Pharo
by Sreenath G K April 17, 2019

April 17, 2019

Hello All, I just wanted to know if we have any tools for which we can make use of to migrate VW code base into Pharo. If something is there please let me know or your suggestion d to port it. Thanks in advance. Best Regards, Sree

3 4

Fwd: Re: How to prevent Mustache from replacing & with & etc.?
by jtuchel＠objektfabrik.de April 17, 2019

April 17, 2019

I sent this to Norbert only instead of to the list... --- Hi Norbert, so I already found the & modifier, which meansÂ {{& myObject.asString }} will not have escaped characters in it. So far so good for & which I want to be interpreted by LaTeX as Column delimiters. But now I have this need for &'s that should be printed. Of course that means I need the encoded, just not as HTML entities ;-) Do you happen to know how I could implement my own modifier that enables to plug a custom encoding? I am thinking of introducing a modifier, say Â§ to switch the html entity encoding for another one which I of course have to implement on my own. The end result would be: {{ myObject }} Â Â Â to encoe with HTML entities for all things (X)HTML {{& myObject }} Â Â Â to not encode at all (e.g. when I need & as & in the resulting String) {{Â§ myObject }}Â Â Â for an individually added encoding (tbd - for my LaTeX needs) A mechanism like this could be used to make a "universal superset" of Mustache, I guess. Especially if we introduce some syntax for selecting an encoding from the template... Any pointers are welcome. And also ideas if this is a feasible/clever idea or not. Joachim Am 17.04.19 um 08:31 schrieb Norbert Hartl: > Joachim, > >> Am 17.04.2019 um 07:56 schrieb jtuchel(a)objektfabrik.de: >> >> Norbert, >> >> thanks for answering. I had tried the {{{ }}} option. In case of >> LaTeX, this is not so easy, however, because {{{ and }}} are >> completely valid syntactical elements of LaTeX. >> >> It seems like you can replace {{ and }} in Mustache, but not {{{ and >> }}}. At least it didn't work when I tried. Using '{{{=### ###=}}} ' >> in my MustacheTemplate would leave text like >> '###myObject.printString###' unchanged in the resulting text instead >> of replacing it with the text representation of myObject. >> >> So what I tried last and what gave me quite some mileage on the way >> to a sulotion was to use >> >> \catcode to replace & with ; in my LaTeX file for the Column >> separator problem >> {{=## to make sure I can fill in my table rows with ; as column >> separator. >> >> Thus my Mustache-Template looks like this (excerpt): >> >> % redefine Mustache-Insertion syntax {{=## ##=}} >> \catcode`\;=4 % redefine ; for & to allow non-escaped >> column-separators in \tabular >> >> ... >> \begin{tabular}{ccp{6.0cm}rrr} >> ##myObject.asLatexTableRows## % This is where & is needed for LaTeX >> to separate table columns, but Mustache would replace the with the >> html entity & >> \end{tabular} >> >> >> This is a bit hacky, and as I wrote, also still presents problems, >> because if any of the Strings being inserted using Mustache contains >> an &, there will be an & in the .tex file, which will lead to a >> LaTeX error. >> >> >> So, essentially, what I am most likely looking for is a way to >> replace {{{ and }}} in Mustache to make sure the $&'s will remain >> untouched in my inserted text... >> Sorry for asking the wrong question, I was so glad how far I'd gotten >> with what I did that I didn't see the forest between all the trees. >> >> So my real question is: how can I replace {{{ in Mustache with >> something that will not irritate LaTeX? >> >> >> Any ideas? >> > Sure ;) In Mustache {{ and }} are the default delimiters. Every > addtional character is a modifier. So {{{ is actuall a start delimiter > {{ with a { as modifier. So what you can do is to change the delimiter > but leave the { modifier like so > > '{{=<% %>=}} <%{ value %>}' asMustacheTemplate value: { #value -> > '&' } asDictionary > > So {{ is the start delimiter, = is the modifier to change the > delimiters. We set them to <% and %>. If you want to have unescaped > strings you keep using the { on the new delimiter which turns out to > be <%{ and %>}. > > Norbert >> Am 16.04.19 um 12:00 schrieb Norbert Hartl: >>> Hi, >>> >>> >>>> Am 16.04.2019 um 09:02 schrieb jtuchel(a)objektfabrik.de: >>>> >>>> Hi Pharoers, >>>> >>>> >>>> I may be a bit wrong on this list. I try anyways. >>>> >>>> I am using Mustache to fill text into a String which will then be >>>> handed over to LaTeX. The Data I fill in comes from the Database. >>>> >>>> Now the problem is this: if a String from the database contains an >>>> ampersand (like in 'Katz & Maus'), Mustache will replace special >>>> chars with HTML entities. That is fine in a web context, but LaTeX >>>> doesnt actually work well with HTML entities. I could, of course, >>>> remove the html entities after Mustache invested a lopt of work >>>> into creating them. But it seems more logical to keep Mustache from >>>> being so eager to help. >>> It is not logical because mustache is defined that way. So >>> redefining does not improve it. But just use triple {{{ }}} to have >>> strings not being escaped. >>> >>>> BTW: I already took the hurdle of Mustache excaping $& fir tabular >>>> environments (LaTeX uses the ampersand as a divider for table >>>> cells) by using \catcode in our .tex template files. But now the >>>> String comes from the database and so I am a bit lost... >>>> >>>> >>>> So is there any best practice for this problem? >>>> >>> Yes, use it this way >>> >>> '{{{ value }}}' asMustacheTemplate value: { #value -> '&' } >>> asDictionary >>> >>> Norbert >>> >>> >>> >> -- >> ----------------------------------------------------------------------- >> Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de >> Fliederweg 1 http://www.objektfabrik.de >> D-71640 Ludwigsburg http://joachimtuchel.wordpress.com >> Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 >> >> >> > > -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1 http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1 http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1

2 4

How to prevent Mustache from replacing & with & etc.?
by jtuchel＠objektfabrik.de April 17, 2019

April 17, 2019

Hi Pharoers, I may be a bit wrong on this list. I try anyways. I am using Mustache to fill text into a String which will then be handed over to LaTeX. The Data I fill in comes from the Database. Now the problem is this: if a String from the database contains an ampersand (like in 'Katz & Maus'), Mustache will replace special chars with HTML entities. That is fine in a web context, but LaTeX doesnt actually work well with HTML entities. I could, of course, remove the html entities after Mustache invested a lopt of work into creating them. But it seems more logical to keep Mustache from being so eager to help. BTW: I already took the hurdle of Mustache excaping $& fir tabular environments (LaTeX uses the ampersand as a divider for table cells) by using \catcode in our .tex template files. But now the String comes from the database and so I am a bit lost... So is there any best practice for this problem? Joachim

2 5

Method comment template
by Tim Mackinnon April 16, 2019

April 16, 2019

One of the things mentioned at PharoDays, which actually could have been a boring talk but in fact caught my attention due to being well researched and presented - was the question of commenting in Pharo (thanks presenters). However, the question of class comments and how many classes actually follow the suggested template was an interesting point. Having earlier heard feenk talk about making documentation fun and usable, it struck me that the current template and even basic tooling are a million miles from this - and in fact run the risk of promoting redundancy and drudgeryâ¦. Sharp claims, but hey we keep striving for better in Pharo. I like the CRC parallel, but I think its the âpublic apiâ and even the "internal representation" bits that annoy me. Surely the public api is what our categories are for? So repeating that is bad (just indicating the category that is the api would be better - and potentially inlining it automatically in the comment would be more useful - this does raise the problem that methods can only be in 1 category, and maybe this is what this template is trying to cover up? Equally, the internal representation should not just be to describe instance variables (we could just give them better names, and possibly double up on the class builder idea where adding a variable could also let you explain right there what its for) but more about the bigger picture - why a dictionary ivar vs a collection. If its a while before we get to full GT, canât we tart up the class comment pane and make it a bit more interactive (like a form) and able to inline docs (or show generated info) so its not retyped? Iâm sure there are some simple tricks we could do to improve the situation immensely to address the premise of the talk? Tim

1 0

Is this really a string concat error?
by Tim Mackinnon April 16, 2019

April 16, 2019

I looked at changing the threshold of getting the string concatenation critique and got a mixed reaction, having lived with the current state a bit longer - Iâm getting tired of the kind of error, but though it worth checking - do we really consider the following a warning? To me its wrong joining 2 stings with , is surely fine? In fact a stream seems overkill or surely the compiler can generate the optimal code for me? This smacks of old days where everyone was busily doing a == b just because it was supposed to be faster until the vm guys just sorted it out?

2 1

"Instance of SampleForm did not understand #myInstanceVariable"
by Steve Quezadas April 14, 2019

April 14, 2019

I am going through the "Spec UI framework" manual and creating a simple UI interface for a program I am writing. When I do a: foo := SampleForm new openWithSpec. I am getting the following error: "Instance of SampleForm did not understand #okButton" okButton is an "instance variable" of the [SampleForm] class and for some reason the class method is not seeing it. The exact line that brings up this error is here: SampleForm class >> defaultSpec ^ SpecLayout composed newRow: [ :row | row add: #okButton ] <----- error happens here origin: 0 @ 0 corner: 1 @ 0.7; yourself Am I missing something incredibly simple? Should I refer to a instance variable with a hash tag in front of it?

1 0

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo 7.0.3
by Tim Mackinnon April 14, 2019

April 14, 2019

This is great - Iâm pleased we can get fixes like this (and keen to get passed that font issue which was driving me crazy). A small related question - how do ensure we get fixes from sub projects considered too? Iâd really like to see: https://github.com/pharo-ide/Calypso/pull/451 as itâs annoying not being able to move methods between classes. There are a few other Calypso gems in there too (and quite a few more to fix). I worry that having all these sub-projects makes it a bit complicated to get them included? Tim Sent from my iPhone > On 12 Apr 2019, at 16:26, "tesonep(a)gmail.com" <tesonep(a)gmail.com> wrote: > > Pharo 7.0.3 contains several bugfixes, notably a fix for the annoying font corruption font. > > <image.png> > > Changes Log > > #2781 Fix comment on OSWindow >> startTextInput > #3160 2975-Problem-when-you-read-an-mcz-pharo7 > #3130 Improving the performance of SourceFileArray > #3164 MailMessage can not send mails with attachment in Pharo7 > #3149 3148-backport-2395-to-Pharo-70--Non-ASCII-class-and-author-names-break-SourceFileArraygetPreambleFromat > #3178 Fix for corrupted fonts in Pharo7 > Detailed Diff: v7.0.2...pharo-project:v7.0.3 > https://github.com/pharo-project/pharo/releases/tag/v7.0.3 > > All the images are available in ZeroConf and in the Pharo Launcher. > > Thanks to all the collaborators especially: > > - David > - Guille > - Pavel > - Christophe > - Theo > - Sabine > - Sven > > And to all the people that helped to make this release in a couple of minutes. > And thanks to the academy! > > Pablo

3 2