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

Re: [Pharo-users] How to prevent Mustache from replacing & with & etc.?

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

April 17, 2019

Re: [Pharo-users] How to prevent Mustache from replacing & with & etc.?

by jtuchel＠objektfabrik.de

So writing my answer I came to the conclusion to visithttps://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessfulBuild/artifact/book-result/Mustache/Mustache.html again. BTW: Good work, thanks for both implementing and documenting Mustache this nicely! And I found {{& which keeps Mustache from escaping. By combinng {{=## and {{& for the "insertion points" I can now render table data with $& as column seprators from Smalltalk. No need for the \catcode any more. But this is not the end of the story. Now I get 'misplaced alignment tab character' errors from LaTeX whenever the text contains an &. Because LaTeX wants & to be escaped as \& ;-)))) So now I can transport my &'s to Latex without much trouble by using ##&, but LaTeX needs the & which are intended to be printed as & to be escaped, just not as html entities but tex entities ;-) Does anybody have a solution for this already or should I try to use Mustache and bend it to my LaTeX needs...? Joachim P.S.: some problems look so easy at the beginning and open a wide universe of unmatching available solutions when you attack them. I cannot use bindWith: because of the % signs, expandMakrosWith: also doesn't work, and Mustache is not suitable out of the box. It's worth a laugh, but somehow it's not funny... -- ----------------------------------------------------------------------- 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

April 17, 2019

Re: [Pharo-users] How to prevent Mustache from replacing & with & etc.?

by jtuchel＠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? Joachim 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

April 17, 2019

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini -also in 7.03

by Paul DeBruicker

HI Ted, How did you install Pharo? I ask because I tested the process you described and everything worked fine on my mac, also Mojave 10.14.4 I opened a terminal, made a temp directory and pasted in curl https://get.pharo.org/64/ | bash to install Pharo. I started the image with ./pharo-ui Pharo.image Then followed your instructions to set the font to large and maximize Pharo to be full screen. Seems to work fine. When you run the command to start Pharo from the command line in the directory with your Pharo 7.0.3 image but instead of specifying an image you ask the VM for its version e.g './pharo --version' what do you get? I get: 5.0 5.0.201901051900 Mac OS X built on Jan 5 2019 19:11:02 UTC Compiler: 4.2.1 Compatible Apple LLVM 7.3.0 (clang-703.0.31) [Production Spur 64-bit VM] CoInterpreter VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Maybe you're inadvertently using an old VM? TedVanGaalen wrote > Hello > > > The freeze problem still exist. (since 2017, starting with Pharo 6) > 16 April 2019: > Today I have loaded Pharo7.0.3-0-64bit-0903ade.image > with VM > <http://forum.world.st/file/t230630/Screen_Shot_2019-04-16_at_18.png> > > On my Mac Mini late 2012, mac OS Mojave 10.14.4 (OS up to date, system > 100%) > Monitor: > Samsung U28D590: > Resolution: 3840 x 2160 (2160p 4K UHD - Ultra High Definition) > UI Looks like: 3840 x 2160 @ 30 Hz > Framebuffer Depth: 24-Bit Color (ARGB8888) > > Note that the same freeze as described previously in this thread > still occurs with the latest Squeak version that > I have downloaded and tried last week. > So this could be a VM problem? I really don't know. > All I want to do is write applications with stable Smalltalk/Seaside > no desire (and knowledge) enough to dive into the deep > and dark catacombs of the VM world. > > what I did: > -opened the pristine image as downloaded today > - in Pharo - settings - appearance: > changed the general font size to Large. > - opened the system browser. > - clicked the green bullet in the top left corner (maximize) > Pharo hangs/freeze, menus don't work either. > Can only exit using Force Quit. > The last stable version I did use was Pharo 5.0. > The problem is still the same as I have described in this thread in August > 2017. > I did use Pharo launcher a few weeks ago (having the same problem) > but this is not exactly user friendly, saved images where I don't want to. > and "Save as from within the image is not respected" > I prefer to use just a VM and images, thats good enough for me. > > Keep it simple. > > I'd like to spend more time with Smalltalk, preferably Pharo. > In essence, I do like new developments like enhanced > system browsers and debugging > that might improve Pharo. > But one might be overshooting the target here, > I find rocksolid stability more important, > than adding more features, so, this should be the main priority, > that is, assuming that Pharo should be deployable in a production > environment? > It is marked as "stable" but it isn't, sorry. > A good house needs a good foundation, same with Smalltalk. > But it seems we are living in a culture of nervous deadlines and hasty and > frequent updates, > is it really necessary? > > All I want is a one click vm + image, as it was before. > simply download and run it. > Why git btw? Smalltalk has an excellent version system, > by using git there is more dependency impact. > > Now I am still using Pharo 5.0, the last (to me) stable version of Pharo. > > Kind regards > Ted > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 16, 2019

