Beginners September 2019

beginners@lists.squeakfoundation.org

11 participants
17 discussions

Re: [Newbies] Second expression in sequence confusion FreeLink <- "[[" .{&[>\]]} "]]"
by gettimothy 11 Sep '19

11 Sep '19

He Levente. Thank you very much. This is a huge time saver. I was literally reading the wrong documentation. whew! Where is this documented? I do not see it on the wiki link you sent me. Is it infferable from a class in the XTreams packages? I looked over the XTreams tests classes yesterday and did not see any clues. Do the test cases need improving? (I can contribute by doing the grunt work under supervision) Also, what does "don't yield them" mean? Does it mean the parser stays in its present spot? thank you again. t. p.s. I have cc'ed squeak-beginners list on this message. ---- On Tue, 10 Sep 2019 20:30:07 -0400 Levente Uzonyi <leves(a)caesar.elte.hu> wrote ---- Hi Tim, On Tue, 10 Sep 2019, gettimothy wrote: > Hi Levente. > > If you don't have time for this, "No" is a good answer. > > I have the WikiMedia freelinks working. https://en.wikipedia.org/wiki/Help:Wikitext#Free_links > > [[This Is A Link]] generates > > <a href="https://en.wikipedia.org/wiki/This_is_a_link">This is a link</a> > > I would like to translate the FreeLink <- "[[" .{&[>\]]} "]]" sequence into something like > > FreeLink <- LinkOpen .{&[>\]]} LinkClose > LinkOpen <- BracketOpen BracketOpen > LinkClose <- BracketClose BracketClose > BracketOpen <- "[" > BracketClose <- "]" > > so that I can iteratively build up to more complicated link styles. > > That Capture in the middle of the sequence is giving me fits. > Something as simple as: > > FreeLink <- LinkOpen .{&[>\]]} LinkClose > > does not parse as neither LinkOpen nor LinkClose are consumed. > > My interpretation of that middle sequence term is: > "." get the next character and consume it. > {&[>\]]} apply expression &[>\]] and capture the string that matched it for later use. In Xtreams-Parsing, braces don't mean capture. They mean cardinality. It comes from common regular expression syntax. The regular expression x{1,3} means x 1 to 3 times, so it accepts x, xx, and xxx. You can also pass a single number x{3}, which is a shorthand for xxx. You can also omit the second argument like in x{3,}, which means x 3 or more times. This construct is extended in Xtreams-Parsing with a stop expression. "x"{"y"} means, accept any number of x up until y comes. Consume y too, but don't yield it. So, such expression accepts: xy, xxy, xxxy, xxxxy, etc, and yields x, xx, xxx, xxxx, etc. I suspect having & inside {} probably causes problems, because {} tries to consume what it parses, but & tells the parser not to consume what comes after it. If I were to write the FreeLink rule, it would be something like: FreeLink <- "[[" .{"]]"} It means: take two opening braces, accept and yield everything up to two closing braces, then consume those too, but don't yield them. Levente > &[>\]] AND predicate : indicate success if expression [>\]] matches text ahead; otherwise indicate failure. do not consume text. > [>\]] character range between ">" and "]" > > > Thanks for your time. > > cordially, > > t > > > > > > >

1 0

Morphic layout: Proportional centering of cells
by Thiede, Christoph 09 Sep '19

09 Sep '19

Hi, I am probably not seeing the wood for the trees: How can I achieve the following situation? When the layout changes, both texts should keep their center relative to their owner's bounds: [cid:70e3aa7d-eff6-4995-b290-56b49b770d6d] If I use a ProportionalLayout, I can position the TextMorphs at the offsets 0.5(a)0.25 and 0.5(a)0.75, but only with their upper left corner, so they will not really be centered. If I use a TableLayout, I can center the TextMorphs at the top and the bottom using #listCentering:. However, I cannot center each morph relative to one vertical halft of the owner. How can I stretch both cells to half the height of the morph? I also experimented with #cellSpacing: but still did not achieve the desired layout. (Also, I did not found any senders of the property in the image.) Of course, I could use two auxiliary morphs which are arranged using a ProportionalLayout and each contain one text as a centered cell (with #listCentering: and #wrapCentering:). But for me, this feels a quite heavy solution for such a simple problem. Or is this the only way to go? Thanks in advance, Christoph

2 7

Resize all windows in image to fit current resolution
by Christian Kellermann 09 Sep '19

09 Sep '19

Hello! I was wondering whether there's already a handy command sequence for this out there: I would like to resize all windows in a workspace wrt the current screen resolution, ideally keeping their size in proportion to the screen size. The use case for this is working on an image on different machines (laptop/workstation/projector) and having to resize windows (Browser, Transcript, ...) that are too large for the currently used monitor resolution gets tedious. It should be possible to get a list of all currently active windows in a world I guess but I haven't been able to come up with the right keyword in my method finder / browser adventures. How do you deal with this? Kind regards, Christian -- May you be peaceful, may you live in safety, may you be free from suffering, and may you live with ease.

