May 2017 - Pharo-users - lists.pharo.org

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

Re: [Pharo-users] SPEC: accept by Tab ?

by Hartmut Krasemann

The error I made: textinputField acceptBlock does not work. the action seems to take a morph. The following worked for me. textinputField bindKeyCombination: Character tab toAction: [:morph| "hereTheAcceptBlockContent." textInputField text: morph text]. But this is ugly. I use a spec with 5 TextinputFields. with or without "asKeyCombination" the additionalKeyBindings only sometimes work, ie. on some of the fields in a spec, but not all (this was even dynamically changing). In those cases where the additional binding of the tab works, the navigation fails. It seems that the tab is consumed either by navigation or the additional keyBinding. And which one is decided by chance. So this will not help me. Any idea? Am 07.05.17 um 09:34 schrieb Stephane Ducasse: > Hi harmunt > > I'm doing too many things to get energy to be concentrated on Spec. > Now I'm surprised that Character space would work as a KeyCombination > > and I saw that the eventKeyStrokes are often converted into a > keyCombination > for the next previous event. > > > registerKeyStrokesForNextFor: aWidget > > aWidget ifNil: [ ^ self ]. > self eventKeyStrokesForNextFocus do: [:each | > aWidget bindKeyCombination: each toAction: [ self giveFocusToNextFrom: > self ] ] > > eventKeyStrokesForNextFocus > "String describing the keystroke to perform to jump to the next widget" > ^ { Character tab asKeyCombination } > > > Can you try > textinputField bindKeyCombination: Character tab asKeyCombination > toAction: textinputField acceptBlock > > > Tx > > > > On Sat, May 6, 2017 at 10:22 PM, Hartmut Krasemann > <Hartmut.Krasemann(a)t-online.de <mailto:Hartmut.Krasemann@t-online.de>> > wrote: > > Hi, > > maybe someone can give me a hint. > I use SPEC for an elaborate GUI with the need to switch autoaccept > of inputFields off. > So accept of textInputFields is by Return. > > Since Tabs are used to navigate anyway, It would be great to > "accept" on leaving the inputField. > > I found the possibility to bind a key/keyCombination to an action > (as is done in ButtonModel initialize: > self bindKeyCombination: Character space toAction: [ self action > ] ) > > However the following code in a TextinputFieldModel > textinputField bindKeyCombination: Character tab toAction: > textinputField acceptBlock > did not work. > > What should I do? > > Thanks for a hint > > -- > > Hartmut Krasemann > KÃ¶nigsberger Str. 41 c > D 22869 Schenefeld > Tel. 040.8307097 > Mobil 0171.6451283 > Krasemann(a)acm.org <mailto:Krasemann@acm.org> > > -- signatur Hartmut Krasemann KÃ¶nigsberger Str. 41 c D 22869 Schenefeld Tel. 040.8307097 Mobil 0171.6451283 Krasemann(a)acm.org

May 12, 2017

Re: [Pharo-users] [ann] bloc & cairo+morphic

by Stephane Ducasse

