March 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] About handling strings in streams with STON

by Sven Van Caekenberghe

So I guess that you want a Smalltalk expression that, when evaluated, returns an arbitrary STON-ified object as a real object. Let's say you want to STON-ify the following object: { #firstName->'StÃ©phane'. #lastName->'Ducasse'. #note->'Look: '', that was a single quote.' } asDictionary. Note there is a single quote character inside the #note. You can do that using #print: when needed. Here is an expression to see how that works: Compiler evaluate: (String streamContents: [ :out | out nextPutAll: 'STON fromString: '; print: (STON toString: ({ #firstName->'StÃ©phane'. #lastName->'Ducasse'. #note->'Look: '', that was a single quote.' } asDictionary)) ]). The Smalltalk expression then looks like this: STON fromString: '{#note:''Look: \'', that was a single quote.'',#firstName:''StÃ©phane'',#lastName:''Ducasse''}' The double single quotes are Smalltalk's syntax's escaping, while the backslashes are STON's. Yes, that is a bit confusing, but consistent. Is this what you need ? > On 12 Mar 2018, at 22:43, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi > > I want to write a method that generate a method that when I execute > this recreates the objects that I STONified. > (I love STON). > > So I did something like that > > descriptionMethodFrom: descriptionItems > "self new descriptionMethodFrom: ChrysalConfigurationDescription > itemDescriptionForXX" > > ^ String streamContents: [ :s | > s nextPutAll: 'descriptions'; cr. > s nextPutAll: '^ STON fromString: '. > s nextPutAll: (STON toStringPretty: descriptionItems) ] > > and I get of course something wrong :) because the strings are not > doubel quoted and the first expression is not surrounded by single > quote. > > And I could do it but I want a smart way to do it. I was thinking that > may be I'm missing something obvious. > > descriptions > ^ STON fromString: [ > StringConfigurationItem { > #propertyName : 'title', > #default : 'my super cool book' > }, > BooleanConfigurationItem { > #propertyName : 'verbose', > #default : 'true' > }, > StringConfigurationItem { > #propertyName : 'attribution', > #default : 'me, myself and I' > }, > StringConfigurationItem { > #propertyName : 'series', > #default : 'Square Bracket Associate Collection' > } > ] >

March 12, 2018

About handling strings in streams with STON

by Stephane Ducasse

Hi I want to write a method that generate a method that when I execute this recreates the objects that I STONified. (I love STON). So I did something like that descriptionMethodFrom: descriptionItems "self new descriptionMethodFrom: ChrysalConfigurationDescription itemDescriptionForXX" ^ String streamContents: [ :s | s nextPutAll: 'descriptions'; cr. s nextPutAll: '^ STON fromString: '. s nextPutAll: (STON toStringPretty: descriptionItems) ] and I get of course something wrong :) because the strings are not doubel quoted and the first expression is not surrounded by single quote. And I could do it but I want a smart way to do it. I was thinking that may be I'm missing something obvious. descriptions ^ STON fromString: [ StringConfigurationItem { #propertyName : 'title', #default : 'my super cool book' }, BooleanConfigurationItem { #propertyName : 'verbose', #default : 'true' }, StringConfigurationItem { #propertyName : 'attribution', #default : 'me, myself and I' }, StringConfigurationItem { #propertyName : 'series', #default : 'Square Bracket Associate Collection' } ]

March 12, 2018

Re: [Pharo-users] Ever growing image

by Hilaire

Le 12/03/2018 Ã 10:16, Guillermo Polito a Ã©critÂ : > That said, I would also like to have a smaller and more malleable > system, in that I agree with you, but that takes time and work, and I > see few people that is diving in the insides of Pharo to help get us > something in that direction. Not because they don't care but because > it is difficult and time consuming. Which direction should I follow after building a boostrap image following these instructions https://github.com/pharo-project/pharo#bootstrapping-pharo-from-sources ? -- Dr. Geo http://drgeo.eu

March 12, 2018

Re: [Pharo-users] How do I ask the FileSystem to resolve a relative path?

by Alistair Grant

