- Pharo-users - lists.pharo.org

Re: [Pharo-users] PetitParser and PPBrowser in Pharo 3.0

by Hartmut

Hi Doru, Thanks for such a quick response. I had to change the fonts for Default AND for Button to a TrueTypeFont. PPBrowser now works for me, thanks. Hartmut PS: After loading the script from 'GTToolkit' activateWithoutSaving was still unknown Am 31.12.14 14:14, schrieb Tudor Girba: > Hi, > > PPBrowser uses Roassal which relies on the Athens canvas which > requires FreeType fonts :). > > To fix this, you can go to Settings: > - Make Use Free type ... true > - Choose a Free type font as the default one. > > Or you can just use the Moose 5.0 image: > http://moosetechnology.org/#install > > Or you can use some ready made setup script we have in Moose: > Gofer new > smalltalkhubUser: 'Moose' project: 'GToolkit'; > package: 'GT-Setup'; > load. > #GTImageSetupCommandLineHandler asClass activateWithoutSaving > > Cheers, > Doru > > > > On Wed, Dec 31, 2014 at 2:10 PM, Hartmut <krasemann(a)acm.org > <mailto:krasemann@acm.org>> wrote: > > Hi Jan, > > since a while I get a MessageNotUnderstood on PPBrowser open after > ConfigurationOfPetitParser loadDevelopment. > Has to do with fonts. > Debugger Stack fueled out can be accessed here: > https://dl.dropboxusercontent.com/u/4548797/Debugger-Stack-StrikeFont-2014-… > > Regards, Hartmut > > Am 16.12.14 14:34, schrieb Jan KurÅ¡: >> Hi, >> >> Anyone experience with Athens can help with the first issue? >> TRLabelShape>>drawOn: seem to be somehow responsible, but I don't >> see into this :( >> >> Regarding to the second issue, there are some cases, when one >> really needs a start rule, e.g when computing follow. Yet I >> updated the code so that it handles missing start rule a bit better. >> >> Please, let me know, if you have some other ideas/suggestions/issues. >> >> Regards, >> Jan >> >> On 9 December 2014 at 15:17, Hartmut <krasemann(a)acm.org >> <mailto:krasemann@acm.org>> wrote: >> >> Hi to all, >> >> I'm working with PetitParser in a Pharo 3 image. >> Until now I had to do without the PPBrowser which I loved in >> Pharo 2. >> >> On forum.world.st <http://forum.world.st> I now found the >> hint by Jan Kurs to install all of the Petit suite: >> >> > "Configuration should be loaded like this:" >> > Gofer new smalltalkhubUser: 'Moose' project: 'PetitParser'; >> > configurationOf: #PetitParser; load. >> > >> > "All the petit parser suite:" >> > ConfigurationOfPetitParser loadDevelopment. >> >> Apart from the fact that this installed a real lot into my >> image, I notice the following problems >> in PPBrowser: >> >> 1. The map of none of the 18 parsers included, is displayed >> (it becomes red crossed). >> However, this was the most useful part of it >> >> 2. My interrelated parsers consist of a tree of parsers where >> each leave has its own start clause. >> They define related languages. It makes no sense to add a >> /start/ clause to the root. >> However, without such a meaningless /start/ clause, only >> the /source/ is displayed, >> neither /graph, example, first/ or /follow/ of any clause. >> (this can be reproduced when you move >> PPJsonGrammar>>start to PPJsonParser) >> >> I like the style of having a grammar class above a parser (or >> compiler) class. >> This is as seen in most of the accompanying parsers. >> My preferred petit parser style comprises: >> a) keeping grammar rules (without ==>) in the upper >> classes of the grammar hierarchy tree, >> such that we find the complete grammar there (without >> the /start/ clause). >> b) keeping replacement rules (using ==>) as low as >> possible the grammar hierarchy tree >> c) writing the start clause to the class that is actually >> called. (this gives different entries >> in a grammar allowing for different languages with >> grammar subsets) >> >> Is there an idea to have 1. and/or 2. resolved? >> >> Hartmut >> >> -- >> Hartmut Krasemannâ¨ >> KÃ¶nigsberger Str. 41 c >> â¨D 22869 Schenefeldâ¨ >> Tel. 040.8307097â¨ >> Mobil 0171.6451283â¨ >> krasemann(a)acm.org <mailto:krasemann@acm.org> >> > > -- > Hartmut Krasemannâ¨ > KÃ¶nigsberger Str. 41 c > â¨D 22869 Schenefeldâ¨ > Tel. 040.8307097â¨ > Mobil 0171.6451283â¨ > krasemann(a)acm.org <mailto:krasemann@acm.org> > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow" -- Hartmut Krasemannâ¨ KÃ¶nigsberger Str. 41 c â¨D 22869 Schenefeldâ¨ Tel. 040.8307097â¨ Mobil 0171.6451283â¨ krasemann(a)acm.org