Tx I will do a pass on the text. The first public demo was at ESUG at Brescia. And this is Igor Stasenko On Fri, May 12, 2017 at 5:34 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > It seems that my initial message generated a misunderstanding. > > My original blog post was meant to communicate two things: > 1. That the known Bloc project has received a new feature that the > community raised as a problem (i.e., host & backend). > 2. Address the other concern that the community raised: how to sustain the > Bloc development in terms of engineering effort. This is why we announced > the financial support for the work of Alex that is valid from this point on. > > The post was certainly not intended to overlook the people that > contributed to the overall project. I apologize if it looked like this. > > To clarify the historical perspective, we now added an explicit history > page on the official project page: > https://github.com/pharo-graphics/Bloc/blob/master/HISTORY.md > > I also changed the blog post to more clearly communicate the intent: > http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/ > > I hope this addresses the concerns. I am really excited that Alain joined > and that we can get even more traction around Bloc. > > Cheers, > Doru > > > > > On May 12, 2017, at 7:56 AM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > > > BTW for an historical perspective > > > > RMoD me and igor were also involved far less than the effort of alain > but as he mentioned it we collaborated on it. I spent time on documenting > several versions and I stopped disgusted to see the total lack of attention > for comments. > > Then Rmod paid nearly a year of effort on Athens, SDL20 support, a year > on TxText. I find really strange that we are not even mentioned in any > support. > > > > Stef > > > > > > On Thu, May 11, 2017 at 8:12 PM, Stephane Ducasse < > stepharo.self(a)gmail.com> wrote: > > Doru can you change the humane assessment blog post? > > > > > > On Thu, May 11, 2017 at 8:07 PM, Tudor Girba <tudor(a)tudorgirba.com> > wrote: > > Hi, > > > > Indeed, this is wonderful news that you will rejoin your baby project :). > > > > Cheers, > > Doru > > > > > > > On May 11, 2017, at 6:40 PM, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > > > > > Hi Alain! > > > > > > Thanks for the mail (even if the historial part has always been pretty > clear to me). > > > We miss you! Be back soon! > > > > > > Cheers, > > > Alexandre > > > -- > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > Alexandre Bergel http://www.bergel.eu > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > >> On May 11, 2017, at 12:36 PM, Alain Plantec via Pharo-dev < > pharo-dev(a)lists.pharo.org> wrote: > > >> > > >> > > >> From: Alain Plantec <alain.plantec(a)yahoo.com> > > >> Subject: Re: [Pharo-users] [ann] bloc & cairo+morphic > > >> Date: May 11, 2017 at 12:36:36 PM GMT-3 > > >> To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > >> Cc: Alain Plantec <alain.plantec(a)yahoo.com>, Moose-related > development <moose-dev(a)list.inf.unibe.ch>, Any question about pharo is > welcome <pharo-users(a)lists.pharo.org> > > >> > > >> > > >> Hello Doru, all, > > >> > > >> Iâm really happy to see Bloc progresses. > > >> Even Iâm not active since more than one year, Bloc is still an > important project for me. > > >> > > >> but let me complete this short historical presentation a little bit. > > >> > > >> Bloc is a project that I initiated in 2013 in collaboration with RMOD > following experiments made around the ROME project. > > >> The idea was to completely revisit the 2D framework of Pharo to > address Morphic limits. > > >> Following an invitation of the Software Composition Group (thanks to > Oscar Nierstrasz and to Doru here), > > >> I presented the first version of Bloc at Bern (March, 2015), then > Doru and Aliaksel joined the project. > > >> One year ago, during his PhD at Brest, Glenn Cavarle produced a new > version of the Bloc infrastructure that is now the > > >> one used together with the layouting system that was implemented by > Aliaksel. > > >> > > >> Please, do not use the humane assessment web site but the github > project one instead. > > >> > > >> I will restart working on Bloc/Brick soon in the context of a project > that we recently signed with the Thales company. > > >> > > >> Thanks, > > >> Cheers > > >> > > >> Alain > > >> > > >> > > >>> On 8 mai 2017, at 23:00, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > >>> > > >>> Hi, > > >>> > > >>> We are happy to announce that based on the work of Glenn, Alex > extended Bloc (Sparta) to work directly in the Morphic world using Cairo as > a backend. > > >>> > > >>> Cairo is less powerful than Moz2D (see the screenshot below for an > example), but the implementation addresses a concern that the community > raised regarding a perceived increased liability due to the dependency to > Moz2D. Essentially this means that Bloc can be treated as another graphical > library that can coexist with Morphic without requiring any external VM > plugin. > > >>> > > >>> <bloc-two-backends-morphic-host-figures.png> > > >>> > > >>> I would also like to point out that adding a new backend and host > was possible because of the many iterations (including throwing away whole > implementations) that Alex and Glenn went through. I think they did an > amazing job. > > >>> > > >>> You can find a bit more details about Bloc here: > > >>> http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/ > > >>> > > >>> Another issue raised regarding Bloc was that of the engineering > effort required to make it a reality. That is why I would also like to > announce that Alex joined feenk.com where he is primarily working on the > graphical stack for Pharo. > > >>> > > >>> Cheers, > > >>> Doru > > >>> > > >>> > > >>> -- > > >>> www.tudorgirba.com > > >>> www.feenk.com > > >>> > > >>> "To lead is not to demand things, it is to make them happen." > > >>> > > >>> > > >>> > > >>> > > >> > > >> > > >> > > >> > > > > > > _______________________________________________ > > > Moose-dev mailing list > > > Moose-dev(a)list.inf.unibe.ch > > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > > > -- > > www.tudorgirba.com > > www.feenk.com > > > > "Yesterday is a fact. > > Tomorrow is a possibility. > > Today is a challenge." > > > > > > > > > > > > > > > > -- > www.tudorgirba.com > www.feenk.com > > "Presenting is storytelling." > > >

