September 2018 - Pharo-users

Re: [Pharo-users] [Esug-list] Internet of Things in Smalltalk - meeting proposal

by tesonep＠gmail.com

Nice idea. I will try to be there. On Mon, 10 Sep 2018, 16:09 CÃ©drick BÃ©ler, <cdrick65(a)gmail.com> wrote: > 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 > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >

Sept. 10, 2018

Re: [Pharo-users] Internet of Things in Smalltalk - meeting proposal

by Guillermo Polito

I'll be there :) On Mon, Sep 10, 2018 at 4:09 PM CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > 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 > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Sept. 10, 2018

Internet of Things in Smalltalk - meeting proposal

by CÃ©drick BÃ©ler

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

Sept. 10, 2018

Re: [Pharo-users] ZnURL and parsing URL with diacritics

by Sven Van Caekenberghe

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

Sept. 10, 2018

Re: [Pharo-users] ZnURL and parsing URL with diacritics

by Petr Fischer

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

Sept. 10, 2018

Re: [Pharo-users] ZnURL and parsing URL with diacritics

by Sven Van Caekenberghe

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

Sept. 10, 2018

Re: [Pharo-users] ZnURL and parsing URL with diacritics

by PBKResearch

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

Sept. 10, 2018

ZnURL and parsing URL with diacritics

by Petr Fischer

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

Sept. 10, 2018

Re: [Pharo-users] memorizing data between tests

by Esteban Maringolo

You can use a TestResource for it, and use some sort of memoization. I don't know if there is a library for memoization in Pharo, but if the HTTP calls are not that many you can implement it by having a cache in the test resource, implemented as a dictionary, with the URL as key and its cached response as value. Regards, Esteban A. Maringolo El dom., 9 sept. 2018 a las 5:11, Peter Uhnak (<i.uhnak(a)gmail.com>) escribiÃ³: > > Hi Ben, > > take a look at TestResource (its comment and subclasses). It should do what you are looking for. > > Peter > > On Sun, Sep 9, 2018 at 8:08 AM Ben Coman <btc(a)openinworld.com> wrote: >> >> 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 >>

Sept. 9, 2018

Re: [Pharo-users] Ready to use Roassal?

by Hilaire

Le 09/09/2018 Ã 15:06, Peter Uhnak a Ã©critÂ : > Not sure if this is already fixed in P7, but in P6 sometimes the > catalog would not load properly... so one has to close pharo and open > it again... probably not the best experience for non-pharo user. This was my taught too. > > Also, if your user is using linux, they also need to have > libcairo(i386) installed, otherwise Roassal will not work. This one is ok, this is a Dr. Geo user. Hilaire -- Dr. Geo http://drgeo.eu

Sept. 9, 2018