April 2014 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [Pharo-dev] Pharo Consortium: New Gold Member Lam Research

by Tudor Girba

Great! Doru -- www.tudorgirba.com "Every thing has its own flow." > On 09.04.2014, at 11:38, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > The Pharo Consortium is very happy to announce that Lam Research has joined the Consortium as a Gold Industrial Member. > > More about > - Lam Research: http://lamrc.com > - Pharo Consortium: http://consortium.pharo.org > > > The goal of the Pharo Consortium is to allow companies to support the ongoing development and future of Pharo. > > Individuals can support Pharo via the Pharo Association: http://association.pharo.org

April 10, 2014

Re: [Pharo-users] Zinc HTTP server seems to convert always ...

by Paul DeBruicker

+1 to Sven's comment and Marten - you should post this on the GemStone list as one of their guys will be able to help you with the encoding issues. Paul Sven Van Caekenberghe-2 wrote > On 09 Apr 2014, at 20:54, > itlists@ > wrote: > >> And now the additional information: I'm working under Gemstone and I >> noticed quite some differences between Pharo and its Gemstone port >> of Zinc in this area ... I have to take a closer look here. >> >> Marten > > I already expected that much. Yes, Zinc on Gemstone is seriously behind > the original. Furthermore, I have never seen or worked with it. And > although I have some sympathy for other Smalltalk implementations out > there, I find it difficult to give free support for an expensive, closed > source, commercial product. > > Sven -- View this message in context: http://forum.world.st/Zinc-HTTP-server-seems-to-convert-always-tp4753613p47… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 10, 2014

Re: [Pharo-users] NeoJSON Parsing Nested Objects

by Esteban A. Maringolo

It's basic but it works. :) THanks sean! Esteban A. Maringolo 2014-04-09 18:07 GMT-03:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Esteban A. Maringolo wrote >>>> I'm wrapping the Digital Ocean API. >>> Cool ! >> +1 > > The embryo is alive. See documentation at > http://smalltalkhub.com/#!/~SeanDeNigris/DigitalOcean > > A few supported operations: > DoDroplet allActive. > DoDroplet allActive detect: [ :e | e name = 'mycooldomain.org' ]. > DoDropletSize all. > DoDropletSize named: '512MB' > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/NeoJSON-Parsing-Nested-Objects-tp4753695p4753749.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

April 9, 2014

Re: [Pharo-users] NeoJSON Parsing Nested Objects

by Sean P. DeNigris

Esteban A. Maringolo wrote >>> I'm wrapping the Digital Ocean API. >> Cool ! > +1 The embryo is alive. See documentation at http://smalltalkhub.com/#!/~SeanDeNigris/DigitalOcean A few supported operations: DoDroplet allActive. DoDroplet allActive detect: [ :e | e name = 'mycooldomain.org' ]. DoDropletSize all. DoDropletSize named: '512MB' ----- Cheers, Sean -- View this message in context: http://forum.world.st/NeoJSON-Parsing-Nested-Objects-tp4753695p4753749.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 9, 2014

Re: [Pharo-users] Zinc HTTP server seems to convert always ...

by Sven Van Caekenberghe

On 09 Apr 2014, at 20:54, itlists(a)schrievkrom.de wrote: > And now the additional information: I'm working under Gemstone and I > noticed quite some differences between Pharo and its Gemstone port > of Zinc in this area ... I have to take a closer look here. > > Marten I already expected that much. Yes, Zinc on Gemstone is seriously behind the original. Furthermore, I have never seen or worked with it. And although I have some sympathy for other Smalltalk implementations out there, I find it difficult to give free support for an expensive, closed source, commercial product. Sven

April 9, 2014

Re: [Pharo-users] Zinc HTTP server seems to convert always ...

by itlists＠schrievkrom.de

And now the additional information: I'm working under Gemstone and I noticed quite some differences between Pharo and its Gemstone port of Zinc in this area ... I have to take a closer look here. Marten -- Marten Feldtmann

April 9, 2014

Re: [Pharo-users] NeoJSON Parsing Nested Objects

by Sven Van Caekenberghe

On 09 Apr 2014, at 19:28, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Sean P. DeNigris wrote >> I'd like to convert them to DropletSize objects > > Duh :-P > > reader for: DoResponse do: [ :m | > m mapInstVar: #status. > (m mapInstVar: #contents to: #sizes) valueSchema: #ArrayOfDropletSizes ]. BTW, I did some recent enhancements to NeoJSON mapping that could be interesting. http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Neo/commits like #nextPut:as:

