April 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Idea icon pack now in Configuration Browser

by Cyril Ferlicot

Thank you Esteban :) On 30 April 2015 at 12:37, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > The Gofer stanza works. > > But > > Then DNU IdeaUIThermeIcons>>icons > > glamorousRight > ^ self icons > at: #'glamorousRight' > ifAbsentPut:[ Form fromBinaryStream: (Base64MimeConverter mimeDecodeToBytes: > self glamorousRightIconContents readStream) ]. > > ?? > > Pharo3.0 > Latest update: #30864 > > Phil > > > On Thu, Apr 30, 2015 at 12:20 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: >> >> sorry, answered to fastâ¦ it was: >> >> the same >> you can execute same scriptâ¦ it is proved to work on Pharo 3 without >> problems (the other Esteban tested it :P) >> >> Esteban >> >> >> > On 30 Apr 2015, at 12:19, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> > >> > the same >> > >> >> On 30 Apr 2015, at 12:18, phil(a)highoctane.be wrote: >> >> >> >> Wow >> >> >> >> Nice. >> >> >> >> Any way to load that in a 3.0? >> >> >> >> Phil >> > >> >> > > -- Cheers Cyril Ferlicot

April 30, 2015

Re: [Pharo-dev] Differences between TextConverters and ZnEncoders

by Sven Van Caekenberghe

> On 30 Apr 2015, at 11:59, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > I'd like to summarize some things > > + 1 to all that sven said. > > Taking a look at users of old text converters, there are only 77 of them: > > (TextConverter withAllSubclasses gather: [ :each | > SystemNavigation new allReferencesTo: each binding ]) size > " => 77" > > That is maybe a good starting point. And it will step by step remove the leading char magic. > > The only point where I see a problem is in the feature "convert magically cr's to some line ending convention" that is managed by a mixture between the text converter and the file stream. I would not like to push this "feature" to the zinc encoders. Actually I don't believe it belongs to the file reading neither. That are the things I am talking about, the old code mixed things up way too much. The main API problem is a key one: the old converters work String <-> String, the new ones String <-> ByteArray (or streams of course). Also does anyone dare to touch MultiByteFileStream or MultiByteBinaryOrTextStream (the names alone ;-) ? > Guille > > El jue., 30 de abr. de 2015 a la(s) 11:46 a. m., Norbert Hartl <norbert(a)hartl.name> escribiÃ³: > If yours is better there shouldn't be much of a reason to keep the bad one, right? I'd just suggest that pharo does not depend on zinc classes but the encoder moves to pharo with a different name. > > Norbert > > > Am 30.04.2015 um 11:42 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > > > > >> On 30 Apr 2015, at 11:13, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > >> > >> Hi! > >> > >> I'm struggling with the TextConverter's API in Pharo :). > >> > >> I wanted to test the converters in Pharo, and I found the method #convertFromSystemString: that should (from its name) convert a Pharo String into an encoded version of it. > >> > >> (UTF8TextConverter default convertFromSystemString: 'Ã¡'). > >> > >> Funny thing, it does not do that. It does the opposite: it tries to convert an encoded string to a pharo string. And so it fails. Of course, its symmetrical version does what I want and behaves as the ZnUTF8Encoder :) > >> > >> (UTF8TextConverter default convertToSystemString: 'Ã¡') asByteArray > >> "#[195 161]" > >> > >> ZnUTF8Encoder new encodeString: 'Ã¡' "#[195 161]" > >> > >> Question: > >> - does the convertTo/From methods makes sense to you or It's just me that sees them inverted? > >> - does it make sense to have the two versions of converters? Zn and the TextConverters do the same in my opinion (or maybe I'm confused :) ) > >> > >> Guille > > > > I am biased, but the Zn converters are better. Why ? Because they work between String <-> Bytes as a text encoder/decoder should. They also have a number of extra features (counting the number of encoded bytes, being able to move backwards on input, being able to be very strict), are faster and have a clearer implementation. Furthermore, they are more correct and implement more encodings. > > > > There is also good documentation http://stfx.eu/EnterprisePharo/Zinc-Encoding-Meta/ > > > > ZnCharacter[Read|Write]Stream are also very instructive, compare them to MultiByteStream. > > > > Should we throw the other one out ? Probably. But it is the same problems as with Xtreams: the API is different and adding a compatibility layer would defeat the purpose. So I don't know. > > > > Sven > > > > > > > >

April 30, 2015

Re: [Pharo-dev] [ANN] Idea icon pack now in Configuration Browser

by phil＠highoctane.be

The Gofer stanza works. But Then DNU IdeaUIThermeIcons>>icons glamorousRight ^ self icons at: #'glamorousRight' ifAbsentPut:[ Form fromBinaryStream: (Base64MimeConverter mimeDecodeToBytes: self glamorousRightIconContents readStream) ]. ?? Pharo3.0 Latest update: #30864 Phil On Thu, Apr 30, 2015 at 12:20 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > sorry, answered to fastâ¦ it was: > > the same > you can execute same scriptâ¦ it is proved to work on Pharo 3 without > problems (the other Esteban tested it :P) > > Esteban > > > > On 30 Apr 2015, at 12:19, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > the same > > > >> On 30 Apr 2015, at 12:18, phil(a)highoctane.be wrote: > >> > >> Wowâ > >> > >> Nice. > >> > >> Any way to load that in a 3.0? > >> > >> Phil > > > > >

April 30, 2015

Re: [Pharo-dev] [Pharo-users] [ANN] Idea icon pack now in Configuration Browser

by Norbert Hartl