Dec. 31, 2014

Re: [Pharo-users] PetitParser and PPBrowser in Pharo 3.0

by Tudor Girba

Hi, PPBrowser uses Roassal which relies on the Athens canvas which requires FreeType fonts :). To fix this, you can go to Settings: - Make Use Free type ... true - Choose a Free type font as the default one. Or you can just use the Moose 5.0 image: http://moosetechnology.org/#install Or you can use some ready made setup script we have in Moose: Gofer new smalltalkhubUser: 'Moose' project: 'GToolkit'; package: 'GT-Setup'; load. #GTImageSetupCommandLineHandler asClass activateWithoutSaving Cheers, Doru On Wed, Dec 31, 2014 at 2:10 PM, Hartmut <krasemann(a)acm.org> wrote: > Hi Jan, > > since a while I get a MessageNotUnderstood on PPBrowser open after > ConfigurationOfPetitParser loadDevelopment. > Has to do with fonts. > Debugger Stack fueled out can be accessed here: > https://dl.dropboxusercontent.com/u/4548797/Debugger-Stack-StrikeFont-2014-… > > Regards, Hartmut > > Am 16.12.14 14:34, schrieb Jan KurÅ¡: > > Hi, > > Anyone experience with Athens can help with the first issue? > TRLabelShape>>drawOn: seem to be somehow responsible, but I don't see into > this :( > > Regarding to the second issue, there are some cases, when one really > needs a start rule, e.g when computing follow. Yet I updated the code so > that it handles missing start rule a bit better. > > Please, let me know, if you have some other ideas/suggestions/issues. > > Regards, > Jan > > On 9 December 2014 at 15:17, Hartmut <krasemann(a)acm.org> wrote: >> >> Hi to all, >> >> I'm working with PetitParser in a Pharo 3 image. >> Until now I had to do without the PPBrowser which I loved in Pharo 2. >> >> On forum.world.st I now found the hint by Jan Kurs to install all of the >> Petit suite: >> >> > "Configuration should be loaded like this:" >> > Gofer new smalltalkhubUser: 'Moose' project: 'PetitParser'; >> > configurationOf: #PetitParser; load. >> > >> > "All the petit parser suite:" >> > ConfigurationOfPetitParser loadDevelopment. >> >> Apart from the fact that this installed a real lot into my image, I >> notice the following problems >> in PPBrowser: >> >> 1. The map of none of the 18 parsers included, is displayed (it becomes >> red crossed). >> However, this was the most useful part of it >> >> 2. My interrelated parsers consist of a tree of parsers where each leave >> has its own start clause. >> They define related languages. It makes no sense to add a *start* >> clause to the root. >> However, without such a meaningless *start* clause, only the *source* >> is displayed, >> neither *graph, example, first* or *follow* of any clause. >> (this can be reproduced when you move PPJsonGrammar>>start to >> PPJsonParser) >> >> I like the style of having a grammar class above a parser (or compiler) >> class. >> This is as seen in most of the accompanying parsers. >> My preferred petit parser style comprises: >> a) keeping grammar rules (without ==>) in the upper classes of the >> grammar hierarchy tree, >> such that we find the complete grammar there (without the *start* >> clause). >> b) keeping replacement rules (using ==>) as low as possible the >> grammar hierarchy tree >> c) writing the start clause to the class that is actually called. >> (this gives different entries >> in a grammar allowing for different languages with grammar subsets) >> >> Is there an idea to have 1. and/or 2. resolved? >> >> Hartmut >> >> -- >> Hartmut Krasemann >> KÃ¶nigsberger Str. 41 c >> â¨D 22869 Schenefeld >> Tel. 040.8307097 >> Mobil 0171.6451283â¨krasemann(a)acm.org >> >> > -- > Hartmut Krasemann > KÃ¶nigsberger Str. 41 c > â¨D 22869 Schenefeld > Tel. 040.8307097 > Mobil 0171.6451283â¨krasemann(a)acm.org > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 31, 2014

