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

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

by 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

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

by Stephane Ducasse

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." >> >> >> >> >> >> >

May 12, 2017

Re: [Pharo-users] Wandering Through Dependency Hell

by Evan Donahue

Thanks for the replies. With Juraj's help, I figured out the first layer of my problem. I needed to recompile all the methods after loading the code with Monticello, because their bytecode was all messed up. Now I can get code out of the image via plain Monticello. Tests were failing not because of reversion, but because of random bytecode issues. There is still some odd versioning behavior, but it's not my biggest problem. Now I am trying to create a ConfigurationOf with Versionner. I followed this video: https://www.youtube.com/watch?v=cFRJDuWL-Q0 When I go to commit, Versionner gives me an array out of bounds due to the "KommitStagingArea" not having any elements in its packages array. Sometimes this yields no upload, sometimes it uploads a Config that does not seem to work when I try to download with it, and sometimes I get a debugger on smalltalkhub while trying to view the source. I'm not sure how to predict or interpret which will happen. Essentially, I am just trying to find the simplest, easiest way to let people download a project and its dependencies. The above errors have happened in more or less every project I've tried to commit, and I know other people don't have the same difficulty I do in trying to get code out of and into an image, so I suspect that it is something about my workflow that is off, or possibly my computer. So my first question is, is that video still up to date, or has the system changed? Thanks, Sorry for what I know is not a lot of detail. I'm not really sure where to start with this one. Evan -- View this message in context: http://forum.world.st/Wandering-Through-Dependency-Hell-tp4946266p4946815.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 12, 2017

Re: [Pharo-users] Petri nets and workflow patterns

by phil＠highoctane.be

There is code in several papers, including this one: https://www.dropbox.com/s/lc2ev4841lzn9q0/Worfklow-Continuations.pdf?dl=0 Phil On Thu, May 11, 2017 at 9:07 PM, <serge.stinckwich(a)gmail.com> wrote: > I ask him but he don't have the code anymore, maybe this is possible to do > a retroengineering from the PhD thesis ? > > EnvoyÃ© de mon iPhone > > Le 11 mai 2017 Ã 20:54, Stephane Ducasse <stepharo.self(a)gmail.com> a > Ã©crit : > > yes :) > I contacted the guy to ask for the smalltalk code but he never replied to > me may be someone else should try. > > stef > > On Thu, May 11, 2017 at 9:59 AM, Serge Stinckwich < > serge.stinckwich(a)gmail.com> wrote: > >> On Wed, May 10, 2017 at 10:09 PM, Stephane Ducasse >> <stepharo.self(a)gmail.com> wrote: >> > Norbert >> > >> > I know petri nets and I was wondering if you were interested in worklow >> (as >> > in microworkflow). >> > because I think that a simple extensible workflow library is missing in >> > Pharo >> >> I guess you talk about this: http://micro-workflow.com/phdthesis/ >> >> -- >> Serge Stinckwich >> UCN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ >> >> >

May 11, 2017

Re: [Pharo-users] Petri nets and workflow patterns

by phil＠highoctane.be

I read that paper too and I was wondering about the trempoline piece he uses. Is there someone having implemented that using Pharo? His code was VW. Phil On Thu, May 11, 2017 at 8:54 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > yes :) > I contacted the guy to ask for the smalltalk code but he never replied to > me may be someone else should try. > > stef > > On Thu, May 11, 2017 at 9:59 AM, Serge Stinckwich < > serge.stinckwich(a)gmail.com> wrote: > >> On Wed, May 10, 2017 at 10:09 PM, Stephane Ducasse >> <stepharo.self(a)gmail.com> wrote: >> > Norbert >> > >> > I know petri nets and I was wondering if you were interested in worklow >> (as >> > in microworkflow). >> > because I think that a simple extensible workflow library is missing in >> > Pharo >> >> I guess you talk about this: http://micro-workflow.com/phdthesis/ >> >> -- >> Serge Stinckwich >> UCN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ >> >> >

May 11, 2017

Re: [Pharo-users] Issue with Pillar

by phil＠highoctane.be