Why are package tags not proper sub-packages?

by Tim Mackinnon

Does anyone remember why we decided to consider package tags (as in: Kernel-BasicObjects) not fully fledged sub-packages? The implication here is that extension methods canât live on the tag (they live on the parent package - in the above case Kernel - and not Kernel-BasicObjects), and equally the code critic works on the package level and not on an individual tag. Equally, refactoring can work at the package level â¦ the list goes on. Having decided that it seemed to make it more understandable that Exercism exercises would simply be tags of the package exercism (its tidy to have the exercises neatly organised under a common parent with some generic menu options), I am finding that the above are starting to bite me. Extensions, Code critic (and sometimes refactoring) are awkward or more difficult to explain, and I was left wondering what the rational was to not make the tags fully fledged sub projects? Iâm now wondering if I should bite the bullet and migrate every exercise tag to being a fully formed project (although in most cases it seems overkill for a class and a test). But Iâm interested in the history of this one as maybe it can guide me? Tim

April 16, 2019

Method comment template

by Tim Mackinnon

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

April 16, 2019

Re: [Pharo-users] Is this really a string concat error?

by Sven Van Caekenberghe

No, that is no error, a single #, is actually more efficient than streaming concatenation (because both the argument and result lengths are all known). It is a pity that there are a couple of rules that are too aggressive - and I know that that was not the intention. > On 16 Apr 2019, at 23:09, Tim Mackinnon <tim(a)testit.works> wrote: > > 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? > > <PastedGraphic-10.png>

April 16, 2019

Is this really a string concat error?

by Tim Mackinnon

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?

April 16, 2019

glamorous toolkit forum/maillist

by Steve Quezadas

Is there a forum or maillist for glamorous toolkit? I can't find anything on the official website or google searches.

April 16, 2019

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini -also in 7.03

by TedVanGaalen

Hello The freeze problem still exist. (since 2017, starting with Pharo 6) 16 April 2019: Today I have loaded Pharo7.0.3-0-64bit-0903ade.image with VM <http://forum.world.st/file/t230630/Screen_Shot_2019-04-16_at_18.png> On my Mac Mini late 2012, mac OS Mojave 10.14.4 (OS up to date, system 100%) Monitor: Samsung U28D590: Resolution: 3840 x 2160 (2160p 4K UHD - Ultra High Definition) UI Looks like: 3840 x 2160 @ 30 Hz Framebuffer Depth: 24-Bit Color (ARGB8888) Note that the same freeze as described previously in this thread still occurs with the latest Squeak version that I have downloaded and tried last week. So this could be a VM problem? I really don't know. All I want to do is write applications with stable Smalltalk/Seaside no desire (and knowledge) enough to dive into the deep and dark catacombs of the VM world. what I did: -opened the pristine image as downloaded today - in Pharo - settings - appearance: changed the general font size to Large. - opened the system browser. - clicked the green bullet in the top left corner (maximize) Pharo hangs/freeze, menus don't work either. Can only exit using Force Quit. The last stable version I did use was Pharo 5.0. The problem is still the same as I have described in this thread in August 2017. I did use Pharo launcher a few weeks ago (having the same problem) but this is not exactly user friendly, saved images where I don't want to. and "Save as from within the image is not respected" I prefer to use just a VM and images, thats good enough for me. Keep it simple. I'd like to spend more time with Smalltalk, preferably Pharo. In essence, I do like new developments like enhanced system browsers and debugging that might improve Pharo. But one might be overshooting the target here, I find rocksolid stability more important, than adding more features, so, this should be the main priority, that is, assuming that Pharo should be deployable in a production environment? It is marked as "stable" but it isn't, sorry. A good house needs a good foundation, same with Smalltalk. But it seems we are living in a culture of nervous deadlines and hasty and frequent updates, is it really necessary? All I want is a one click vm + image, as it was before. simply download and run it. Why git btw? Smalltalk has an excellent version system, by using git there is more dependency impact. Now I am still using Pharo 5.0, the last (to me) stable version of Pharo. Kind regards Ted -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 16, 2019