Re: [Pharo-users] PetitParser and PPBrowser in Pharo 3.0

by Hartmut

Hi Jan, since a while I get a MessageNotUnderstood on PPBrowser open after ConfigurationOfPetitParser loadDevelopment. Has to do with fonts. Debugger Stack fueled out can be accessed here: https://dl.dropboxusercontent.com/u/4548797/Debugger-Stack-StrikeFont-2014-… Regards, Hartmut Am 16.12.14 14:34, schrieb Jan KurÅ¡: > Hi, > > Anyone experience with Athens can help with the first issue? > TRLabelShape>>drawOn: seem to be somehow responsible, but I don't see > into this :( > > Regarding to the second issue, there are some cases, when one really > needs a start rule, e.g when computing follow. Yet I updated the code > so that it handles missing start rule a bit better. > > Please, let me know, if you have some other ideas/suggestions/issues. > > Regards, > Jan > > On 9 December 2014 at 15:17, Hartmut <krasemann(a)acm.org > <mailto:krasemann@acm.org>> wrote: > > Hi to all, > > I'm working with PetitParser in a Pharo 3 image. > Until now I had to do without the PPBrowser which I loved in Pharo 2. > > On forum.world.st <http://forum.world.st> I now found the hint by > Jan Kurs to install all of the Petit suite: > > > "Configuration should be loaded like this:" > > Gofer new smalltalkhubUser: 'Moose' project: 'PetitParser'; > > configurationOf: #PetitParser; load. > > > > "All the petit parser suite:" > > ConfigurationOfPetitParser loadDevelopment. > > Apart from the fact that this installed a real lot into my image, > I notice the following problems > in PPBrowser: > > 1. The map of none of the 18 parsers included, is displayed (it > becomes red crossed). > However, this was the most useful part of it > > 2. My interrelated parsers consist of a tree of parsers where each > leave has its own start clause. > They define related languages. It makes no sense to add a > /start/ clause to the root. > However, without such a meaningless /start/ clause, only the > /source/ is displayed, > neither /graph, example, first/ or /follow/ of any clause. > (this can be reproduced when you move PPJsonGrammar>>start to > PPJsonParser) > > I like the style of having a grammar class above a parser (or > compiler) class. > This is as seen in most of the accompanying parsers. > My preferred petit parser style comprises: > a) keeping grammar rules (without ==>) in the upper classes of > the grammar hierarchy tree, > such that we find the complete grammar there (without the > /start/ clause). > b) keeping replacement rules (using ==>) as low as possible the > grammar hierarchy tree > c) writing the start clause to the class that is actually > called. (this gives different entries > in a grammar allowing for different languages with grammar > subsets) > > Is there an idea to have 1. and/or 2. resolved? > > Hartmut > > -- > Hartmut Krasemannâ¨ > KÃ¶nigsberger Str. 41 c > â¨D 22869 Schenefeldâ¨ > Tel. 040.8307097â¨ > Mobil 0171.6451283â¨ > krasemann(a)acm.org <mailto:krasemann@acm.org> > -- Hartmut Krasemannâ¨ KÃ¶nigsberger Str. 41 c â¨D 22869 Schenefeldâ¨ Tel. 040.8307097â¨ Mobil 0171.6451283â¨ krasemann(a)acm.org

Dec. 31, 2014

Traveling from Pharo Days to FOSDEM

by Rafael Luque

Hi Pharoers, I will attend Pharo Days with a friend and after the conference we'd like to attend FOSDEM. Which the best way to travel to Brussels from Lille? Thank you and see you in Pharo Days.

Dec. 31, 2014

Re: [Pharo-users] pharo at google code-in

by stepharo

Created jenkins job to produce the PDFs I just realized that I lost some of my edits in the Spec chapter. https://ci.inria.fr/pharo-contribution/job/PharoBookWorkInProgress/ws/ https://ci.inria.fr/pharo-contribution/job/PharoBookWorkInProgress/1/artifa… Stef

Dec. 31, 2014

Re: [Pharo-users] pharo at google code-in