Hi Sven, On 12 March 2018 at 19:38, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi Alistair, > >> On 12 Mar 2018, at 19:06, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> On 12 March 2018 at 10:03, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >>> >>> Hi, >>> >>> do not forget also that there is an entire chapter on FileSystem in here: >>> >>> http://files.pharo.org/books-pdfs/deep-into-pharo/2013-DeepIntoPharo-EN.pdf >>> >>> And I particularly recommend everybody dealing with files to read about how to manage encodings in here: >>> >>> http://files.pharo.org/books-pdfs/entreprise-pharo/2016-10-06-EnterprisePha… >> >> >> Cool! I wasn't aware of the section on character encoding, it's >> probably the best introduction to character encoding I've read. > > Thanks. > >> There is one important mistake in the examples. On page 46 it gives >> the following code: >> >> 'encoding-test.txt' asFileReference writeStreamDo: [ :out | >> (ZnCharacterWriteStream on: out binary encoding: #utf8) >> nextPutAll: 'Hello'; space; nextPutAll: 'ÎÎ»Î»Î¬Î´Î±'; crlf; >> nextPutAll: 'Les Ã©lÃ¨ves franÃ§ais'; crlf ]. >> >> >> This won't work reliably as #writeStreamDo: (and #readStreamDo:) use >> MultiByteFileStreams, which are not binary by default. > > It does work, you missed the #binary message sent to out. You're right, of course. My apologies (I did miss the #binary). Cheers, Alistair >> It really should be (in Pharo 7, I haven't checked pharo 6) >> #binaryWriteStreamDo: and #binaryReadStreamDo:, i.e.: >> >> 'encoding-test.txt' asFileReference binaryWriteStreamDo: [ :out | >> (ZnCharacterWriteStream on: out binary encoding: #utf8) >> nextPutAll: 'Hello'; space; nextPutAll: 'ÎÎ»Î»Î¬Î´Î±'; crlf; >> nextPutAll: 'Les Ã©lÃ¨ves franÃ§ais'; crlf ]. > > This is indeed better (but I am not sure #binaryWriteStreamDo: was available in the past). In this case, the #binary message sent to out should be dropped. > > Sven > >> Cheers, >> Alistair >> >> (I know I should submit a PR for this, but I'm suffering a personal >> interrupt stack overflow at the moment)

March 12, 2018

Re: [Pharo-users] How do I ask the FileSystem to resolve a relative path?

by Sven Van Caekenberghe

Hi Alistair, > On 12 Mar 2018, at 19:06, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > On 12 March 2018 at 10:03, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> >> Hi, >> >> do not forget also that there is an entire chapter on FileSystem in here: >> >> http://files.pharo.org/books-pdfs/deep-into-pharo/2013-DeepIntoPharo-EN.pdf >> >> And I particularly recommend everybody dealing with files to read about how to manage encodings in here: >> >> http://files.pharo.org/books-pdfs/entreprise-pharo/2016-10-06-EnterprisePha… > > > Cool! I wasn't aware of the section on character encoding, it's > probably the best introduction to character encoding I've read. Thanks. > There is one important mistake in the examples. On page 46 it gives > the following code: > > 'encoding-test.txt' asFileReference writeStreamDo: [ :out | > (ZnCharacterWriteStream on: out binary encoding: #utf8) > nextPutAll: 'Hello'; space; nextPutAll: 'ÎÎ»Î»Î¬Î´Î±'; crlf; > nextPutAll: 'Les Ã©lÃ¨ves franÃ§ais'; crlf ]. > > > This won't work reliably as #writeStreamDo: (and #readStreamDo:) use > MultiByteFileStreams, which are not binary by default. It does work, you missed the #binary message sent to out. > It really should be (in Pharo 7, I haven't checked pharo 6) > #binaryWriteStreamDo: and #binaryReadStreamDo:, i.e.: > > 'encoding-test.txt' asFileReference binaryWriteStreamDo: [ :out | > (ZnCharacterWriteStream on: out binary encoding: #utf8) > nextPutAll: 'Hello'; space; nextPutAll: 'ÎÎ»Î»Î¬Î´Î±'; crlf; > nextPutAll: 'Les Ã©lÃ¨ves franÃ§ais'; crlf ]. This is indeed better (but I am not sure #binaryWriteStreamDo: was available in the past). In this case, the #binary message sent to out should be dropped. Sven > Cheers, > Alistair > > (I know I should submit a PR for this, but I'm suffering a personal > interrupt stack overflow at the moment)

March 12, 2018

Re: [Pharo-users] How do I ask the FileSystem to resolve a relative path?

by Alistair Grant

On 12 March 2018 at 10:03, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi, > > do not forget also that there is an entire chapter on FileSystem in here: > > http://files.pharo.org/books-pdfs/deep-into-pharo/2013-DeepIntoPharo-EN.pdf > > And I particularly recommend everybody dealing with files to read about how to manage encodings in here: > > http://files.pharo.org/books-pdfs/entreprise-pharo/2016-10-06-EnterprisePha… Cool! I wasn't aware of the section on character encoding, it's probably the best introduction to character encoding I've read. There is one important mistake in the examples. On page 46 it gives the following code: 'encoding-test.txt' asFileReference writeStreamDo: [ :out | (ZnCharacterWriteStream on: out binary encoding: #utf8) nextPutAll: 'Hello'; space; nextPutAll: 'ÎÎ»Î»Î¬Î´Î±'; crlf; nextPutAll: 'Les Ã©lÃ¨ves franÃ§ais'; crlf ]. This won't work reliably as #writeStreamDo: (and #readStreamDo:) use MultiByteFileStreams, which are not binary by default. It really should be (in Pharo 7, I haven't checked pharo 6) #binaryWriteStreamDo: and #binaryReadStreamDo:, i.e.: 'encoding-test.txt' asFileReference binaryWriteStreamDo: [ :out | (ZnCharacterWriteStream on: out binary encoding: #utf8) nextPutAll: 'Hello'; space; nextPutAll: 'ÎÎ»Î»Î¬Î´Î±'; crlf; nextPutAll: 'Les Ã©lÃ¨ves franÃ§ais'; crlf ]. Cheers, Alistair (I know I should submit a PR for this, but I'm suffering a personal interrupt stack overflow at the moment)