May 12, 2017

Re: [Pharo-users] [ann] bloc & cairo+morphic

by Tudor Girba

Hi, It seems that my initial message generated a misunderstanding. My original blog post was meant to communicate two things: 1. That the known Bloc project has received a new feature that the community raised as a problem (i.e., host & backend). 2. Address the other concern that the community raised: how to sustain the Bloc development in terms of engineering effort. This is why we announced the financial support for the work of Alex that is valid from this point on. The post was certainly not intended to overlook the people that contributed to the overall project. I apologize if it looked like this. To clarify the historical perspective, we now added an explicit history page on the official project page: https://github.com/pharo-graphics/Bloc/blob/master/HISTORY.md I also changed the blog post to more clearly communicate the intent: http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/ I hope this addresses the concerns. I am really excited that Alain joined and that we can get even more traction around Bloc. Cheers, Doru > On May 12, 2017, at 7:56 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > BTW for an historical perspective > > RMoD me and igor were also involved far less than the effort of alain but as he mentioned it we collaborated on it. I spent time on documenting several versions and I stopped disgusted to see the total lack of attention for comments. > Then Rmod paid nearly a year of effort on Athens, SDL20 support, a year on TxText. I find really strange that we are not even mentioned in any support. > > Stef > > > On Thu, May 11, 2017 at 8:12 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Doru can you change the humane assessment blog post? > > > On Thu, May 11, 2017 at 8:07 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Indeed, this is wonderful news that you will rejoin your baby project :). > > Cheers, > Doru > > > > On May 11, 2017, at 6:40 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > > > Hi Alain! > > > > Thanks for the mail (even if the historial part has always been pretty clear to me). > > We miss you! Be back soon! > > > > Cheers, > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > >> On May 11, 2017, at 12:36 PM, Alain Plantec via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > >> > >> > >> From: Alain Plantec <alain.plantec(a)yahoo.com> > >> Subject: Re: [Pharo-users] [ann] bloc & cairo+morphic > >> Date: May 11, 2017 at 12:36:36 PM GMT-3 > >> To: Pharo Development List <pharo-dev(a)lists.pharo.org> > >> Cc: Alain Plantec <alain.plantec(a)yahoo.com>, Moose-related development <moose-dev(a)list.inf.unibe.ch>, Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > >> > >> > >> Hello Doru, all, > >> > >> Iâm really happy to see Bloc progresses. > >> Even Iâm not active since more than one year, Bloc is still an important project for me. > >> > >> but let me complete this short historical presentation a little bit. > >> > >> Bloc is a project that I initiated in 2013 in collaboration with RMOD following experiments made around the ROME project. > >> The idea was to completely revisit the 2D framework of Pharo to address Morphic limits. > >> Following an invitation of the Software Composition Group (thanks to Oscar Nierstrasz and to Doru here), > >> I presented the first version of Bloc at Bern (March, 2015), then Doru and Aliaksel joined the project. > >> One year ago, during his PhD at Brest, Glenn Cavarle produced a new version of the Bloc infrastructure that is now the > >> one used together with the layouting system that was implemented by Aliaksel. > >> > >> Please, do not use the humane assessment web site but the github project one instead. > >> > >> I will restart working on Bloc/Brick soon in the context of a project that we recently signed with the Thales company. > >> > >> Thanks, > >> Cheers > >> > >> Alain > >> > >> > >>> On 8 mai 2017, at 23:00, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >>> > >>> Hi, > >>> > >>> We are happy to announce that based on the work of Glenn, Alex extended Bloc (Sparta) to work directly in the Morphic world using Cairo as a backend. > >>> > >>> Cairo is less powerful than Moz2D (see the screenshot below for an example), but the implementation addresses a concern that the community raised regarding a perceived increased liability due to the dependency to Moz2D. Essentially this means that Bloc can be treated as another graphical library that can coexist with Morphic without requiring any external VM plugin. > >>> > >>> <bloc-two-backends-morphic-host-figures.png> > >>> > >>> I would also like to point out that adding a new backend and host was possible because of the many iterations (including throwing away whole implementations) that Alex and Glenn went through. I think they did an amazing job. > >>> > >>> You can find a bit more details about Bloc here: > >>> http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/ > >>> > >>> Another issue raised regarding Bloc was that of the engineering effort required to make it a reality. That is why I would also like to announce that Alex joined feenk.com where he is primarily working on the graphical stack for Pharo. > >>> > >>> Cheers, > >>> Doru > >>> > >>> > >>> -- > >>> www.tudorgirba.com > >>> www.feenk.com > >>> > >>> "To lead is not to demand things, it is to make them happen." > >>> > >>> > >>> > >>> > >> > >> > >> > >> > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.tudorgirba.com > www.feenk.com > > "Yesterday is a fact. > Tomorrow is a possibility. > Today is a challenge." > > > > > > > -- www.tudorgirba.com www.feenk.com "Presenting is storytelling."

