- Pharo-users - lists.pharo.org

Re: [Pharo-users] About encoding

by Stephane Ducasse

Now inspecting the file containent opens gtinspector and freezes Pharo :( I think that I will remove this part of my book. It is simpler. On Tue, Sep 26, 2017 at 5:53 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > I'm reading your chapter :) > Now I understand the file I found is totally bogus :) > But the first one I found is indeed encoded in latin1. > So I'm trying to convert it. > > > > > On Tue, Sep 26, 2017 at 5:40 PM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: >>> Any chance you can point me to the original file ? >> >> No they removed it >> May be I could try to convert it to utf-8 (I do not know how to do it) >> >>> The file is indeed in Latin1 encoded, but GitHub serves it as UTF-8 (it did not change the contents, but the meta data). >> >> Ok I see the problem >>> >>> The default encoder option only works when the server says nothing, it does not override what the server says. >> >> Ah ok. >> >>> The only way to read it, is by reading it binary (which basically ignores the meta data) and then convert it manually: >>> >>> (ZnCharacterEncoder latin1 decodeBytes: >>> (ZnClient new >>> beBinary; >>> get: 'https://raw.githubusercontent.com/SquareBracketAssociates/LearningOOPWithPh…')) lines. >>> >>> But this is very ugly. >>> >>> Best convert the original file to UTF-8 before uploading to GitHub. >> >> OK I will try to leanr how to do it. >> >> >>> >>> Sven >>> >>> >>>

Sept. 26, 2017

Re: [Pharo-users] Force headless mode

by Esteban Lorenzano

> On 26 Sep 2017, at 16:49, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > Hi, > > At Synectique we are working on the deployment of a web application > and we would like to force the headless mode. We tried to just > override the method SmalltalkImage>>#isHeadless to return true all the > time be it is not enough because the image is still opened. It is > probabaly the vm that open the window. > > I know we can add some arguments to the command line to open the image > as headless but we want to forbid the user to launch the image without > headless to protect the code. > > Is this possible? Do you have some pointers? it is not. specially on windows. vm handles the creation of host window and you will always have one. nowâ¦ if you wait one week, I will have ready the (experimental) real headless VMs. In my tests, they are working fine but we will still need to work when we want to actually start a world windowâ¦ but thatâs another story ;) Esteban > > Thanks in advance. > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France >

Sept. 26, 2017

Re: [Pharo-users] About encoding

by Stephane Ducasse

I'm reading your chapter :) Now I understand the file I found is totally bogus :) But the first one I found is indeed encoded in latin1. So I'm trying to convert it. On Tue, Sep 26, 2017 at 5:40 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> Any chance you can point me to the original file ? > > No they removed it > May be I could try to convert it to utf-8 (I do not know how to do it) > >> The file is indeed in Latin1 encoded, but GitHub serves it as UTF-8 (it did not change the contents, but the meta data). > > Ok I see the problem >> >> The default encoder option only works when the server says nothing, it does not override what the server says. > > Ah ok. > >> The only way to read it, is by reading it binary (which basically ignores the meta data) and then convert it manually: >> >> (ZnCharacterEncoder latin1 decodeBytes: >> (ZnClient new >> beBinary; >> get: 'https://raw.githubusercontent.com/SquareBracketAssociates/LearningOOPWithPh…')) lines. >> >> But this is very ugly. >> >> Best convert the original file to UTF-8 before uploading to GitHub. > > OK I will try to leanr how to do it. > > >> >> Sven >> >> >>

Sept. 26, 2017

Re: [Pharo-users] Force headless mode

by Cyril Ferlicot

On Tue, Sep 26, 2017 at 5:13 PM, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > Hi > > What about deploying a minimal image without UI ? > But, as you probably know, headless mode does not prevent to dump the code. > I just tried to build our tools on a minimal image but it crash when trying to load a github's project. I now added a piece of code to update Metacello to a newer version but it just do nothing without any log. I know there is still some way to get the code but this is the first step to build a real delivery image. > Christophe > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Sept. 26, 2017

Re: [Pharo-users] About encoding

by Sven Van Caekenberghe

You can convert it in Pharo, of course: (FileLocator desktop / 'mots.txt') writeStreamDo: [ :out | out << (ZnCharacterEncoder latin1 decodeBytes: (ZnClient new beBinary; get: 'https://raw.githubusercontent.com/SquareBracketAssociates/LearningOOPWithPh…')) ]. You just take the string as it is in Pharo and write it out to a file, it is by default utf-8 encoded. > On 26 Sep 2017, at 17:40, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > >> Any chance you can point me to the original file ? > > No they removed it > May be I could try to convert it to utf-8 (I do not know how to do it) > >> The file is indeed in Latin1 encoded, but GitHub serves it as UTF-8 (it did not change the contents, but the meta data). > > Ok I see the problem >> >> The default encoder option only works when the server says nothing, it does not override what the server says. > > Ah ok. > >> The only way to read it, is by reading it binary (which basically ignores the meta data) and then convert it manually: >> >> (ZnCharacterEncoder latin1 decodeBytes: >> (ZnClient new >> beBinary; >> get: 'https://raw.githubusercontent.com/SquareBracketAssociates/LearningOOPWithPh…')) lines. >> >> But this is very ugly. >> >> Best convert the original file to UTF-8 before uploading to GitHub. > > OK I will try to leanr how to do it. > > >> >> Sven >> >> >> >

Sept. 26, 2017

Re: [Pharo-users] About encoding

by Stephane Ducasse

> Any chance you can point me to the original file ? No they removed it May be I could try to convert it to utf-8 (I do not know how to do it) > The file is indeed in Latin1 encoded, but GitHub serves it as UTF-8 (it did not change the contents, but the meta data). Ok I see the problem > > The default encoder option only works when the server says nothing, it does not override what the server says. Ah ok. > The only way to read it, is by reading it binary (which basically ignores the meta data) and then convert it manually: > > (ZnCharacterEncoder latin1 decodeBytes: > (ZnClient new > beBinary; > get: 'https://raw.githubusercontent.com/SquareBracketAssociates/LearningOOPWithPh…')) lines. > > But this is very ugly. > > Best convert the original file to UTF-8 before uploading to GitHub. OK I will try to leanr how to do it. > > Sven > > >

Sept. 26, 2017

Re: [Pharo-users] Usability issues with Calypso

by Stephane Ducasse

In fact I'm not sure that continuing to use the * is not a good idea. On Sun, Sep 24, 2017 at 2:46 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi Sean > > 2017-09-23 19:57 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: >> >> Stephane Ducasse-3 wrote >> > Calypso is still an enfant and this is >> > IMPORTANT that people tell what >> > they do not like so that we can improve. >> >> A few more impressions now that I've been using Calypso as my default >> browser: >> - Overall really enjoying it! >> - When browsing a class from its own package, and then adding an extension >> protocol via '*...' in "New protocol" context menu, the dialog closes >> without objection, but then the new protocol doesn't seem to exist. I had >> to >> create a dummy protocol and then DND the methods into the >> package-to-be-extended. > > > In Calypso you should not create protocols with star. In method editor > status bar there is explicit checkbox "extension" to specify external > package for the method. > We should move away from star convention and work directly with packages. > Calypso gives you the tools for this. > > But I will add special notification when user creates new protocol with > star. I think it will help "old" Pharo users to adopt. > https://github.com/dionisiydk/Calypso/issues/96 > >> >> - When Calypso is set to be the default browser, it would be helpful if >> the >> World menu item changed from "Calypso Browser" to "Nautilus" >> - Lack of word wrapping is becoming teeeeeeedious >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >

Sept. 26, 2017

Re: [Pharo-users] About encoding

by Sven Van Caekenberghe

> On 26 Sep 2017, at 17:25, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi sven > > the web site I was using remove the file for my book. > So I copied the file on github. > When I open the file with texmate it tells that the encoding is western-latin1 > but when I try to load it as follow I get an UTF-8 illegal error. > > | lines | > lines := (ZnDefaultCharacterEncoder > value: ZnCharacterEncoder latin1 > during: [ > ZnClient new > get: 'https://raw.githubusercontent.com/SquareBracketAssociates/LearningOOPWithPh…' > ]) lines. > > Do you have any idea? > > Tx > > Stef Any chance you can point me to the original file ? The file is indeed in Latin1 encoded, but GitHub serves it as UTF-8 (it did not change the contents, but the meta data). The default encoder option only works when the server says nothing, it does not override what the server says. The only way to read it, is by reading it binary (which basically ignores the meta data) and then convert it manually: (ZnCharacterEncoder latin1 decodeBytes: (ZnClient new beBinary; get: 'https://raw.githubusercontent.com/SquareBracketAssociates/LearningOOPWithPh…')) lines. But this is very ugly. Best convert the original file to UTF-8 before uploading to GitHub. Sven

Sept. 26, 2017

About encoding

by Stephane Ducasse

Hi sven the web site I was using remove the file for my book. So I copied the file on github. When I open the file with texmate it tells that the encoding is western-latin1 but when I try to load it as follow I get an UTF-8 illegal error. | lines | lines := (ZnDefaultCharacterEncoder value: ZnCharacterEncoder latin1 during: [ ZnClient new get: 'https://raw.githubusercontent.com/SquareBracketAssociates/LearningOOPWithPh…' ]) lines. Do you have any idea? Tx Stef

Sept. 26, 2017

Re: [Pharo-users] Force headless mode

by ClÃ©ment Bera

Or write a script that obfuscate the code. Not so hard to do. On Tue, Sep 26, 2017 at 5:13 PM, Christophe Demarey < christophe.demarey(a)inria.fr> wrote: > Hi > > What about deploying a minimal image without UI ? > But, as you probably know, headless mode does not prevent to dump the code. > > Christophe > ----- Cyril Ferlicot <cyril.ferlicot(a)gmail.com> a Ã©crit : > > Hi, > > > > At Synectique we are working on the deployment of a web application > > and we would like to force the headless mode. We tried to just > > override the method SmalltalkImage>>#isHeadless to return true all the > > time be it is not enough because the image is still opened. It is > > probabaly the vm that open the window. > > > > I know we can add some arguments to the command line to open the image > > as headless but we want to forbid the user to launch the image without > > headless to protect the code. > > > > Is this possible? Do you have some pointers? > > > > Thanks in advance. > > > > -- > > Cyril Ferlicot > > https://ferlicot.fr > > > > http://www.synectique.eu > > 2 rue Jacques PrÃ©vert 01, > > 59650 Villeneuve d'ascq France > > > > >

Sept. 26, 2017