- Pharo-users - lists.pharo.org

Re: [Pharo-users] make a simple sample(for korean)

by peter yoo

@Ben of course. server side is PHP. client side is using Pharo. data format using JSON(NeoJSON). PHP code is receive JSON data using "post stream". and managing data with mysql(mariadb) thanks to your interesting. i want more usefull Pharo to my work. but my Main business is complex. maybe cannot now. and.. you interesting to korea then look this service. contents is free. can look. of course english. (it's my service. for forigner) and... can download from appstore(android and iOS) * http://www.lookandwalk.com/en/main/home after can then Pharo using for my service. but can not find use now. and.... im already "SMALLTALK-80/The Language and Its Implementation" draft translation to korean. but dont have time. cannot study now. * http://trans.onionmixer.net/mediawiki/index.php?title=Smalltalk80LanguageIm… after have a time then more deep study to Smalltalk. i wish. @Stephane of course. but multi lingual is perfect. Im using Korean Font in Pharo 5(alt 64bit) with 64bit linux. * NanumGothic(http://www.ffonts.net/NanumGothic.font) * NanumGothicCoding(https://github.com/naver/nanumfont/releases)-fixed type this font is Free. maybe Pharo Using XIM now(fcitx). input and look korean is very beautiful. dont worry. and "Really" Always thanks to Pharo developer. have a problem then report to community.

May 13, 2017

Re: [Pharo-users] PetitParser installation fails in Pharo 5.0

by Andreas Sunardi

Hi Stephane, Indeed, PetitParser installation from Catalog Browser works just fine! Thank you very much. I used Monticello Browser before, but not Catalog Browser. I didn't know this is the preferred method to install package. I don't think DeepIntoPharo mentions about Catalog Browser, but maybe my version is outdated. Thanks again, Stephane. -- Andreas Sunardi On Fri, May 12, 2017 at 12:48 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Sorry I meant the catalogBrowser. > Using the catalogBrowser on a given version of Pharo you should access the > configuration for this version (if people updated it correctly). > Our plan is to make sure that such configurations are validated. > Stef > > On Fri, May 12, 2017 at 9:47 PM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> Hi andreas >> >> Normally you should be able to load a package using the >> ConfigurationBrowser and the configuration (now I do not know the one of >> PetitParser) >> should take care of the pharo version for you. >> >> stef >> >> >> On Fri, May 12, 2017 at 7:06 PM, Andreas Sunardi <a.sunardi(a)gmail.com> >> wrote: >> >>> Following DeepIntoPharo, I tried to install PetitParser into my Pharo >>> 5.0 image (I noticed PetitParser installation problem email in March). It >>> failed with the message WinPlatform class was undefined. I went to Moose's >>> PetitParser site in smalltalkhub and followed the instruction there, and >>> this also failed. >>> >>> Out of frustration, I downloaded Moose 6.0 and thought I'd start from >>> Moose image instead. But then I noticed Moose's PetitParser package has >>> ConfigurationOfPetitParser from version TudorGirba.77 and the instruction I >>> followed was trying to install it using version TudorGirba.80. Back to my >>> Pharo 5 image, I unload/remove ConfigurationOfPetitParser and load version >>> TudorGirba.77. And this works! >>> >>> But this way to solve PetitParser installation problem seems wrong. I >>> figure if this could very well happen with other packages too. What is the >>> right way to find package version that works with my image/pharo version? >>> Or is this an issue with PetitParser package itself and should I ask/report >>> this to Moose team? >>> >>> -- >>> Andreas Sunardi >>> >> >> >

May 13, 2017

Re: [Pharo-users] Basic Iceberg First Commit

by Esteban Lorenzano

you used the incorrect linux version. you need the threaded one. wget -O- get.pharo.org/vmT60 <http://get.pharo.org/vmT60> | bash (I need to put that in the README) Esteban > On 12 May 2017, at 20:54, Evan Donahue <emdonahu(a)gmail.com> wrote: > > Hello, > > I am trying to get Iceberg working. I have a new Pharo 6 image as of about 5 minutes ago, and I am following the tutorial here: > > https://github.com/pharo-vcs/iceberg <https://github.com/pharo-vcs/iceberg> > > I get as far as cloning the repository, but when I enter my github ssh url and hit "Create repository" I get "LGit_GIT_ERROR: no error message set by libgit2." > > I am wondering three things: > 1) What are the dependencies, libgit or otherwise, that I should make sure to have on my system? I have everything mentioned at the top of teh tutorial. > 2) Is this tutorial still up to date enough that I should be getting past this step? I know the code is under development. > 3) Is there a way to see what actually gets sent to the ffi? Nothing in the call trace looks especially out of place. > > Thanks, > Evan

May 12, 2017

Re: [Pharo-users] make a simple sample(for korean)

by Stephane Ducasse

Hi peter in Pharo we have a problem, we do not have enough "non ascii speaking language" developer involved. we may break without even seeing it other languages. So if you see that we broke something let us know. Stef On Fri, May 12, 2017 at 4:10 PM, peter yoo <onionmixer(a)gmail.com> wrote: > this requirements. > > 1. nginx + php-fpm (another web env is ok. important is PHP) > 2. Pharo 5 > > http://workspace.onionmixer.net/mediawiki/index.php?title= > Pharo_Json_PHP_Example_01 > > > so.. me know now. but need "sample code" then can help to any newbie. > > always thank you to community. and... Pharo 64bit for linux is good for > korean. because input korea charactor is not have problem. all clear now. :D > > -- > http://lookandwalk.com http://looknw.com | http://onionmixer.net > peter yoo(Jonghwa Yoo). ROK >

May 12, 2017

Re: [Pharo-users] PetitParser installation fails in Pharo 5.0

by Stephane Ducasse

Sorry I meant the catalogBrowser. Using the catalogBrowser on a given version of Pharo you should access the configuration for this version (if people updated it correctly). Our plan is to make sure that such configurations are validated. Stef On Fri, May 12, 2017 at 9:47 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi andreas > > Normally you should be able to load a package using the > ConfigurationBrowser and the configuration (now I do not know the one of > PetitParser) > should take care of the pharo version for you. > > stef > > > On Fri, May 12, 2017 at 7:06 PM, Andreas Sunardi <a.sunardi(a)gmail.com> > wrote: > >> Following DeepIntoPharo, I tried to install PetitParser into my Pharo 5.0 >> image (I noticed PetitParser installation problem email in March). It >> failed with the message WinPlatform class was undefined. I went to Moose's >> PetitParser site in smalltalkhub and followed the instruction there, and >> this also failed. >> >> Out of frustration, I downloaded Moose 6.0 and thought I'd start from >> Moose image instead. But then I noticed Moose's PetitParser package has >> ConfigurationOfPetitParser from version TudorGirba.77 and the instruction I >> followed was trying to install it using version TudorGirba.80. Back to my >> Pharo 5 image, I unload/remove ConfigurationOfPetitParser and load version >> TudorGirba.77. And this works! >> >> But this way to solve PetitParser installation problem seems wrong. I >> figure if this could very well happen with other packages too. What is the >> right way to find package version that works with my image/pharo version? >> Or is this an issue with PetitParser package itself and should I ask/report >> this to Moose team? >> >> -- >> Andreas Sunardi >> > >

May 12, 2017

Re: [Pharo-users] PetitParser installation fails in Pharo 5.0

by Stephane Ducasse

Hi andreas Normally you should be able to load a package using the ConfigurationBrowser and the configuration (now I do not know the one of PetitParser) should take care of the pharo version for you. stef On Fri, May 12, 2017 at 7:06 PM, Andreas Sunardi <a.sunardi(a)gmail.com> wrote: > Following DeepIntoPharo, I tried to install PetitParser into my Pharo 5.0 > image (I noticed PetitParser installation problem email in March). It > failed with the message WinPlatform class was undefined. I went to Moose's > PetitParser site in smalltalkhub and followed the instruction there, and > this also failed. > > Out of frustration, I downloaded Moose 6.0 and thought I'd start from > Moose image instead. But then I noticed Moose's PetitParser package has > ConfigurationOfPetitParser from version TudorGirba.77 and the instruction I > followed was trying to install it using version TudorGirba.80. Back to my > Pharo 5 image, I unload/remove ConfigurationOfPetitParser and load version > TudorGirba.77. And this works! > > But this way to solve PetitParser installation problem seems wrong. I > figure if this could very well happen with other packages too. What is the > right way to find package version that works with my image/pharo version? > Or is this an issue with PetitParser package itself and should I ask/report > this to Moose team? > > -- > Andreas Sunardi >

May 12, 2017

Re: [Pharo-users] Wandering Through Dependency Hell

by Evan Donahue

Ok, I think this case is closed. Having gotten my code out of the image with Monticello and manual recompile, I can use versionner for upload if and only if I do it in Pharo6. Likewise, I can use it for download if and only if I do it in Pharo6. Pharo5 breaks in strange ways on both ends, even with fresh image/vm. I take this as a sign that I should transition to Pharo6. Relievedly yours, Evan -- View this message in context: http://forum.world.st/Wandering-Through-Dependency-Hell-tp4946266p4946933.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 12, 2017

Basic Iceberg First Commit

by Evan Donahue

Hello, I am trying to get Iceberg working. I have a new Pharo 6 image as of about 5 minutes ago, and I am following the tutorial here: https://github.com/pharo-vcs/iceberg I get as far as cloning the repository, but when I enter my github ssh url and hit "Create repository" I get "LGit_GIT_ERROR: no error message set by libgit2." I am wondering three things: 1) What are the dependencies, libgit or otherwise, that I should make sure to have on my system? I have everything mentioned at the top of teh tutorial. 2) Is this tutorial still up to date enough that I should be getting past this step? I know the code is under development. 3) Is there a way to see what actually gets sent to the ffi? Nothing in the call trace looks especially out of place. Thanks, Evan

May 12, 2017

Re: [Pharo-users] [Zinc] ZnInvalidUTF8: Illegal leading byte for utf-8 encoding

by Udo Schneider

Hi Sven, I didn't tell the whole truth :-) I'm /mainly/ parsing the header (extracting published dates). For some sites however I have to resort to finding a date in the body. CU, Udo Am 12/05/17 um 09:03 schrieb Norbert Hartl: > Just to mention. If you are not interested in the content body you could do a HEAD request instead of GET. > > Norbert > >> Am 11.05.2017 um 22:44 schrieb Udo Schneider <udo.schneider(a)homeaddress.de>: >> >> Hi Sven, >> >> that's perfect. To be honest I don't care about the content - I'm just parsing the header. And even if there is a wrong decoding in there... I can live with that. >> >> Thank you very very much! For your help but also your stuff in general. >> >> CU, >> >> Udo >> >> >>> Am 11/05/17 um 22:35 schrieb Sven Van Caekenberghe: >>> Hi Udo, >>>> On 11 May 2017, at 21:37, Udo Schneider <udo.schneider(a)homeaddress.de> wrote: >>>> >>>> All, >>>> >>>> I'm hitting an error where fetching web content fails. The website does indeed use invalid characters. >>>> >>>> The easiest way to reproduce: >>>> >>>> ZnEasy get: 'http://www.darkreading.com/partner-perspectives/malwarebytes/locky-returns-…' >>>> >>>> Is there any way to tell Zinc to simply ignore that error and to continue? >>>> >>>> CU, >>>> >>>> Udo >>> That server/page has a mime-type text/plain with no explicit encoding (charset) setting, so we have to guess. Like utf-8, pure latin1/iso88591 does not work. The following does work, but you can't be sure everything went well (beLenient takes some bytes as they are). >>> ZnDefaultCharacterEncoder >>> value: ZnCharacterEncoder latin1 beLenient >>> during: [ >>> ZnClient new >>> get: 'http://www.darkreading.com/partner-perspectives/malwarebytes/locky-returns-…'; >>> yourself ]. >>> I added some API earlier today, so that the following should also work (you need to load Zn #bleedingEdge first). >>> ZnClient new >>> defaultEncoder: ZnCharacterEncoder latin1 beLenient; >>> get: 'http://www.darkreading.com/partner-perspectives/malwarebytes/locky-returns-…'; >>> yourself. >>> HTH, >>> Regards, >>> Sven >> >> >> > > >

May 12, 2017

PetitParser installation fails in Pharo 5.0

by Andreas Sunardi

Following DeepIntoPharo, I tried to install PetitParser into my Pharo 5.0 image (I noticed PetitParser installation problem email in March). It failed with the message WinPlatform class was undefined. I went to Moose's PetitParser site in smalltalkhub and followed the instruction there, and this also failed. Out of frustration, I downloaded Moose 6.0 and thought I'd start from Moose image instead. But then I noticed Moose's PetitParser package has ConfigurationOfPetitParser from version TudorGirba.77 and the instruction I followed was trying to install it using version TudorGirba.80. Back to my Pharo 5 image, I unload/remove ConfigurationOfPetitParser and load version TudorGirba.77. And this works! But this way to solve PetitParser installation problem seems wrong. I figure if this could very well happen with other packages too. What is the right way to find package version that works with my image/pharo version? Or is this an issue with PetitParser package itself and should I ask/report this to Moose team? -- Andreas Sunardi

May 12, 2017