2 1

Morphs that never gain mouse focus?
by Christoph Thiede 08 Sep '19

08 Sep '19

Hi, I'm wondering whether Morphic currently supports any way to hinder a morph from being ever given mouse focus. There are multiple scenarios where I could need something like this. For example. an Autocompletion menu morph should never gain mouse focus <https://github.com/MrModder/Autocompletion/issues/31#issue-472835222> , but currently it overrides #handleMouseEnter: and transfers the focus to its containing morph. The problem with this approach seems to me to be that, when hovering the menu morph, the MouseOverHandler first sends #mouseLeave: to the containing text morph -- before the menu morph can decide to forward the focus event. Ultimately, the focus is consistent, but I do not want #mouseLeave: to be sent at all, as some text morphs <https://github.com/hpi-swa-teaching/SpreadSheetTool/tree/master/packages/Sp…> may show undesirable behavior when loosing focus. I am also running another project where I never want a morph to gain mouse focus from a similar reason. The only Morph in Squeak I remember to never gain focus is the HaloMorph, what is apparently achieved by an extra-check in PasteUpMorph>>#filterEvent:for: where the event is ignored in #tryInvokeHaloFor: before passing it to MouseOverHandler. Manipulating a PasteUpMorph method does not seem appropriate for a small tool. tl;dr: Is it possible to forbid a morph to gain focus at the expense of the current focused morph? If not, would you know any better approach? Or would this even be a possible feature proposal for squeak/dev? Thanks in advance! Best, Christoph -- Sent from: http://forum.world.st/Squeak-Beginners-f107673.html

2 1

PEG Rule to handle nested WikiText Templates.
by gettimothy 05 Sep '19

05 Sep '19

Hi Folks. I am writting a Parser Grammar in the XTreams package http://squeaksource.com/@BPfsPY0nJbH9IXBW/wqWrIinC to handle the Wikimedia wikitext https://en.wikipedia.org/wiki/Help:Wikitext#Text_formatting My grammar looks like this so far: 'Body <- ( Template / Flow )* LineCharacter <- [^\n] Flow <- Bold / Italic / BoldItalic/ LinkShort / LinkFull / LineCharacter /Template Italic <- "''''" Flow{"''''"} Bold <- "''''''" Flow{"''''''"} BoldItalic <- "''''''''''''" Flow{"''''''''''''"} LinkShort <- "[" .{&[>\]]} "]" LinkFull <- "[" Flow{">"} .{"]"} Whitespace <- [\s\t\n\r]* Template <- "{{" Template "}}" / "{{" Flow{"}}"} Heading4 <- Whitespace "==== " Flow{" ====\n"} ' Italic and Bold work just peachy. Template works for a simple Templates like: {{reflist}}. My Actor callback, for now just wraps it in a span like this: <span style="text-decoration: underline">reflist</span> Where things go south is when Templates are nested, for example on Infoboxes which are widely used in wiki markup: Here is a truncated version of my output: <span style="text-decoration: underline">Infobox Italian comune <---This is where the PEGActor callback started to wrap the outmost template. | name = Elmas | official_name = Comune di Elmas .... | area_code = 070 | website = {{official website|http://www.comune.elmas.ca.it/</span> <--here is the nested Template. As you can see the Grammar ended the outermost <span></span> here and never recursed on the inner template. | footnotes = }} <---here is the outermost template should end. So...I need a rule that will cover this. Template <- "{{" Template "}}" / "{{" Flow{"}}"} should be what? Thank you for your help. t

1 0

How to approach this PEGParser Grammar Fix.
by gettimothy 05 Sep '19

05 Sep '19

