- Pharo-users - lists.pharo.org

Re: [Pharo-users] Zinc server with static and non-static files
by Norbert Hartl March 28, 2020

March 28, 2020

There is ZnPrefixMappingDelegate you can use. server delegate: (ZnPrefixMappingDelegate map: 'static' to: staticFileDelegate; map: 'app' to: myApp). There is also ZnStaticFileDecoratorDelegate if you want to mimick another typical setup where all urls that resolve to a file get served from disk and any other will be forwarded to you app. server delegate: (ZnStaticFileDecoratorDelegate decorate: myApp servingFilesFrom: 'static/'). Hope this helps! Norbert > Am 28.03.2020 um 01:34 schrieb Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org>: > > > Von: Davide Varvello <varvello(a)yahoo.com> > Betreff: Zinc server with static and non-static files > Datum: 28. MÃ¤rz 2020 um 01:34:13 MEZ > An: pharo-users(a)lists.pharo.org > > > Hi Guys, > Is it possible a Zinc server returns static files within a specific url path > (like the ZnStaticFileServerDelegate) and also returns other logics as shown > with map:#otherPath to: MyWebapp new ? > TIA > Davide > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > >

3 3

Zinc server with static and non-static files
by Davide Varvello March 28, 2020

March 28, 2020

Hi Guys, Is it possible a Zinc server returns static files within a specific url path (like the ZnStaticFileServerDelegate) and also returns other logics as shown with map:#otherPath to: MyWebapp new ? TIA Davide -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

1 0

Do we have a simple markdown parser?
by Tim Mackinnon March 27, 2020

March 27, 2020

Hi guys - do we have a simple markdown parser that is reasonably up to date? I did a quick GitHub scan and a few popped out, but I wasnât convinced I had found one the âeveryoneâ uses (albeit, everyone might be a small sample). Ideally I donât want to get sucked into writing another one (a project for a future time). Tim

6 8

Today 27/03/2020: Pharo Sprint!
by Guillermo Polito March 27, 2020

March 27, 2020

Hi all, Today we are having a dematerialized Pharo sprint. # What is this sprint thingy? We join. We fix bugs. We discuss about fixing bugs. We add documentation. We review issues and pull requests. We make Pharo better for us and for everybody else :). # How is this sprint thing going on? In discord we have a text and a voice channel dedicated to #sprint. http://pharo.org/community <http://pharo.org/community> Please feel free to join and ask questions # What can I do to help? ## Get some knowledge => Read a couple of issues We have > 500 open issues. Some of them are difficult to reproduce, or the instructions are not clear enough, or maybe were already fixed but the issue was never closed. If everybody takes 3 issues at random and makes a review, we will be in much better shape for the next sprint!! Reviewing an issue is as easy as asking yourself the questions: - are there reproduction instructions? - it is specified the version / commit? - can I reproduce it? If some of those check fails, put a comment :) ## Get some action => Fix an easy issue In this morning (europe time) Iâve taken some time doing a pass on issues, and Iâve identified a list of potentially easy ones. https://github.com/pharo-project/pharo/issues?q=is%3Aissue+is%3Aopen+label%… <https://github.com/pharo-project/pharo/issues?q=is:issue+is:open+label:Easy> Iâve also categorised several of them as bugs, enhancements, new features and cleanups. Within those, youâll see - super-easy (like adding a comment), - medium-easy (like changing some code following the analysis on the issue) and - hard-easy like a cleanup refactoring So if somebody wants to do a contribution for the first time, this list of 26 issues is probably a good place to look at. The info of how to make a PR is in here https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo <https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo> ## Get to know other people involved in Pharo => Discuss with us in discord And have fun :) Guille

1 0

Re: [Pharo-users] Do we have a simple markdown parser?
by Tim Mackinnon March 27, 2020

March 27, 2020