March 12, 2018

Re: [Pharo-users] feenk log

by Alistair Grant

On 11 March 2018 at 21:01, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Here is an update of the work on Bloc, Brick and GT. As always, please do let us know what you think. > > [snip/] > > - Andrei put together a beautiful description of a scenario in which an application is molded interactively in the Playground & Inspector. The subject is face recognition, and the resulting code is both functional and explainable. This is intended as a tutorial material that shows what moldable development means and how it changes the way we program: > https://twitter.com/feenkcom/status/972907051448979458 The GToolkit has certainly influenced how I program - and this is a great article that lays it out quite clearly. If I'm developing a new application the first few iterations of the UI are pretty much always extensions to the inspector. I also enjoyed Tudor's interview on No Fluff Just Stuff which discusses a real world use of this: - Podcast audio: https://player.fm/series/no-fluff-just-stuff/changing-the-way-we-code-w-tud… - No Fluff Just Stuff: https://nofluffjuststuff.com/home/main Thanks! Alistair

March 12, 2018

Re: [Pharo-users] [system update problem]

by H. Hirzel

On 3/12/18, Baveco, Hans <hans.baveco(a)wur.nl> wrote: > Hi, > I consistently have problems doing the software update, under the System > item in the World menu. > Get stuck in "Fetching BaselineOfIceberg", when according to the debugger a > ZnClient is trying to connect to url > "https://github.com:443/pharo-vcs/iceberg/zipball/v0.6.8" > > > It says this a Pharo 6.0 image, latest update: #60529 (though I am fairly > sure it was actually a downloaded 6.1 image I started from) As for the Pharo 6.0 label for a Pharo 6.1 image. This is a known issue. The Pharo 6.1 release did not update the version label.... > Any suggestions how to solve this? > Thanks! > Hans > > >

March 12, 2018

[system update problem]

by Baveco, Hans

Hi, I consistently have problems doing the software update, under the System item in the World menu. Get stuck in "Fetching BaselineOfIceberg", when according to the debugger a ZnClient is trying to connect to url "https://github.com:443/pharo-vcs/iceberg/zipball/v0.6.8" It says this a Pharo 6.0 image, latest update: #60529 (though I am fairly sure it was actually a downloaded 6.1 image I started from) Any suggestions how to solve this? Thanks! Hans

March 12, 2018

Re: [Pharo-users] Please rejoin Discord

by Esteban Lorenzano

> On 12 Mar 2018, at 10:43, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Maybe it would be better to flip it around: > > have http://pharo.org/discord <http://pharo.org/discord> which would automatically redirect to the proper pharo invite link maybe better http://pharo.org/joindiscord <http://pharo.org/joindiscord> because otherwise it gives the idea the client and not the link? Esteban > > On Sun, Mar 11, 2018 at 9:25 PM, Dimitris Chloupis <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: > Because I posted a new link it was misinterpreted that the old one did not work which is not the case. Yeah changing it back to the old one is the right choice. I created the new one only for convenience but as I said we already have a ton of invite links. > > In any case the old one will remain and wont bet changed, unless Dicscord decides something stupid which I doubt will do because already too many people (outside our community) that use Discord depend on the invite links not to change and remain the same. > > So all is good :) > > > On Sun, Mar 11, 2018 at 9:43 PM Stephane Ducasse <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> wrote: > Ok now I do not understand why the invite changed on the pharo web > site (and I do not like the here instead of the full name) because we > have to hover to get the information. > > On Sun, Mar 11, 2018 at 7:30 PM, Dimitris Chloupis > <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: > > if you provide me the specific link of the invitation you are referring to, > > I can verify it for you that has not changed > > > > Our server currently has 26 invites with no expiration date. 2 of them are > > created by me. > > > > But yes if an invite is without expiration date it means it won't get > > deleted. > > > > The most likely scenario is that you are using an invite created by Esteban > > (@Estebanlm), because it has been used 871 times. That invite has not > > changed and is the invite ending with "Sj2rhxn" and indeed it has no > > expiration date, which means it will "never" change. Neither any other of > > the 26 invites. > > > > > > > > > > On Sun, Mar 11, 2018 at 8:07 PM Stephane Ducasse <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> > > wrote: > >> > >> did the invitation changed? > >> Because we will have to update books flyers and others. > >> So is there a way to keep the invitation link stable? > >> > >> Stef > >> > >> On Sat, Mar 10, 2018 at 11:48 AM, Dimitris Chloupis > >> <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: > >> > Hey guys after my mistake we got "hacked" and someone banned all our > >> > members > >> > in Discord > >> > > >> > I have revoked all the bans but you will have to rejoin . Existing join > >> > links are still valid , if you dont have one here is one > >> > > >> > https://discord.gg/gtKeHne <https://discord.gg/gtKeHne> > >> > > >> > My apologies for this inconvenience, I am still exploring all possible > >> > threats to make sure this never happens again. > >> > > > >

March 12, 2018