Hi Folks, In XTreams parsing, the grammarWiki/PEGWikiGenerator combo do not parse the Wikimedia headings. I have copied the grammarWiki to grammarWikiMedia and I am slowly building it up in an attempt to isolate the problem. Grammar looks like this: grammarWikiMedia " http://en.wikipedia.org/wiki/Help:Wiki_markup " ^ 'Page <- (Heading)* LineCharacter <- [^\n] Flow <- Escape / Bold / Italic / LinkShort / LinkFull / LineCharacter Escape <- "**" / "__" / "[[" Bold <- "*" Flow{"*"} Italic <- "_" Flow{"_"} LinkShort <- "[" .{&[>\]]} "]" LinkFull <- "[" Flow{">"} .{"]"} Line <- Flow{1,"\n"} Paragraph <- Line Empty <- "\n" Whitespace <- [\t\s]* Heading <- Heading6 / Heading5 / Heading4 / Heading3 / Heading2 / Heading1 Heading1 <- Whitespace "= " Flow{" ="} Heading2 <- Whitespace "== " Flow{" =="} Heading3 <- Whitespace "=== " Flow{" ==="} Heading4 <- Whitespace "==== " Flow{" ===="} Heading5 <- Whitespace "===== " Flow{" ====="} Heading6 <- Whitespace "====== " Flow{" ======"} ' For the Actor, I have copied the PEGWikiGenerator, saving it as PEGWikiMediaGenerator. I have made some minor additions to support H5 and H6 heading levels per Wikimedia standards. My problem, is that Wikimedia seems to like to wrap its <hN></hN> tags within a paragraph: <p><hN></hN></p> So, while I can parse this input just ducky: | wikiGrammar wikiParser input output | wikiGrammar := PEGParser grammarWikiMedia reading positioning. "This is your grammar converted to an xtream." wikiParser := PEGParser parserPEG parse: 'Grammar' stream: wikiGrammar actor: PEGParserParser new. "This is the parser generated from your grammar." input := ' = Heading 1 = == Heading 2 == === Heading 3 === ==== Heading 4 ==== ===== Heading 5 ===== ====== Heading 6 ======'. output := wikiParser parse: 'Page' stream: input actor: PEGWikiMediaGenerator new. "An actual compiler doing the most basic stuff." output inspect. Producing an XMLElement looking like this: <div><h1>Heading 1</h1><h2>Heading 2</h2><h3>Heading 3</h3><h4>Heading 4</h4><h5>Heading 5</h5><h6>Heading 6</h6></div> When I wrap the <hn> elements in <p> tags for this input... | wikiGrammar wikiParser input output | wikiGrammar := PEGParser grammarWikiMedia reading positioning. "This is your grammar converted to an xtream." wikiParser := PEGParser parserPEG parse: 'Grammar' stream: wikiGrammar actor: PEGParserParser new. "This is the parser generated from your grammar." input := '<p>= Heading 1 =</p> <p>== Heading 2 ==</p> <p>=== Heading 3 ===</p> <p>==== Heading 4 ====</p> <p>===== Heading 5 =====</p> <p> ====== Heading 6 ======</p>'. output := wikiParser parse: 'Page' stream: input actor: PEGWikiMediaGenerator new. "An actual compiler doing the most basic stuff." output inspect. my XMLElement looks like this: <div/> I am supposing that I have a wayward Grammar specification. Where should I focus? Should I hack at Heading1 <- Whitespace "= " Flow{" ="} and change "Whitespace" to something else ? Or should I redefine the Line <- Flow{1,"\n"} Paragraph <- Line duo? If a general principle exists that will guide me going forward, I would very much appreciate it. Thank you in advance. t

2 3

Continue/Ignore error
by gettimothy 03 Sep '19

03 Sep '19

Hi folks. The following code is working very well, but when an Error occurs, I would like it to ignore the error and continue. Transcript clear. [(WikitextModule allSubclasses select:[:module | (module pagetitle indexOf:$/ ifAbsent:[0]) > 0]) do:[:m | |ss f d cmd shell content ios| ss := m pagetitle squeakToUtf8 findBetweenSubStrs: '/'. d := ss collect:[:each | each] from: 1 to: (ss size -1). "handle Sandbox and User: here" ((d at:1) = 'Sandbox') | ((d at:1) beginsWith:'User:') ifTrue:[] ifFalse:[ d := d inject:'' into:[:a :b | a, '/', b]. f := ('lua',d, '/', ss last, '.lua') squeakToUtf8 . "ios writes to shared by default" cmd := 'mkdir -p shared/lua', d. "commandshell writes to squeak root directory, so we prepende 'shared' to it" Transcript show: (m name), ' : ', cmd; cr. shell := PipeableOSProcess bash. shell pipeFromOutput reader setNonBlocking. shell exec: cmd. (Delay forMilliseconds: 400) wait. Transcript show: shell upToEnd ; cr. shell close. content := m lua squeakToUtf8. ios := FileStream newFileNamed: f. ios isNil ifFalse:[ content storeOn: ios. ios close. ]]. ]] ifError:[:x :y | Transcript show: x;cr. y close. thisContext resume] The error is WikitextModule613405370 : mkdir -p shared/lua/Road_data/strings/USA/KY Error: cannot create OS pipe I am assuming it is happening during the mkdir -p command during the shell sequence of code in bold above but that is not my question. Although it could be happening in the ios portion. My question is how, after the Error is thrown do I continue the 'do:[:m...] block? thanks for your time.

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Beginners September 2019