September 2018 - Pharo-users

Internet of Things in Smalltalk - meeting proposal
by CÃ©drick BÃ©ler Sept. 10, 2018

Sept. 10, 2018

Hi, We will have a meeting Tuesday afternoon on IoT at esug. More info later to see how we organize that. Should be after Â« show us your project Â» around 5 or 6 am. More info later especially on where the meeting will take place (might be around the beach). See you later for those interested (maybe answer there so that we can count and find an appropriate place). Cheers, Cedrick

3 2

Re: [Pharo-users] ZnURL and parsing URL with diacritics
by Sven Van Caekenberghe Sept. 10, 2018

Sept. 10, 2018

It would probably help if you gave a real example, a REST call that returns something (presumable JSON or XML) that contains a URL that is problematic. FWIW, the following do also work ('https://en.wikipedia.org/wiki/' , 'ÄeskÃ¡ republika' urlEncoded) asUrl. ('https://en.wikipedia.org/wiki/' , 'ÄeskÃ¡ republika' urlEncoded) asUrl retrieveContents. > On 10 Sep 2018, at 14:16, Petr Fischer via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Petr Fischer <petr.fischer(a)me.com> > Subject: Re: [Pharo-users] ZnURL and parsing URL with diacritics > Date: 10 September 2018 at 14:16:53 GMT+2 > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > OK. Thanks for examples. But in my case, the bad URL (with diacritics) comes directly from the Zomato.com REST API (they probably do not read specs), so I'll end up with a few "hacks" with strings. > > pf > > >> Hi, >> >>> On 10 Sep 2018, at 12:53, PBKResearch <peter(a)pbkresearch.co.uk> wrote: >>> >>> Hi Petr >>> >>> I have used #urlEncoded in the past, with success, to deal with German umlauts. The secret is to urlEncode just the part containing the diacritics. If you encode the whole url, the slashes are encoded, and this confuses Zinc, which segments the url before decoding. >>> >>> So I would expect you to be able to read your file with: >>> >>> ZnEasy get: 'http://domain.com/â,âÄÅ¡ÄÃ½Å¾.html' urlEncoded. >>> >>> However, this also fails with âASCII character expectedâ, and I canât understand why. The debug trace has too many levels for me to understand. Zinc is evidently getting in a mess trying to decode the urlEncoded string, but if we try: >>> >>> âÄÅ¡ÄÃ½Å¾.html' urlEncoded urlDecoded >>> >>> as a separate operation, it works OK. >>> >>> I think only Sven can explain this for you. >> >> The external representation of a URL with special characters is not the same as what an address bar or browser search field accepts. The latter is quite intelligent and accepts much broader input. >> >> ZnUrl parses the official external representation according to the spec. >> >> Internally, ZnUrl represents all components as resolved strings. The solution is to construct difficult/special URLs by hand. >> >> Here is an example: let's say we want to access the English Wikipedia page of the Czech Republic (the country) using its native name 'ÄeskÃ¡ republika' (which is not only non-ASCII, but non-Latin1 as well, so it needs a WideString and UTF-8 encoding). >> >> Here is one way to construct such a string. >> >> ZnUrl new >> scheme: #http; >> host: 'en.wikipedia.org'; >> addPathSegment: 'wiki'; >> addPathSegment: 'ÄeskÃ¡ republika'; >> yourself. >> >> Which gives a URL with the following external representation: >> >> http://en.wikipedia.org/wiki/%C4%8Cesk%C3%A1%20republika >> >> This can be parsed without problems. >> >> 'http://en.wikipedia.org/wiki/%C4%8Cesk%C3%A1%20republika' asUrl. >> >> You can send #retrieveContents to a URL to actually fetch it. >> >> ZnUrl new >> scheme: #http; >> host: 'en.wikipedia.org'; >> addPathSegment: 'wiki'; >> addPathSegment: 'ÄeskÃ¡ republika'; >> retrieveContents. >> >> Or you could use the url in a ZnClient object. >> >> BTW, there are many ways to construct URLs, I would maybe do the following. >> >> 'https://en.wikipedia.org/wiki' asUrl addPathSegment: 'ÄeskÃ¡ republika'; yourself. >> >> Or something like >> >> ZnClient new >> url: 'https://en.wikipedia.org/wiki'; >> addPathSegment: 'ÄeskÃ¡ republika'; >> get. >> >> HTH, >> >> Sven >> >>> HTH >>> >>> Peter Kenny >>> >>> >>> From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Petr Fischer via Pharo-users >>> Sent: 10 September 2018 10:07 >>> To: pharo-users(a)lists.pharo.org >>> Cc: Petr Fischer <petr.fischer(a)me.com> >>> Subject: [Pharo-users] ZnURL and parsing URL with diacritics >>> >>> Hello, >>> >>> when I try to parse this URL asUrl, error "ZnCharacterEncodingError: ASCII character expected" occurs: >>> >>> 'http://domain.com/ÄÅ¡ÄÃ½Å¾.html' asUrl. >>> >>> this also does not work: >>> >>> ZnEasy get: 'http://domain.com/ÄÅ¡ÄÃ½Å¾.html' >>> >>> How to solve this? In the web browser, URL with diacritics is OK. >>> >>> I tried also this: >>> >>> ZnEasy get: 'http://domain.com/ÄÅ¡ÄÃ½Å¾.html' urlEncoded. >>> >>> but this cripples the whole URL. >>> >>> Thanks! Petr Fischer >> >> > > >

1 0

Re: [Pharo-users] ZnURL and parsing URL with diacritics
by PBKResearch Sept. 10, 2018

Sept. 10, 2018