Hmm I hadnât even thought of Xstreamsâ¦ I always thought it sounded cool, perhaps its a place to start - but as you mention, Iâm not sure it really gained traction in the Pharo world. My use case is quite simple as the markdown files are simple configuration (and maybe donât even need a parser - e.g. https://github.com/servirtium/demo-java-climate-tck/blob/master/src/test/mo… <https://github.com/servirtium/demo-java-climate-tck/blob/master/src/test/mo…>). I was hoping there might be something simple I could run with to help explore how best to use the config in those files. Lets see if anyone else mentions something thatâs a no-brainer. Tim > On 24 Mar 2020, at 18:40, gettimothy via Pharo-users <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> wrote: > > > From: gettimothy <gettimothy(a)zoho.com <mailto:gettimothy@zoho.com>> > Subject: Re: [Pharo-users] Do we have a simple markdown parser? > Date: 24 March 2020 at 18:40:42 GMT > To: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> > Cc: "Pharo Users Newsgroup" <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> > > > I do not know if it works on Pharo, but XTreams has a XTreams-Parsing section that I am currently working with. The existing Wikitext grammar was my starting point . > > https://github.com/squeak-smalltalk/squeak-ci/blob/master/package-load-scri… <https://github.com/squeak-smalltalk/squeak-ci/blob/master/package-load-scri…> > > the existing Grammar is under: > > XTreams-Parsing -> PEGParser > grammars->grammarWiki > > > Use case is: > > > | wikiGrammar wikiParser output| > Transcript clear. > wikiGrammar := PEGParser grammarWiki reading positioning. > wikiParser := PEGParser parserPEG parse: 'Grammar' stream: wikiGrammar actor: PEGParserParser new. > input := (your string input goes here) > output := wikiParser parse: 'Page' stream: input actor: PEGWikiGenerator new. > output inspect. > > hth > > ---- On Tue, 24 Mar 2020 13:51:31 -0400 Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote ---- > > Hi guys - do we have a simple markdown parser that is reasonably up to date? I did a quick GitHub scan and a few popped out, but I wasnât convinced I had found one the âeveryoneâ uses (albeit, everyone might be a small sample). > > Ideally I donât want to get sucked into writing another one (a project for a future time). > > Tim > > > >

2 7

[ANN] JRMPC Poll
by Richard Kenneth Eng March 26, 2020

March 26, 2020

https://jrmpc.ca/2020/03/20/what-makes-learning-smalltalk-challenging/ FWIW, 95% of respondents pointed to the lack of reference documentation for the class library as the major obstacle to learning Smalltalk/Pharo. Richard

8 9

Pharo float precision vs Python
by Tim Mackinnon March 25, 2020

March 25, 2020

Hi guys - I recall this came up a few months ago, but Iâm curious about the difference of Pharoâs use of Float64 vs Python - as I assumed that if languages use the same IEEE spec (or whatever spec it is) that simple stuff would be quite similar. I am curious why in Python adding these numbers: y = 987.9504418944 + 815.2627636718801 + 1099.3898999037601 + 1021.6996069333198 + 1019.8750146478401 + 1084.5603759764 + 1008.2985131833999 + 1194.9564575200002 + 893.9680444336799 + 1032.85460449136 + 905.9324633786798 + 1024.2805590819598 + 784.5488305664002 + 957.3522631840398 + 1001.7526196294 print(y) print(y / 15) Gives: 14832.682458496522 988.8454972331015 In pharo I have noticed an anomaly which I thought was precision but it may be something odd with iterators. y := 987.9504418944 + 815.2627636718801 + 1099.3898999037601 + 1021.6996069333198 + 1019.8750146478401 + 1084.5603759764 + 1008.2985131833999 + 1194.9564575200002 + 893.9680444336799 + 1032.85460449136 + 905.9324633786798 + 1024.2805590819598 + 784.5488305664002 + 957.3522631840398 + 1001.7526196294. y. y / 15. Gives the same as Python. BUT: z := {987.9504418944 . 815.2627636718801 . 1099.3898999037601 . 1021.6996069333198 . 1019.8750146478401 . 1084.5603759764 . 1008.2985131833999 . 1194.9564575200002 . 893.9680444336799 . 1032.85460449136 . 905.9324633786798 . 1024.2805590819598 . 784.5488305664002 . 957.3522631840398 . 1001.7526196294} sum. z. z / 15. Gives 14832.68245849652 988.8454972331014 Is this correct?

5 16

[ANN] Next Pharo Sprint: March 27
by Marcus Denker March 24, 2020

March 24, 2020

We will organize a Pharo sprint / Moose dojo March 27 Goals of this sprint: - Fix issues from tracker https://github.com/pharo-project/pharo/issues This is a Remote Sprint, it happens on Discord. http://pharo.org/contribute-events We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 A list of all Pharo Event of the year an be found here: https://association.pharo.org/events

1 0

Versioning and packaging?
by Rob Raisch March 23, 2020

March 23, 2020

Iâve noticed that the majority of projects in which I have an interest, from any repository, like Moose or PetitParser, fail to load into Pharo 8.0 throwing errors related to missing requirements. For example, filing in Moose into Pharo 8.0 fails with âError: Cannot resolve symbolic version #release1â. In the Catalog browser, Moose is tagged with âPharo3.0â. Does this imply that Moose only works in that version of Pharo only? PetitParser, which Moose requires, is tagged âPharo5.0â and PetitParser2 is tagged âPharo6.0â neither of which will work in Pharo 3.0. So, Iâm left wondering if Iâm doing something wrong, and how requirements are supposed to work when there are so many projects that depend on deprecated versions of Pharo. Thanks. /rr -- Rob Raisch, Internet Handyman

2 1

[ANN] Pharo Newsletter March 2020
by Marcus Denker March 23, 2020

March 23, 2020

[ANN] Pharo Newsletter March 2020 The Pharo Newsletter March 2020 has been sent to subscribers last week: https://mailchi.mp/pharo/pharo-newsletter-march-2020 To get it as soon as it is released, please subscribe here: http://eepurl.com/bykqWn

1 0