April 9, 2014

Re: [Pharo-users] Zinc HTTP server seems to convert always ...

by Sven Van Caekenberghe

On 09 Apr 2014, at 19:35, itlists(a)schrievkrom.de wrote: > Ok, forget the JSON stuff - it has nothing to do with the "problem". > > Other way round: > > My whole database and internal processing is done in UTF8. This is the > most important point here to mention. Why ? This means you forgo almost all String functionality, since UTF8 is a variable length encoding not really suitable to character by character processing. > Now the request comes into Zinc as mentioned below (the content of the > request is a JSON string only): > > HTML-Request (charset=UTF-8) =(sends)=> ZINC HTTP > > Now Zinc sees the content of the body, knows that it is coded in UTF8 > and creates a ZnStringEntity with UTF8Encoder. > > Zinc HTTP =(builds)=> ZnStringEntity (with UTF8Encoder) > > The instance of ZnRequest and its entity value is an instance of > ZnStringEntity (with its encoder attribute is set to an instance to > ZnUTF8Encoder). Yes, of course, UTF-8 (a variable length binary encoding) is converted into native Pharo Strings (possibly WideStrings) containing Characters, each of which is encoded using a Unicode code point value. > I checked the content of the string attribute of the ZnStringEntity and > this string is NOT encoded in UTF8 any more, but in either ISO8859-? > or WIN1252. Here you lose me (again) ;-) > I think, that this is ok for almost all people, because they work with > some CodePages - but my internal processing assumes UTF8. No, nobody works with code pages or any encoding, just native [Wide]Strings in pure Unicode. > I just fixed this for me by changing ZnStringEntity>>initializeEncoder > to ALWAYS set the encoder attribute to ZnNullEncoder and now everthing > is ok again. This means of course, that all apllication running with > that source code work in UTF 8 only ... OK, I think I understand, you want UTF-8 to remain UTF-8. What you did is one solution, but I think it is wrong to use a String to represent bytes. This case is actually already implemented server side for Seaside: ZnZincServerAdaptor>>#configureServerForBinaryReading "Seaside wants to do its own text conversions" server reader: [ :stream | ZnRequest readBinaryFrom: stream ] The #reader: option is used here to read everything binary, without decoding to Strings. You will get ZnZnByteArrayEntity objects back, containing the original binary representation. BTW, I think this is an interesting discussion. Regards, Sven > Marten > > Am 09.04.2014 18:42, schrieb Sven Van Caekenberghe: >> Marten, >> >> On 09 Apr 2014, at 18:25, itlists(a)schrievkrom.de wrote: >> >>> Ok, if the browser sends POST/PUT request with a JSON structure it also >>> sends charset = utf8 (in my case). That's ok, because for JSON this is >>> more or less the default charset. >>> >>> Zinc now seems to notice, that UTF8 charset is needed and creates a >>> ZnStringEntity with an UTF8Encoder. >>> >>> Now when my application tries to get the JSON string of that >>> ZnStringEntity and builds the structure out of that string - and the >>> strings are NOT UTF8, but converted to (?) ISO8859 ? >> >> (NeoJSONReader fromString: >> (ZnEntity with: (NeoJSONWriter toString: { #message -> 'An der schÃ¶nen blauen Donau' } asDictionary))) >> at: #message. >> >> You must be doing something possibly wrong when you <<get the JSON string of that ZnStringEntity and builds the structure out of that string>> (how do you do that, BTW), so please write some code that demonstrates what is not right according to you. >> >> Sven >> > > > -- > Marten Feldtmann >

April 9, 2014

Re: [Pharo-users] NeoJSON Parsing Nested Objects

by Esteban A. Maringolo

2014-04-09 14:56 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > On 09 Apr 2014, at 19:18, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > >> I'm wrapping the Digital Ocean API. > > Cool ! +1 I use it for my Pharo hosting too (plus a JIRA instance on other droplet). Anybody using Supervisord or anything similar tool to "manage" pharo instances? Regards!

April 9, 2014

Re: [Pharo-users] NeoJSON Parsing Nested Objects

by Sven Van Caekenberghe

On 09 Apr 2014, at 19:18, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I'm wrapping the Digital Ocean API. Cool !

April 9, 2014