May 12, 2017

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

by Ben Coman

On Fri, May 12, 2017 at 10: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_Ex… > > > 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 I can't read Korean, but from the code samples it looks like an intersting demo. Thanks for posting. Do I guess correctly that PHP is used for the server and Pharo for the client? Nice to hear of another corner of the world where Pharo is being used. cheers -ben

May 12, 2017

make a simple sample(for korean)

by peter yoo

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_Ex… 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

<Programming> 2018: Call for Papers

by Sylvia Grewe

------------------------------------------------------------------------------------ <Programming> 2018 : The Art, Science, and Engineering of Programming Mon 9 - Thu 12 April 2018 Nice, France http://2018.programming-conference.org/ In 2017, we started a new conference and journal focused on everything to do with programming, including the experience of programming, called <Programming> for short. The first edition of <Programming> was a great success (see http://twitter.com/programmingconf for testimonies). Paper submissions and publications are handled by the journal. Accepted papers must be presented at the conference. ******************************************************** CALL FOR PAPERS ******************************************************** <Programming> 2018 accept scholarly papers including essays that advance the knowledge of programming. Almost anything about programming is in scope, but in each case there should be a clear relevance to the act and experience of programming. PAPER SUBMISSIONS: August 1 2017 (Research Papers Second Submission Deadline) December 1 2017 (Research Papers Third Submission Deadline) We accept submissions covering several areas of expertise. These areas include, but are not limited to: â¢ General-purpose programming â¢ Distributed systems programming â¢ Parallel and multi-core programming â¢ Graphics and GPU programming â¢ Security programming â¢ User interface programming â¢ Database programming â¢ Visual and live programming â¢ Data mining and machine learning programming â¢ Interpreters, virtual machines and compilers â¢ Modularity and separation of concerns â¢ Model-based development â¢ Metaprogramming and reflection â¢ Testing and debugging â¢ Program verification â¢ Programming education â¢ Programming environments â¢ Social coding ******************************************************** IMPORTANT DATES ******************************************************** Research paper submissions: August 1 2017 (Research Papers Second Submission Deadline) December 1 2017 (Research Papers Third Submission Deadline) Research paper first notification (for second submission deadline): October 1 2017 Research paper final notification (for second submission deadline): November 7 2017 Research paper first notification (for third submission deadline): February 1 2018 Research paper final notification (for third submission deadline): March 7 2018 All important dates can also be found at http://programming-journal.org/timeline/ ******************************************************** ORGANIZATION ******************************************************** General Chair: Manuel Serrano, INRIA France Local Organizing Chair: Tamara Rezk, INRIA France Organizing Committee: Stefan Marr (workshops), Johannes Kepler University Linz Tobias Pape (web technology), HPI - University of Potsdam Sylvia Grewe (publicity), Technische UniversitÃ¤t Darmstadt Germany Program Committee: Guido Salvaneschi (program chair), Technische UniversitÃ¤t Darmstadt, Germany Davide Ancona, University of Genova, Italy Alberto Bacchelli, Delft University of Technology, Netherlands Shigeru Chiba, University of Tokyo, Japan Yvonne Coady, University of Victoria, Canada Susan Eisenbach, Imperial College London, UK Patrick Eugster, TU Darmstadt, Germany and Purdue University, United States Antonio Filieri, Imperial College London, UK Matthew Flatt, University of Utah, United States Lidia Fuentes, Universidad de MÃ¡laga, Spain Richard P. Gabriel, Dream Songs, Inc. & IBM Research, California Jeremy Gibbons, University of Oxford, UK Yossi Gil, Isreal Institute of Technology Elisa Gonzalez Boix, Vrije Universiteit Brussel, Belgium Phlipp Haller, KTH Royal Institute of Technology, Sweden Matthew Hammer, University of Colorado, Boulder, United States Felienne Hermans, Delft University of Technology, Netherlands Robert Hirschfeld, Hasso Plattner Institute (HPI), Germany Roberto Ierusalimschy, Pontifical Catholic University of Rio de Janeiro, Brazil Jun Kato, National Institute of Advanced Industrial Science and Technology, Japan JÃ¶rg Kienzle, McGill University, Canada Neelakantan R. Krishnaswami, University of Cambridge, UK Ralf LÃ¤mmel, University of Koblenz-Landau, Germany Hidehiko Masuhara, Tokyo Institute of Technology, Japan Mira Mezini, Technische UniversitÃ¤t Darmstadt, Germany Emerson Murphy-Hill, North Carolina State University, United States Mario SÃ¼dholt, IMT Atlantique, Inria, France Sam Tobin-Hochstadt, Indiana University, United States Tijs van der Storm, CWI & University of Groningen, Netherlands Eelco Visser, Delft University of Technology, Netherlands ******************************************************** <Programming> 2018 is kindly supported by: INRIA France AOSA ********************************************************