by stepharo

Le 31/12/14 08:03, Martin BÃ¤hr a Ã©crit : > Excerpts from Martin BÃ¤hr's message of 2014-12-24 19:48:47 +0100: >> i have been meaning to learn smalltalk for a while, but i always lacked a good >> project that i could do with it, until recently. and figuring that teaching is >> the best way to learn i put up my projects as tasks for google code-in as part >> of FOSSASIA which is a code-in mentor organization. > i posted a write-up of the smalltalk projects and tasks here: > http://societyserver.org/mbaehr/learning-smalltalk-with-Google-Code-In > > i'll be updating that as students work progresses and if i add new tasks. > > i am also still looking for tutorials that can be used to start learning pharo. > in particular for spec and desktop apps in general, but i don't mind having > more options for webframeworks too. I will make sure that the Spec chapter compile and I will let you know. There are hosted at https://github.com/SquareBracketAssociates/PharoInProgress I will create a jenkins job > > so far i have 4 students started on smalltalk, one of them didn't continue > after the tutorial (so i reopened the task for others), and one who is learning > amber. we'll see if any of them pick up the actual project tasks. I strongly suggest them to register to the mailing-lists and ask questions. Tell them that we are all happy to help them. Stef > > greetings, martin. >

Dec. 31, 2014

Re: [Pharo-users] pharo at google code-in

by Martin BÃ¤hr

Excerpts from Martin BÃ¤hr's message of 2014-12-24 19:48:47 +0100: > i have been meaning to learn smalltalk for a while, but i always lacked a good > project that i could do with it, until recently. and figuring that teaching is > the best way to learn i put up my projects as tasks for google code-in as part > of FOSSASIA which is a code-in mentor organization. i posted a write-up of the smalltalk projects and tasks here: http://societyserver.org/mbaehr/learning-smalltalk-with-Google-Code-In i'll be updating that as students work progresses and if i add new tasks. i am also still looking for tutorials that can be used to start learning pharo. in particular for spec and desktop apps in general, but i don't mind having more options for webframeworks too. so far i have 4 students started on smalltalk, one of them didn't continue after the tutorial (so i reopened the task for others), and one who is learning amber. we'll see if any of them pick up the actual project tasks. greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org BLUG secretary beijinglug.org foresight developer foresightlinux.org realss.com unix sysadmin Martin BÃ¤hr working in china http://societyserver.org/mbaehr/

Dec. 31, 2014

Re: [Pharo-users] ZnClient Error - Improper store into indexable object

by stepharo

Sven this is a really cool answer! May be we should add that somewhere :) Stef Le 29/12/14 20:16, Sven Van Caekenberghe a Ã©crit : > Hi Edward, > >> On 29 Dec 2014, at 17:19, Edward Povazan <empovazan(a)gmail.com> wrote: >> >> I am playing around with Zinc, and I get an >> "Error - Improper store into indexable objectâ >> at >> ZnBufferedWriteStream>>nextPut: >> >> My Workspace: >> ----- >> | response | >> response := ZnClient new >> url:'http://amazon.com'; >> get; >> response. >> >> response writeOn: Transcript. >> Transcript flush >> ----- >> >> The reason is that instead of a Character, there is a SmallInteger of value 10 being added at ByteString>>at:put: (and 10 is a linefeed). >> >> Also the string in the entity is a WideString (ZnUTF8Encoder>>next:putAll:startingAt:toStream is where the choice is made to decode a ByteString vs WideString). >> >> Is this a bug? Running on Pharo 3. My newb debugging skills donât go further :( Other sites that fail are reddit.com, news.ycombinator.com. >> >> Thanks, >> -Ed > Short answer: > > Zinc writes to or reads from binary streams, the Transcript is a character stream. I know that what you are trying to do is actually in the documentation and in the API, and it normally works, just not in all cases. It is better to use inspection to look at what is going on, you'll get a much more structured (object-oriented) view of what is going on. I would suggest inspecting the ZnClient instance, which will hold the state of the last request and response. > > Long answer: > > If you try > > | response | > response := ZnClient new > url:'http://stfx.eu/small.html'; > get; > response. > > response writeToTranscript. > > It will work and print > > HTTP/1.1 200 OK > X-Pad: avoid browser bug > Date: Mon, 29 Dec 2014 18:56:37 GMT > Content-Length: 113 > Etag: "202f9-71-4c7ae94364f1e" > Server: Apache/2.2.22 (Ubuntu) > Accept-Ranges: bytes > Last-Modified: Mon, 20 Aug 2012 08:48:51 GMT > Vary: Accept-Encoding > Content-Type: text/html > > <html> > <head><title>Small</title></head> > <body><h1>Small</h1><p>This is a small HTML document</p></body> > </html> > > So what is the difference ? > > The fact that the responses that you get from the website you mention are using chunked transfer encoding (http://en.wikipedia.org/wiki/Chunked_transfer_encoding) Zinc deals with this in both ways, while reading a response, but also while writing a response (which is what you are trying to do here). > > Here is how you disable chunked transfer encoding so that you can write the response to the Transcript > > | response | > response := ZnClient new > url:'http://amazon.com'; > get; > response. > > response headers removeKey: 'Transfer-Encoding'. > response writeToTranscript. > > Zinc manages to write to the Transcript in most cases by cheating a bit: it wraps a ZnBivalentWriteStream around another stream when needed - such a stream can do both binary and character writing at the same time (though the result is only good for quick and dirty debugging, since it is not 100% correct). > > I hope the long explanation didn't make it worse ;-) > > HTH, > > Sven > > PS: BTW, in Pharo 4 with Zinc #bleedingEdge you get even nicer and more high level presentations of Zinc objects in GT-Inspector ! > > >

