September 2020 - Pharo-users

how to check for the statusCode

by Roelof Wobben

Hello, Sorry for asking so much questions but I lost the big picture right now. Im trying to get the response object back from a api call. That I can do with : ` response := ZnEasy get: url. ` and I see that it has the fields statusline which has the field code I thought I could use it like this :Â response at: #statusline ` but that give me a error message thatÂ indexes needs to be integers. How do I get the code field again ? Roelof

Sept. 28, 2020

Re: Standalone html builder (a la seaside without seaside?)

by Eric Gade

> On 28 Sep 2020, at 19:28, Tim Mackinnon <tim(a)testit.works> wrote: > > > I often find I want to build some HTML, but donât want the full seaside > - and was wondering if anyone has managed to extract it, or have something > similar? > I had a similar thought a few months back when I was looking for libraries to build a lightweight static site generator for personal use (I gave up due to time constraints) > Hi - has anyone ever managed to extract the html builder out of seaside - > or written something equivalent? > You might want to dip into the code for Amber Smalltalk. From what I recall, that system was able to extract the TagBrush and related classes -- Eric

Sept. 28, 2020

Re: Standalone html builder (a la seaside without seaside?)

by Sven Van Caekenberghe

Hi Tim, > On 28 Sep 2020, at 19:28, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - has anyone ever managed to extract the html builder out of seaside - or written something equivalent? > > I often find I want to build some HTML, but donât want the full seaside - and was wondering if anyone has managed to extract it, or have something similar? > > This combined with Renoir from BA-ST would give a good little light weight web potential to run with Zinc. > > Tim There is a minimal HTML builder to be found in ZnHtmlOutputStream. It is used for a couple of examples and default functionality of ZnServer. There are even unit tests. It is not the same as the Seaside HTML approach though. Sven

Sept. 28, 2020

Standalone html builder (a la seaside without seaside?)

by Tim Mackinnon

Hi - has anyone ever managed to extract the html builder out of seaside - or written something equivalent? I often find I want to build some HTML, but donât want the full seaside - and was wondering if anyone has managed to extract it, or have something similar? This combined with Renoir from BA-ST would give a good little light weight web potential to run with Zinc. Tim

Sept. 28, 2020

Re: how the best deal with this

by Roelof Wobben

Sept. 28, 2020

Re: how the best deal with this

by Sven Van Caekenberghe

> On 28 Sep 2020, at 07:28, Roelof Wobben via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hello, > > I have this code : > > getMoreData > | url url2 json json2 artObjectJson levelsJson| > url := 'https://www.rijksmuseum.nl/api/nl/collection/' , objectNumber > , '?key=14OGzuak&format=json'. > url2 := 'https://www.rijksmuseum.nl/api/nl/collection/' > , objectNumber , '/tiles?key=14OGzuak'. > "Read the data from the api respons" > json := NeoJSONReader fromString: (ZnEasy get: url) contents. > artObjectJson := json at: #artObject. > painter := ((artObjectJson at: #principalMakers) at: 1) at: #name. > title := artObjectJson at: #title. > "Read the imageUrl from the api respons" > json2 := NeoJSONObject fromString: (ZnEasy get: 'https://www.rijksmuseum.nl/api/nl/collection/SK-C-1368/tiles?key=14OGzuak') contents utf8Decoded. > levelsJson := (json2 at: #levels). > imageUrl := levelsJson at: 1. > > but now I see that somethimes ZnEasy get: url gives a document of zero bytes. > Now can I put the rest in a big ifFalse block or make another function for it or is there a better more smalltalk way of dealing with this "problem". > > Roelof I think it would be good if you ask de rijksmuseum api guys to explain why https://www.rijksmuseum.nl/api/nl/collection/SK-C-1368 is correctly typed with content-type application/json, while https://www.rijksmuseum.nl/api/nl/collection/SK-C-1368/tiles has a missing content-type (while it is clearly also application/json). Your code can be improved as well. If you do your parsing via NeoJSONObject, you do not get Dictionaries back, but instances of NeoJSONObject (a subclass of Dictionary). These behave more like JavaScript maps/objects. You can use accessors, as if they exist, and they will turned into #at: accesses, with the additional feature of returning nil when the property is not found. So, for example, at the end, you can say json2 levels. Instead of at: 1 you can use first, together this gives you json2 levels first. The same approach is possible for the first json expression and its subsequent use (but parse via NeoJSONObject fromString:). json artObject principalMarkers first name. Coming back to your problem, 'sometimes' is not a bug report we can work on, it does not sound good. It could be that the server returns an empty response. But normally, if something is wrong, you should get a real error. The API seems cool though, I got a nice painting back retrieving one of the embedded URLs (artObject->webImage->url) using ZnEasy getJpeg: 'https://lh3.googleusercontent.com/N2m90mImdcoLacUybb_rxcktTwtr0LFhtuzxbSE9e…'. If you use the Form tab in the inspector, you can see the image