May 12, 2017

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

by PBKResearch

With reference to Norbert's comment, there /may/ be an ambiguity about the word 'header' in Udo's reply. It could refer to the http HEAD section, in which case Norbert is of course right. It could also refer to the <head> section of the html file, which is part of the content of the http response. If it is the latter, this is similar to a question that Paul deBruicker posted last November ("[Pharo-users] ZnClient GET, but just the content of the <head> tag?"). I tried the method I devised for Paul's case on Udo's problem website, and read the html header with no problem. Incidentally, the header includes 'charset=iso-8859-1', which does not agree with Sven's findings. In case it is of interest, I used XMLHTMLParser to read and parse the header. Try the following in a Playground: par := XMLHTMLParser onURL: 'http://www.darkreading.com/partner-perspectives/malwarebytes/locky-returns- with-a-new-(borrowed)-distribution-method/a/d-id/1328723'. par parseDocumentUntil: [|top|(top := par topNode) notNil and: [ top isElement and:[ top isNamed: 'body']]]. par parsingResult findElementNamed: 'head'. If you 'Do it and go', the full header appears. The way I get it to stop after the header may not be quite correct, because it uses XMLHTMLParser>>topNode, which is a private method. On the other hand, I can't see how to make the stop condition for XMLHTMLParser>>parseDocumentUntil: depend on the parsed results without using a private method. Hope this is helpful Peter Kenny -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Norbert Hartl Sent: 12 May 2017 08:04 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] [Zinc] ZnInvalidUTF8: Illegal leading byte for utf-8 encoding 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- with-a-new-(borrowed)-distribution-method/a/d-id/1328723' >>> >>> 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- with-a-new-(borrowed)-distribution-method/a/d-id/1328723'; >> 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- with-a-new-(borrowed)-distribution-method/a/d-id/1328723'; >> yourself. >> HTH, >> Regards, >> Sven > > >

May 12, 2017

Re: [Pharo-users] Intro to git-only Pharo

by Dimitris Chloupis