Dec. 29, 2014

Re: [Pharo-users] ZnClient Error - Improper store into indexable object

by Edward Povazan

Sven, thank you so much for the detailed explanation. I used it to look at the debugger again so I could reformulate the way I look for bugs. Iâd was looking backwards from the error, but had I started at the DoIt, I would have seen the ZnBivalentWriteStream and seen the class comment. Moreover, I would have realized it all starts with the Transcript. I guess habits from my other environment (iOS, where the stack leads into closed source). And here in Pharo I can inspect the MethodContext and see the program counter :) Thanks again, -Edward > On Dec 29, 2014, at 11:16 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Edward, > >> On 29 Dec 2014, at 17:19, Edward Povazan <empovazan(a)gmail.com> wrote: >> >> I am playing around with Zinc, and I get an >> "Error - Improper store into indexable objectâ >> at >> ZnBufferedWriteStream>>nextPut: >> >> My Workspace: >> ----- >> | response | >> response := ZnClient new >> url:'http://amazon.com'; >> get; >> response. >> >> response writeOn: Transcript. >> Transcript flush >> ----- >> >> The reason is that instead of a Character, there is a SmallInteger of value 10 being added at ByteString>>at:put: (and 10 is a linefeed). >> >> Also the string in the entity is a WideString (ZnUTF8Encoder>>next:putAll:startingAt:toStream is where the choice is made to decode a ByteString vs WideString). >> >> Is this a bug? Running on Pharo 3. My newb debugging skills donât go further :( Other sites that fail are reddit.com, news.ycombinator.com. >> >> Thanks, >> -Ed > > Short answer: > > Zinc writes to or reads from binary streams, the Transcript is a character stream. I know that what you are trying to do is actually in the documentation and in the API, and it normally works, just not in all cases. It is better to use inspection to look at what is going on, you'll get a much more structured (object-oriented) view of what is going on. I would suggest inspecting the ZnClient instance, which will hold the state of the last request and response. > > Long answer: > > If you try > > | response | > response := ZnClient new > url:'http://stfx.eu/small.html'; > get; > response. > > response writeToTranscript. > > It will work and print > > HTTP/1.1 200 OK > X-Pad: avoid browser bug > Date: Mon, 29 Dec 2014 18:56:37 GMT > Content-Length: 113 > Etag: "202f9-71-4c7ae94364f1e" > Server: Apache/2.2.22 (Ubuntu) > Accept-Ranges: bytes > Last-Modified: Mon, 20 Aug 2012 08:48:51 GMT > Vary: Accept-Encoding > Content-Type: text/html > > <html> > <head><title>Small</title></head> > <body><h1>Small</h1><p>This is a small HTML document</p></body> > </html> > > So what is the difference ? > > The fact that the responses that you get from the website you mention are using chunked transfer encoding (http://en.wikipedia.org/wiki/Chunked_transfer_encoding) Zinc deals with this in both ways, while reading a response, but also while writing a response (which is what you are trying to do here). > > Here is how you disable chunked transfer encoding so that you can write the response to the Transcript > > | response | > response := ZnClient new > url:'http://amazon.com'; > get; > response. > > response headers removeKey: 'Transfer-Encoding'. > response writeToTranscript. > > Zinc manages to write to the Transcript in most cases by cheating a bit: it wraps a ZnBivalentWriteStream around another stream when needed - such a stream can do both binary and character writing at the same time (though the result is only good for quick and dirty debugging, since it is not 100% correct). > > I hope the long explanation didn't make it worse ;-) > > HTH, > > Sven > > PS: BTW, in Pharo 4 with Zinc #bleedingEdge you get even nicer and more high level presentations of Zinc objects in GT-Inspector ! > >