Sept. 28, 2020

how the best deal with this

by Roelof Wobben

Hello, I have this code : getMoreData Â Â Â | url url2 json json2 artObjectJson levelsJson| Â Â Â url := 'https://www.rijksmuseum.nl/api/nl/collection/' , objectNumber Â Â Â Â Â Â , '?key=14OGzuak&format=json'. Â Â Â url2 := 'https://www.rijksmuseum.nl/api/nl/collection/' Â Â Â Â Â Â , objectNumber , '/tiles?key=14OGzuak'. Â Â Â "Read the data from the api respons" Â Â Â json := NeoJSONReader fromString: (ZnEasy get: url) contents. Â Â Â artObjectJson := json at: #artObject. Â Â Â painter := ((artObjectJson at: #principalMakers) at: 1) at: #name. Â Â Â title := artObjectJson at: #title. Â Â Â "Read the imageUrl from the api respons" Â Â Â json2 := NeoJSONObject fromString: (ZnEasy get: 'https://www.rijksmuseum.nl/api/nl/collection/SK-C-1368/tiles?key=14OGzuak') contents utf8Decoded. Â Â Â levelsJson := (json2 at: #levels). Â Â Â imageUrl :=Â levelsJson at: 1. but now I see that somethimes ZnEasy get: urlÂ Â gives a document of zero bytes. Now can I put the rest in a big ifFalse block or make another function for it or is there a better more smalltalk way of dealing with this "problem". Roelof

Sept. 28, 2020

Re: why is ZnEasy choking on this and languages as c# and ruby not

by Esteban Maringolo

Hi Roelof, As pointed in the Discord chat, and just for others to know, the HTTP response is not correct since it doesn't set any MIME Type, so Zinc (ZnEasy) does the correct thing that it is to assume the content is application/octet-stream, so you get a ByteArray. If you decode such bytearray using UTF8 you'll get the "text" you're expecting. Just out of curiosity, can you show us a snippet of how you do that in C# and Ruby? Regards, Esteban A. Maringolo On Sun, Sep 27, 2020 at 2:35 PM Roelof Wobben via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hello, > > In a project of mine I do this : > > (ZnEasy get: 'https://www.rijksmuseum.nl/api/nl/collection/SK-C-1368/tiles?key=14OGzuak') contents . > > but this is given me a bytearray. > > When I do the same in other languages I know like c# or ruby I get a dictionary like I suspect. > > > Can som one explain to me why this happens with ZnEasy. > > Regards, > > Roelof >

Sept. 27, 2020

Re: why is ZnEasy choking on this and languages as c# and ruby not

by Sven Van Caekenberghe

> On 27 Sep 2020, at 19:34, Roelof Wobben via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hello, > > In a project of mine I do this : > > (ZnEasy get: 'https://www.rijksmuseum.nl/api/nl/collection/SK-C-1368/tiles?key=14OGzuak' > ) contents . > > but this is given me a bytearray. > > When I do the same in other languages I know like c# or ruby I get a dictionary like I suspect. > > > Can som one explain to me why this happens with ZnEasy. > > Regards, > > Roelof This website/webservice has an incomplete http 1.1 fallback IMHO, as it does not set the content-type of the response - in that case the default is application/octet-stream, hence a ByteArray. You can see this when you ask curl to use http 1.1 $ curl -v --http1.1 https://www.rijksmuseum.nl/api/nl/collection/SK-C-1368/tiles?key=14OGzuak You will see there is no content-type in the response. Now, curl too will seemingly show you the expected text, but that is an assumption it cannot actually make (it does this in a unix tradition). Now, since we know/expect textual JSON data (apparently), you can make the request work as follows: (ZnEasy get: 'https://www.rijksmuseum.nl/api/nl/collection/SK-C-1368/tiles?key=14OGzuak') contents utf8Decoded. When you have NeoJSON load, you can parse as follows: NeoJSONObject fromString: (ZnEasy get: 'https://www.rijksmuseum.nl/api/nl/collection/SK-C-1368/tiles?key=14OGzuak') contents utf8Decoded. Sven

Sept. 27, 2020

why is ZnEasy choking on this and languages as c# and ruby not

by Roelof Wobben

Sept. 27, 2020