So far coding solo with git and filetree has been painless and straightforward for me, I use github for public and gitlab for private projects. I do not use configurations other than copy pasting one for adding my project in Package browser. I do not use versioner because a simple copy paste is enough. I do not use iceberg I prefer my favourite git client "gitup". My experience has been both simpler, easier and far more reliable than working with the pharo vcs and smalltalkhub. But I was already familiar with git because I was already an experienced python coder , and still am, way before working with Pharo. I have made a tutorial about Pharo and git that can be viewed here. Its with sourcetree not gitup because gitup is only available for macos and I wanted to make a tutorial that would work on all 3 major desktop OSes. https://www.youtube.com/watch?v=n2WNYDtO0cE On Thu, May 11, 2017 at 9:56 PM Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Le 11/05/2017 Ã 20:52, Stephane Ducasse a Ã©crit : > > Joachim > > > > many people are using Pharo to develop ***COMPLEX*** Pharo applications > > and it works. They use monticello and metacello and it works. > > So you do not have to have Github to make great software in Pharo. > > > > Now in addition many people are using github to build complex > applications > > with github. > > And people have been building complex applications with Monticello, > Metacello and Github... > > Thierry > > > > > Stef > > > > > > On Thu, May 11, 2017 at 9:54 AM, Norbert Hartl <norbert(a)hartl.name > > <mailto:norbert@hartl.name>> wrote: > > > > > >> Am 11.05.2017 um 08:54 schrieb jtuchel(a)objektfabrik.de > >> <mailto:jtuchel@objektfabrik.de>: > >> > >> Hi Norbert, > >> > >> thanks for your explanations. > >> So it seems liek I should start by using Pharo6 and load Iceberg > >> and just take a look. > >> > > Yes, iceberg has still some issues but is usable and it will evolve > > quickly. If you are the brave type of guy you can start with pharo6 > > 64bits ;) > > > > Norbert > > > >> Joachim > >> > >> > >> > >> Am 10.05.17 um 10:34 schrieb Norbert Hartl: > >>> Hi Joachim, > >>> > >>> I think your timing is quite good. We had some changes in the > >>> last years and it is getting better now. > >>> Before we had only monticello. Monticello is a zip container that > >>> contains a version number in the filename and prior version > >>> pointer inside the repository. Regarding dependencies there was > >>> nothing that was used widely. Then Metacello appeared and solved > >>> the problem by providing dependency management and versioning of > >>> dependencies. Dependency management works good, the integrated > >>> versioning has issues. Especially when you look at a system like > >>> git you can see that versioning is solved there. Filetree is > >>> needed because git and other vcs systems are file based so you > >>> need to layout your code in files (how quaint!) > >>> To make a long story short: The best thing to use is git with > >>> Metacello Baselines. Filetree is used to store code. Versioning > >>> you do with git tags that can be used in Baselines. Now we have a > >>> decent UI (iceberg) that supports the most needed workflow items. > >>> We have a UI for the dependency management as well (versionner) > >>> but it sadly targets ConfigurationOfs and not BaselineOfs. That > >>> needs to be changed. > >>> > >>> my 2 cents, > >>> > >>> Norbert > >>> > >>>> Am 10.05.2017 um 07:56 schrieb Joachim Tuchel > >>>> <jtuchel(a)objektfabrik.de <mailto:jtuchel@objektfabrik.de>>: > >>>> > >>>> Hi guys, > >>>> > >>>> please forgive me if this mail is a sign of ignorance. I am not > >>>> a regular Pharo user and one of the reasons for this is that I > >>>> didn't like most of the source management tools around > >>>> Monticello. Coming from an envy background, it feels like not > >>>> being ready for prime time. Of course you guys have been proving > >>>> you can work with these tools quite well, but still I'd be > >>>> interested in using Pharo in a pure git-based environment, as it > >>>> most closely resembles some of the most-beloved features of envy. > >>>> > >>>> Over the years there was a lot of work and discussion on > >>>> filetree, gitfiletree, iceberg, cypress and maybe quite a few > >>>> other projects that sounded promising and interesting. But I > >>>> must admit I lost track of what was really done and how far > >>>> things went in the last years. > >>>> > >>>> So are there any pointers to info material that I could look at > >>>> to see what the current status of source control in Pharo 5 and > >>>> Pharo 6 is and/or will be soon? > >>>> > >>>> I am mostly interested in these topics: > >>>> > >>>> * git only - no monticello meta info any more - possible? > >>>> * tools like merge/diff, committing from within the image > >>>> * dependencies within my own project as well as dependencies > >>>> on external code in - possibly multiple - external > repositories > >>>> * what is the current "most official" source repository for > >>>> open source code? > >>>> * best practices for managing complex projects and keeping old > >>>> versions reproducible at any time > >>>> * tutorial for git newbies in a Pharo context? (Like, how do I > >>>> start with a new packege - create folder first and do git > >>>> init, or start in the image and push into repo later? as I > >>>> said: beginners' stuff) > >>>> > >>>> Thanks for pointers and help > >>>> > >>>> > >>>> Joachim > >>>> > >>>> > >>> > >> > >> > >> -- > >> > ----------------------------------------------------------------------- > >> Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de > >> Fliederweg 1 http://www.objektfabrik.de < > http://www.objektfabrik.de/> > >> D-71640 Ludwigsburg > http://joachimtuchel.wordpress.com > >> <http://joachimtuchel.wordpress.com/> > >> Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 > >> > > > > > > >

May 12, 2017