Dec. 29, 2014

Re: [Pharo-users] ZnClient Error - Improper store into indexable object

by Sven Van Caekenberghe

> On 29 Dec 2014, at 20:16, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Edward, > >> On 29 Dec 2014, at 17:19, Edward Povazan <empovazan(a)gmail.com> wrote: >> >> I am playing around with Zinc, and I get an >> "Error - Improper store into indexable objectâ >> at >> ZnBufferedWriteStream>>nextPut: >> >> My Workspace: >> ----- >> | response | >> response := ZnClient new >> url:'http://amazon.com'; >> get; >> response. >> >> response writeOn: Transcript. >> Transcript flush >> ----- >> >> The reason is that instead of a Character, there is a SmallInteger of value 10 being added at ByteString>>at:put: (and 10 is a linefeed). >> >> Also the string in the entity is a WideString (ZnUTF8Encoder>>next:putAll:startingAt:toStream is where the choice is made to decode a ByteString vs WideString). >> >> Is this a bug? Running on Pharo 3. My newb debugging skills donât go further :( Other sites that fail are reddit.com, news.ycombinator.com. >> >> Thanks, >> -Ed > > Short answer: > > Zinc writes to or reads from binary streams, the Transcript is a character stream. I know that what you are trying to do is actually in the documentation and in the API, and it normally works, just not in all cases. It is better to use inspection to look at what is going on, you'll get a much more structured (object-oriented) view of what is going on. I would suggest inspecting the ZnClient instance, which will hold the state of the last request and response. > > Long answer: > > If you try > > | response | > response := ZnClient new > url:'http://stfx.eu/small.html'; > get; > response. > > response writeToTranscript. > > It will work and print > > HTTP/1.1 200 OK > X-Pad: avoid browser bug > Date: Mon, 29 Dec 2014 18:56:37 GMT > Content-Length: 113 > Etag: "202f9-71-4c7ae94364f1e" > Server: Apache/2.2.22 (Ubuntu) > Accept-Ranges: bytes > Last-Modified: Mon, 20 Aug 2012 08:48:51 GMT > Vary: Accept-Encoding > Content-Type: text/html > > <html> > <head><title>Small</title></head> > <body><h1>Small</h1><p>This is a small HTML document</p></body> > </html> > > So what is the difference ? > > The fact that the responses that you get from the website you mention are using chunked transfer encoding (http://en.wikipedia.org/wiki/Chunked_transfer_encoding) Zinc deals with this in both ways, while reading a response, but also while writing a response (which is what you are trying to do here). > > Here is how you disable chunked transfer encoding so that you can write the response to the Transcript > > | response | > response := ZnClient new > url:'http://amazon.com'; > get; > response. > > response headers removeKey: 'Transfer-Encoding'. > response writeToTranscript. > > Zinc manages to write to the Transcript in most cases by cheating a bit: it wraps a ZnBivalentWriteStream around another stream when needed - such a stream can do both binary and character writing at the same time (though the result is only good for quick and dirty debugging, since it is not 100% correct). I forgot to add that in the case of chunked transfer encoding, the bivalent property of the output stream gets lost because it gets wrapped in both a ZnChunkedWriteStream and a ZnBufferedWriteStream. > I hope the long explanation didn't make it worse ;-) > > HTH, > > Sven > > PS: BTW, in Pharo 4 with Zinc #bleedingEdge you get even nicer and more high level presentations of Zinc objects in GT-Inspector ! >

Dec. 29, 2014