What an improvement. Thanks! Norbert > Am 30.04.2015 um 12:11 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > Hi, > > I made a configuration to install the new Idea Icon Pack from configurations browser for Pharo 4. > You can install it and then choose your new icon set in settings. > > You can also manual install them by: > > Gofer it > smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo40'; > configurationOf: 'IdeaIcons'; > loadStable. > > ThemeIcons current: #IdeaUIThemeIcons asClass new. > âIn Pharo 4, you might need to execute thisâ > AbstractNautilusUI resetIconCaches. > > This icon pack works also for Pharo 3 > > If you lost it, here a couple of screenshots: > > <Screen Shot 2015-04-30 at 12.01.20.png> > > <Screen Shot 2015-04-30 at 12.01.57.png>

April 30, 2015

Re: [Pharo-dev] Tx: Bold Text

by Sean P. DeNigris

Nicolas Cellier wrote > shouldn't the API be more straight like: > emphasis: aTextEmphasis +1. We have nice emphasis objects, and then undermine them by spreading their state around! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Tx-Bold-Text-tp4822964p4823146.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 30, 2015

Re: [Pharo-dev] [ANN] Idea icon pack now in Configuration Browser

by Esteban Lorenzano

sorry, answered to fastâ¦ it was: the same you can execute same scriptâ¦ it is proved to work on Pharo 3 without problems (the other Esteban tested it :P) Esteban > On 30 Apr 2015, at 12:19, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > the same > >> On 30 Apr 2015, at 12:18, phil(a)highoctane.be wrote: >> >> Wowâ >> >> Nice. >> >> Any way to load that in a 3.0? >> >> Phil >

April 30, 2015

Re: [Pharo-dev] [ANN] Idea icon pack now in Configuration Browser

by Esteban Lorenzano

the same > On 30 Apr 2015, at 12:18, phil(a)highoctane.be wrote: > > Wowâ > > Nice. > > Any way to load that in a 3.0? > > Phil

April 30, 2015

Re: [Pharo-dev] [ANN] Idea icon pack now in Configuration Browser

by phil＠highoctane.be

Wowâ Nice. Any way to load that in a 3.0? Phil

April 30, 2015

[ANN] Idea icon pack now in Configuration Browser

by Esteban Lorenzano

Hi, I made a configuration to install the new Idea Icon Pack from configurations browser for Pharo 4. You can install it and then choose your new icon set in settings. You can also manual install them by: Gofer it smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo40'; configurationOf: 'IdeaIcons'; loadStable. ThemeIcons current: #IdeaUIThemeIcons asClass new. âIn Pharo 4, you might need to execute thisâ AbstractNautilusUI resetIconCaches. This icon pack works also for Pharo 3 If you lost it, here a couple of screenshots:

April 30, 2015

Re: [Pharo-dev] Differences between TextConverters and ZnEncoders

by Guillermo Polito

I'd like to summarize some things + 1 to all that sven said. Taking a look at users of old text converters, there are only 77 of them: (TextConverter withAllSubclasses gather: [ :each | SystemNavigation new allReferencesTo: each binding ]) size " => 77" That is maybe a good starting point. And it will step by step remove the leading char magic. The only point where I see a problem is in the feature "convert magically cr's to some line ending convention" that is managed by a mixture between the text converter and the file stream. I would not like to push this "feature" to the zinc encoders. Actually I don't believe it belongs to the file reading neither. Guille El jue., 30 de abr. de 2015 a la(s) 11:46 a. m., Norbert Hartl < norbert(a)hartl.name> escribiÃ³: > If yours is better there shouldn't be much of a reason to keep the bad > one, right? I'd just suggest that pharo does not depend on zinc classes but > the encoder moves to pharo with a different name. > > Norbert > > > Am 30.04.2015 um 11:42 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > > > > >> On 30 Apr 2015, at 11:13, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > >> > >> Hi! > >> > >> I'm struggling with the TextConverter's API in Pharo :). > >> > >> I wanted to test the converters in Pharo, and I found the method > #convertFromSystemString: that should (from its name) convert a Pharo > String into an encoded version of it. > >> > >> (UTF8TextConverter default convertFromSystemString: 'Ã¡'). > >> > >> Funny thing, it does not do that. It does the opposite: it tries to > convert an encoded string to a pharo string. And so it fails. Of course, > its symmetrical version does what I want and behaves as the ZnUTF8Encoder :) > >> > >> (UTF8TextConverter default convertToSystemString: 'Ã¡') asByteArray > >> "#[195 161]" > >> > >> ZnUTF8Encoder new encodeString: 'Ã¡' "#[195 161]" > >> > >> Question: > >> - does the convertTo/From methods makes sense to you or It's just me > that sees them inverted? > >> - does it make sense to have the two versions of converters? Zn and the > TextConverters do the same in my opinion (or maybe I'm confused :) ) > >> > >> Guille > > > > I am biased, but the Zn converters are better. Why ? Because they work > between String <-> Bytes as a text encoder/decoder should. They also have a > number of extra features (counting the number of encoded bytes, being able > to move backwards on input, being able to be very strict), are faster and > have a clearer implementation. Furthermore, they are more correct and > implement more encodings. > > > > There is also good documentation > http://stfx.eu/EnterprisePharo/Zinc-Encoding-Meta/ > > > > ZnCharacter[Read|Write]Stream are also very instructive, compare them to > MultiByteStream. > > > > Should we throw the other one out ? Probably. But it is the same > problems as with Xtreams: the API is different and adding a compatibility > layer would defeat the purpose. So I don't know. > > > > Sven > > > > > > > > >

April 30, 2015