Will work in creating the book artifact. But not the PDF because of some crap in TeX. Docker container alleviates that pain. We could make a book builder thing using AppVeyor and docker I think. Phil On Thu, May 11, 2017 at 8:44 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > so > ./pillar archetype book > > will work. > > On Thu, May 11, 2017 at 8:43 PM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> Hi alexandre >> >> This is a problem I identified and I'm trying to fix it. >> Now the version works for book, it is the one I used for all the booklets >> and new books >> I'm writing. >> >> Stef >> >> >> On Wed, May 10, 2017 at 7:42 PM, phil(a)highoctane.be <phil(a)highoctane.be> >> wrote: >> >>> Forget about that way which doesn't work. >>> >>> Use this: https://github.com/cdlm/docker-texlive >>> >>> Works nicely and removes 90% of the setup frustration (you'll need >>> latest docker-ce for this to work). >>> >>> Phil >>> >>> On Wed, May 10, 2017 at 5:38 PM, Alexandre Bergel < >>> alexandre.bergel(a)me.com> wrote: >>> >>>> Hi! >>>> >>>> I am trying to get Pillar working on OS X. I followed the instruction >>>> given on https://ci.inria.fr/pharo-contribution/job/EnterprisePhar >>>> oBook/lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html >>>> >>>> I did: >>>> curl https://raw.githubusercontent.com/pillar-markup/pillar/maste >>>> r/download.sh | bash >>>> ./pillar archetype welcome >>>> make book-result/welcome.html >>>> >>>> The two first instruction do not seem to cause any trouble. Work as >>>> expected. The make instruction produces: >>>> -=-=-=-= >>>> /tmp/pillar> make book-result/welcome.html >>>> mkdir -p ./book-result >>>> find . -type d -path ./book-result -prune -o -wholename "*/figures" >>>> -exec cp {} --parents -r ./book-result \; >>>> cp -r support/ ./book-result >>>> ./pillar export --to=html --outputDirectory=./book-result >>>> --outputFile=welcome.pillar welcome.pillar >>>> MessageNotUnderstood: FileReference>>jsonWriteOn: >>>> FileReference(Object)>>doesNotUnderstand: #jsonWriteOn: >>>> [ :assoc | >>>> needComma >>>> ifTrue: [ aStream nextPut: $, ] >>>> ifFalse: [ needComma := true ]. >>>> assoc key jsonWriteOn: aStream. >>>> aStream nextPut: $:. >>>> assoc value jsonWriteOn: aStream ] in Dictionary>>jsonWriteOn: in >>>> Block: [ :assoc | ... >>>> [ :each | each ifNotNil: [ aBlock value: each ] ] in >>>> Dictionary>>associationsDo: in Block: [ :each | each ifNotNil: [ aBlock >>>> value: each ] ] >>>> Array(SequenceableCollection)>>do: >>>> Dictionary>>associationsDo: >>>> Dictionary>>jsonWriteOn: >>>> PRExportPhase>>asJson:withConfiguration: >>>> [ :outStream | >>>> self >>>> writeOutput: (self asJson: output withConfiguration: >>>> cocoonConfiguration) >>>> toStream: outStream ] in PRExportPhase>>write:using: in Block: [ >>>> :outStream | ... >>>> [ aBlock value: stream ] in FileReference(AbstractFileReference)>>writeStreamDo: >>>> in Block: [ aBlock value: stream ] >>>> BlockClosure>>ensure: >>>> FileReference(AbstractFileReference)>>writeStreamDo: >>>> FileReference(AbstractFileReference)>>pillarWriteDuring: >>>> PRExportPhase>>outputStreamDuring: >>>> PRExportPhase>>write:using: >>>> PRExportPhase>>actionOn: >>>> PRExportPhase class(PRPhase class)>>executeOn: >>>> [ :input | self executeOn: input ] in PRExportPhase class(PRPhase >>>> class)>>buildPipe: in Block: [ :input | self executeOn: input ] >>>> LPPhase>>executeOn: >>>> [ :subResult :next | next executeOn: subResult ] in >>>> LPPipeline>>executeOn: in Block: [ :subResult :next | next executeOn: >>>> subResult ] >>>> [ :each | nextValue := binaryBlock value: nextValue value: each ] in >>>> OrderedCollection(Collection)>>inject:into: in Block: [ :each | >>>> nextValue := binaryBlock value: nextValu...etc... >>>> OrderedCollection>>do: >>>> OrderedCollection(Collection)>>inject:into: >>>> LPPipeline>>executeOn: >>>> PRPillarConfiguration>>export >>>> [ :exporter | (configuration getConfigurationNamed: exporter) export ] >>>> in [ configuration defaultExporters >>>> do: [ :exporter | (configuration getConfigurationNamed: exporter) >>>> export ] ] in PRExportCommandLineHandler>>export in Block: [ :exporter >>>> | (configuration getConfigurationNamed...etc... >>>> Array(SequenceableCollection)>>do: >>>> [ configuration defaultExporters >>>> do: [ :exporter | (configuration getConfigurationNamed: exporter) >>>> export ] ] in PRExportCommandLineHandler>>export in Block: [ >>>> configuration defaultExporters... >>>> BlockClosure>>on:do: >>>> PRExportCommandLineHandler>>export >>>> PRExportCommandLineHandler>>activate >>>> make: *** [book-result/welcome.html.json] Error 1 >>>> rm book-result/welcome.html.json >>>> -=-=-=-= >>>> >>>> Any idea whatâs wrong? >>>> >>>> Cheers, >>>> Alexandre >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>> >> >

May 11, 2017

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

by Udo Schneider

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 11, 2017

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

by 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 11, 2017

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

by Udo Schneider

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

May 11, 2017

Re: [Pharo-users] Petri nets and workflow patterns

by serge.stinckwich＠gmail.com

I ask him but he don't have the code anymore, maybe this is possible to do a retroengineering from the PhD thesis ? EnvoyÃ© de mon iPhone > Le 11 mai 2017 Ã 20:54, Stephane Ducasse <stepharo.self(a)gmail.com> a Ã©crit : > > yes :) > I contacted the guy to ask for the smalltalk code but he never replied to me may be someone else should try. > > stef > >> On Thu, May 11, 2017 at 9:59 AM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >> On Wed, May 10, 2017 at 10:09 PM, Stephane Ducasse >> <stepharo.self(a)gmail.com> wrote: >> > Norbert >> > >> > I know petri nets and I was wondering if you were interested in worklow (as >> > in microworkflow). >> > because I think that a simple extensible workflow library is missing in >> > Pharo >> >> I guess you talk about this: http://micro-workflow.com/phdthesis/ >> >> -- >> Serge Stinckwich >> UCN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ >> >

May 11, 2017