Hi Petr I have used #urlEncoded in the past, with success, to deal with German umlauts. The secret is to urlEncode just the part containing the diacritics. If you encode the whole url, the slashes are encoded, and this confuses Zinc, which segments the url before decoding. So I would expect you to be able to read your file with: ZnEasy get: 'http://domain.com/','ÄÅ¡ÄÃ½Å¾.html' urlEncoded. However, this also fails with 'ASCII character expected', and I can't understand why. The debug trace has too many levels for me to understand. Zinc is evidently getting in a mess trying to decode the urlEncoded string, but if we try: 'ÄÅ¡ÄÃ½Å¾.html' urlEncoded urlDecoded as a separate operation, it works OK. I think only Sven can explain this for you. HTH Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Petr Fischer via Pharo-users Sent: 10 September 2018 10:07 To: pharo-users(a)lists.pharo.org Cc: Petr Fischer <petr.fischer(a)me.com> Subject: [Pharo-users] ZnURL and parsing URL with diacritics Hello, when I try to parse this URL asUrl, error "ZnCharacterEncodingError: ASCII character expected" occurs: 'http://domain.com/ÄÅ¡ÄÃ½Å¾.html' asUrl. this also does not work: ZnEasy get: 'http://domain.com/ÄÅ¡ÄÃ½Å¾.html' How to solve this? In the web browser, URL with diacritics is OK. I tried also this: ZnEasy get: 'http://domain.com/ÄÅ¡ÄÃ½Å¾.html' urlEncoded. but this cripples the whole URL. Thanks! Petr Fischer

3 2

ZnURL and parsing URL with diacritics
by Petr Fischer Sept. 10, 2018

Sept. 10, 2018

Hello, when I try to parse this URL asUrl, error "ZnCharacterEncodingError: ASCII character expected" occurs: 'http://domain.com/ÄÅ¡ÄÃ½Å¾.html' asUrl. this also does not work: ZnEasy get: 'http://domain.com/ÄÅ¡ÄÃ½Å¾.html' How to solve this? In the web browser, URL with diacritics is OK. I tried also this: ZnEasy get: 'http://domain.com/ÄÅ¡ÄÃ½Å¾.html' urlEncoded. but this cripples the whole URL. Thanks! Petr Fischer

1 0

memorizing data between tests
by Ben Coman Sept. 9, 2018

Sept. 9, 2018

Say I want to write ten tests for different aspects of a web service point. Apart from the risk of relying on an external service, I'd like to poll the web service once rather than ten times. I wondering about the feasibility of memorizing data between test methods. Taking for example... TestCase subclass: #MyTest ... My understanding is that MyTest >> setUp is run once per test method. What I guess is missing is a #groupSetup that would be called at the start of a running a group of tests. MyTest >> groupSetup memorized := Dictionary new. MyTest >> getLiveDataOncePerRun ^ memorized at: 'data' ifAbsentPut: [ZnClient new get: ' http://someservice.com/liveData1'. MyTest >> test1 |data| data := self getLiveDataOncePerRun . self assert: data result1 equals: 'expected result 1' MyTest >> test2 |data| data := self getLiveDataOncePerRun. self assert: data result2 equals: 'expected result 2' cheers -ben

3 3

Re: [Pharo-users] Ready to use Roassal?
by Hilaire Sept. 9, 2018

Sept. 9, 2018

Hello Alexandre, Afterward, I have indicated that to this non-pharo user. Le 09/09/2018 Ã 11:36, Alexandre Bergel via Pharo-users a Ã©critÂ : > The agilevisualization.com website says: > > "Installing Roassal is easy. You need to install Pharo. Open the Catalog browser, and select Roassal. A video illustrating these steps is online.â > > How can I improve the installation instruction? > > Also, the Quickstart chapter details the steps: > http://agilevisualization.com/AgileVisualization/QuickStart/0101-QuickStart… I was confused as I did not find this zip file ready to download, as described in this quick start page. Hilaire -- Dr. Geo http://drgeo.eu

2 2

Pharo and Docker (some steps)
by Torsten Bergmann Sept. 9, 2018

Sept. 9, 2018

For those interested in Docker: I recently played with Pharo and Docker and summarized some of my steps in a small tutorial in my Pharo wiki: http://wiki.astares.com/pharo/613 There is also a page following Mike Filonovs suggestions on the Pharo docker file: http://wiki.astares.com/pharo/615 Maybe this is useful for others too. Bye T.

3 2

Ready to use Roassal?
by Hilaire Sept. 9, 2018

Sept. 9, 2018

Hi, Is there a ready to download and to use Roassal for end user? I found nothing on http://agilevisualization.com/ I can point a user to. User unaware of Pharo, Smalltalk, etc. Closest things I found is http://moosetechnology.org/#install. And likely instructions will not work for a linux user. Thanks Hilaire -- Dr. Geo http://drgeo.eu

3 3

Sept. 8, 2018

Hi all, Just to inform that a Camp Smalltalk will be at the terrace of the CaffÃ¨ delle Arti starting at 10am. CaffÃ¨ delle Arti Via del Fossario, 1, 09124 Cagliari CA, Italie +39 392 396 3958 https://goo.gl/maps/WMRhdSCeZL62 Feel free to join

1 0

Re: [Pharo-users] CampSmalltalk
by Joachim Tuchel Sept. 8, 2018

Sept. 8, 2018

Waiting at the baggage claim ;-) > Am 08.09.2018 um 05:41 schrieb Sebastian Heidbrink <sheidev(a)yahoo.de>: > > Hi! > > I just found out that there is a dedicated ESUG mailing list.... ta taa! > > I arrived in Cagliari for ESUG 2018 and I am wondering where CampSmalltalk will take place this weekend. > > Anybody in town already? > > CU! > > Kind wishes, > > Sebastian > > > >

3 2