- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Issue Tracker] Problem with Spam

by Marcus Denker

With the help of the Fogbugz support I have disabled the anon submission page for now. > On 26 Jan 2018, at 10:18, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > I have not yet found a way to do it. > > https://forum.manuscript.com/t/dozens-of-spam-emails-a-day-how-do-i-turn-of… <https://forum.manuscript.com/t/dozens-of-spam-emails-a-day-how-do-i-turn-of…> > > >> On 26 Jan 2018, at 10:13, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: >> >> I guess these are anonymous submissions ? >> Can't this (for now at least) not be restricted to actual users that need to authenticate first ? >> >>> On 26 Jan 2018, at 10:09, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >>> >>> Hi, >>> >>> Since some days we get ~20 spam cases per day on the issue tracker. >>> >>> -> I have asked on the Forums what we can do >>> -> As long as there is no solution, I am closing them the morning. >>> >>> Marcus >>> >> >> >

Jan. 30, 2018

Re: [Pharo-dev] [ANN] Fog - Ethereum driver

by Rafael Luque

Hi Santiago, Maybe I could try to add the event support if I could manage to find the time and I can disturb you with my noob questions. Rafa. 2018-01-29 18:55 GMT+00:00 Santiago Bragagnolo <santiagobragagnolo(a)gmail.com >: > Hi Rafael! > Events are not yet supported sadly. > If you are willing to do something about, we can discuss. By my side I > will be kind of busy during february. > > I hope to be able to do something about on march, but i cannot guarantee > it > > Santiago > > > On Mon, 29 Jan 2018 at 17:40 Rafael Luque <rafael.luque.leiva(a)gmail.com> > wrote: > >> Hi Santiago, >> >> I'm currently playing with Dapps on Ethereum using Truffle and web3.js, >> but it would be great to be able to use Pharo. >> >> I've downloaded Fog and started to read the tests and code, but I don't >> see support for events that is something I need for my current use cases. >> Maybe I don't know where to look or events are not (yet) supported? >> >> In any case, thank you for this contribution. >> >> >> 2017-03-14 9:51 GMT+00:00 Santiago Bragagnolo < >> santiagobragagnolo(a)gmail.com>: >> >>> You are welcome :). We are doing some experiments for looking some >>> research branches on it. >>> So, writing some Dapps but not really productive. or not yet. >>> Any way, we still using solidity as language for the contracts. >>> >>> Santiago >>> >>> >>> >>> On Mon, 13 Mar 2017 at 19:44 Esteban A. Maringolo <emaringolo(a)gmail.com> >>> wrote: >>> >>>> Very Nice! Thank you for building it. >>>> >>>> I started a similar project for the Bitcoin blockchain, but then I >>>> drifted away and never got back to it. >>>> >>>> Are you writing DAPPs? >>>> >>>> Best regards, >>>> >>>> Esteban A. Maringolo >>>> >>>> >>>> 2017-03-13 12:00 GMT-03:00 Santiago Bragagnolo < >>>> santiagobragagnolo(a)gmail.com>: >>>> > Hi all. Im happy to announce a pre release of the Fog ethereum driver >>>> that >>>> > we develop in the space of an Inria project. >>>> > >>>> > It still not complete but is already usable for some experiments and >>>> simple >>>> > projects. >>>> > >>>> > You can downloadit from >>>> > https://github.com/sbragagnolo/Fog/ >>>> > (https://github.com/sbragagnolo/Fog/releases/tag/v0.1.1.1) >>>> > >>>> > Dependencies >>>> > >>>> > RHash >>>> > >>>> > sudo apt-get install rhash >>>> > >>>> > Solidity >>>> > >>>> > npm install solc >>>> > >>>> > Download code >>>> > >>>> > Iceberg / Baseline >>>> > >>>> > Metacello >>>> > new >>>> > baseline: 'Fog'; >>>> > repository: 'github://sbragagnolo/Fog:v0.1.1.1/src'; >>>> > load. >>>> > >>>> > By hand >>>> > >>>> > You may want to use this version for having access to some scripts and >>>> > contracts samples. >>>> > >>>> > git checkout git@github.com:sbragagnolo/Fog.git >>>> > >>>> > git checkout v0.1.1.1 >>>> > >>>> > Metacello >>>> > new >>>> > baseline: 'Fog'; >>>> > repository: 'filetree:///path/to/git-repository/Fog/src';; >>>> > load. >>>> > >>>> > >>>> > It's based on the standar API for javascript >>>> > (https://github.com/ethereum/wiki/wiki/JavaScript-API) . >>>> > >>>> > It provides interaction with remote contracts, it do as well provides >>>> a way >>>> > for navigating the architecture objects: blocks, transactions, >>>> accounts and >>>> > contracts. >>>> > >>>> > I hope you find it useful. >>>> > >>>> > Feel free to fill the github issue tracker with anything you find :). >>>> > >>>> > >>>> > I will come to you with some new exciting news about ethereum soon :) >>>> > >>>> > Santiago. >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> >>>> >>

Jan. 30, 2018

Re: [Pharo-dev] [ANN] Fog - Ethereum driver

by Rafael Luque

Hi Ben, I did these courses and they were very useful for me: https://www.zastrin.com/ Also the book "Blockchain Applications: A Hands-On Approach": https://www.amazon.com/Blockchain-Applications-Hands-Arshdeep-Bahga/dp/0996… Btw, Manning has the following MEAP: https://www.manning.com/books/building-ethereum-dapps Rafa. 2018-01-29 22:28 GMT+00:00 Ben Coman <btc(a)openinworld.com>: > btw, I started doing this course... > https://www.udemy.com/ethereum-dapp/ > and hopefully this knowledge can transfer over to Pharo. > > Can anyone recommend other learning resources? > > cheers -ben > > On 30 January 2018 at 02:55, Santiago Bragagnolo > <santiagobragagnolo(a)gmail.com> wrote: > > Hi Rafael! > > Events are not yet supported sadly. > > If you are willing to do something about, we can discuss. By my side I > will > > be kind of busy during february. > > > > I hope to be able to do something about on march, but i cannot guarantee > it > > > > Santiago > > > > > > On Mon, 29 Jan 2018 at 17:40 Rafael Luque <rafael.luque.leiva(a)gmail.com> > > wrote: > >> > >> Hi Santiago, > >> > >> I'm currently playing with Dapps on Ethereum using Truffle and web3.js, > >> but it would be great to be able to use Pharo. > >> > >> I've downloaded Fog and started to read the tests and code, but I don't > >> see support for events that is something I need for my current use > cases. > >> Maybe I don't know where to look or events are not (yet) supported? > >> > >> In any case, thank you for this contribution. > >> > >> > >> 2017-03-14 9:51 GMT+00:00 Santiago Bragagnolo > >> <santiagobragagnolo(a)gmail.com>: > >>> > >>> You are welcome :). We are doing some experiments for looking some > >>> research branches on it. > >>> So, writing some Dapps but not really productive. or not yet. > >>> Any way, we still using solidity as language for the contracts. > >>> > >>> Santiago > >>> > >>> > >>> > >>> On Mon, 13 Mar 2017 at 19:44 Esteban A. Maringolo < > emaringolo(a)gmail.com> > >>> wrote: > >>>> > >>>> Very Nice! Thank you for building it. > >>>> > >>>> I started a similar project for the Bitcoin blockchain, but then I > >>>> drifted away and never got back to it. > >>>> > >>>> Are you writing DAPPs? > >>>> > >>>> Best regards, > >>>> > >>>> Esteban A. Maringolo > >>>> > >>>> > >>>> 2017-03-13 12:00 GMT-03:00 Santiago Bragagnolo > >>>> <santiagobragagnolo(a)gmail.com>: > >>>> > Hi all. Im happy to announce a pre release of the Fog ethereum > driver > >>>> > that > >>>> > we develop in the space of an Inria project. > >>>> > > >>>> > It still not complete but is already usable for some experiments and > >>>> > simple > >>>> > projects. > >>>> > > >>>> > You can downloadit from > >>>> > https://github.com/sbragagnolo/Fog/ > >>>> > (https://github.com/sbragagnolo/Fog/releases/tag/v0.1.1.1) > >>>> > > >>>> > Dependencies > >>>> > > >>>> > RHash > >>>> > > >>>> > sudo apt-get install rhash > >>>> > > >>>> > Solidity > >>>> > > >>>> > npm install solc > >>>> > > >>>> > Download code > >>>> > > >>>> > Iceberg / Baseline > >>>> > > >>>> > Metacello > >>>> > new > >>>> > baseline: 'Fog'; > >>>> > repository: 'github://sbragagnolo/Fog:v0.1.1.1/src'; > >>>> > load. > >>>> > > >>>> > By hand > >>>> > > >>>> > You may want to use this version for having access to some scripts > and > >>>> > contracts samples. > >>>> > > >>>> > git checkout git@github.com:sbragagnolo/Fog.git > >>>> > > >>>> > git checkout v0.1.1.1 > >>>> > > >>>> > Metacello > >>>> > new > >>>> > baseline: 'Fog'; > >>>> > repository: 'filetree:///path/to/git-repository/Fog/src';; > >>>> > load. > >>>> > > >>>> > > >>>> > It's based on the standar API for javascript > >>>> > (https://github.com/ethereum/wiki/wiki/JavaScript-API) . > >>>> > > >>>> > It provides interaction with remote contracts, it do as well > provides > >>>> > a way > >>>> > for navigating the architecture objects: blocks, transactions, > >>>> > accounts and > >>>> > contracts. > >>>> > > >>>> > I hope you find it useful. > >>>> > > >>>> > Feel free to fill the github issue tracker with anything you find > :). > >>>> > > >>>> > > >>>> > I will come to you with some new exciting news about ethereum soon > :) > >>>> > > >>>> > Santiago. > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > >> > > > >

Jan. 30, 2018

[Pharo 7.0-dev] Build #477: 21175-ReleaseTest-testUndeclared-should-allow-stubs-for-test-purpose

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #477 was: SUCCESS. The Pull Request #773 was integrated: "21175-ReleaseTest-testUndeclared-should-allow-stubs-for-test-purpose" Pull request url: https://github.com/pharo-project/pharo/pull/773 Issue Url: https://pharo.fogbugz.com/f/cases/21175 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 30, 2018

Re: [Pharo-dev] How to add a new rule?

by Yuriy Tymchuk

Cool, let me know how it goes! Sent from my iPad > On 29 Jan 2018, at 21:12, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Ok vincent told me that he succeeded and we can use its example. > We can also ask benoit how he extended renaku. > I will set up a booklet. > > > >> On Mon, Jan 29, 2018 at 1:42 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> >> Sent from my iPad >> >>> On 28 Jan 2018, at 22:50, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>> >>> Ok I will add your email next time. >>> >>> >>>> On Sun, Jan 28, 2018 at 8:57 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>>> Hi Stef. >>>> >>>> First of all, please include my email in the recipients list. Iâm committed to maintain the Rule infrastructure, but I rarely manage to read through Pharo dev. I was nice that Myroslava told me about this email. >>> >>> Ok I will add your email next time. >>> >>>> Secondly I suppose that you are working on Pharo 7, because Pharo 6 mostly follows the old approach. >>> >>> I do not know since it was not on my machine but most probably pharo 70 >> >> If it is Pharo 6 then you can just follow the old smalllint strategy, but you may need to reset the cache. >> >>> >>>> >>>> One thing that can cause a rule not showing up is caching, and although it should be automatically invalidated upon the addition of a new rule, you can manually clear it by searching for âRenrakuâ in settings and pressing the âReset rule cacheâ button. >>> >>> Ahhhhhh this is what we suspected. >>> >>>> You should not subclass RBTransformationRule, you should subclass ReNodeRewriteRule. In fact if you check, there are no subclasses of RBTransformationRule. >>> >>> This is strange because I remember that ifNotNilDo was a subclass. >>> But again is was on a machine with super small fonts :) >>> >>>> >>>> Now about documentation. I suspect that my IWST presentation and the Renraku paper (Thesis chapter) are not enough, but the problem is that nobody tried to create rules and give me a feedback about that so far. As you are adding new rules, I think that this is a nice opportunity to write some kind of a booklet, because rules are really powerful and we should share the knowledge of how to create them (and we should also simplify the creation process). >>> >>> Yes I would love to have a booklet on that. Do you want to join effort? >> >> Yes, but I need user experience. Because I already tried to document Renraku here and there but I donât know what is not clear. Also I expect that Myroslava can join. >> >>> >>> >>>> Right now there is a âRenraku Quality Rulesâ help group in the main Pharo help browser that provides a brief description of how to create rules and run them. I think that this is a good starting point because I tried to put there the essential information needed to start with rule creation. >>> >>> Excellent we will read it. >>> >>> >>>> P.S. what would be nice is to generate booklets from Pharo help, because I does not make sense to have 2 sources of documentation. >>> >>> Yes we are working on Pillar and we will get there. Now a booklet for >>> three or four pages of description is not worth. >>> So may be the inverse is better. What we could do is to extend the >>> help to display the pillar booklet inside the image. But slowing.... >>> >>> >>>> Cheers. >>>> Uko >>>> >>>>> On 27 Jan 2018, at 16:19, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>>>> >>>>> Hi yuriy >>>>> >>>>> We defined a new rule subclass of RBTransformationRule and we did not >>>>> get why the rule >>>>> was not taken into account. >>>>> >>>>> We put an halt in another class such as ifNotNilDo: in >>>>> - initialize (is there a cache)? >>>>> - checkMethod: >>>>> >>>>> and it did not stop. >>>>> We started to >>>>> to watch your ESUG videos >>>>> to read your PhD >>>>> >>>>> but it did not help us. >>>>> >>>>> Stef >>>>> >>>> >>>> >>> >> >

Jan. 30, 2018

Re: [Pharo-dev] [ANN] Fog - Ethereum driver

by Ben Coman

btw, I started doing this course... https://www.udemy.com/ethereum-dapp/ and hopefully this knowledge can transfer over to Pharo. Can anyone recommend other learning resources? cheers -ben On 30 January 2018 at 02:55, Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> wrote: > Hi Rafael! > Events are not yet supported sadly. > If you are willing to do something about, we can discuss. By my side I will > be kind of busy during february. > > I hope to be able to do something about on march, but i cannot guarantee it > > Santiago > > > On Mon, 29 Jan 2018 at 17:40 Rafael Luque <rafael.luque.leiva(a)gmail.com> > wrote: >> >> Hi Santiago, >> >> I'm currently playing with Dapps on Ethereum using Truffle and web3.js, >> but it would be great to be able to use Pharo. >> >> I've downloaded Fog and started to read the tests and code, but I don't >> see support for events that is something I need for my current use cases. >> Maybe I don't know where to look or events are not (yet) supported? >> >> In any case, thank you for this contribution. >> >> >> 2017-03-14 9:51 GMT+00:00 Santiago Bragagnolo >> <santiagobragagnolo(a)gmail.com>: >>> >>> You are welcome :). We are doing some experiments for looking some >>> research branches on it. >>> So, writing some Dapps but not really productive. or not yet. >>> Any way, we still using solidity as language for the contracts. >>> >>> Santiago >>> >>> >>> >>> On Mon, 13 Mar 2017 at 19:44 Esteban A. Maringolo <emaringolo(a)gmail.com> >>> wrote: >>>> >>>> Very Nice! Thank you for building it. >>>> >>>> I started a similar project for the Bitcoin blockchain, but then I >>>> drifted away and never got back to it. >>>> >>>> Are you writing DAPPs? >>>> >>>> Best regards, >>>> >>>> Esteban A. Maringolo >>>> >>>> >>>> 2017-03-13 12:00 GMT-03:00 Santiago Bragagnolo >>>> <santiagobragagnolo(a)gmail.com>: >>>> > Hi all. Im happy to announce a pre release of the Fog ethereum driver >>>> > that >>>> > we develop in the space of an Inria project. >>>> > >>>> > It still not complete but is already usable for some experiments and >>>> > simple >>>> > projects. >>>> > >>>> > You can downloadit from >>>> > https://github.com/sbragagnolo/Fog/ >>>> > (https://github.com/sbragagnolo/Fog/releases/tag/v0.1.1.1) >>>> > >>>> > Dependencies >>>> > >>>> > RHash >>>> > >>>> > sudo apt-get install rhash >>>> > >>>> > Solidity >>>> > >>>> > npm install solc >>>> > >>>> > Download code >>>> > >>>> > Iceberg / Baseline >>>> > >>>> > Metacello >>>> > new >>>> > baseline: 'Fog'; >>>> > repository: 'github://sbragagnolo/Fog:v0.1.1.1/src'; >>>> > load. >>>> > >>>> > By hand >>>> > >>>> > You may want to use this version for having access to some scripts and >>>> > contracts samples. >>>> > >>>> > git checkout git@github.com:sbragagnolo/Fog.git >>>> > >>>> > git checkout v0.1.1.1 >>>> > >>>> > Metacello >>>> > new >>>> > baseline: 'Fog'; >>>> > repository: 'filetree:///path/to/git-repository/Fog/src';; >>>> > load. >>>> > >>>> > >>>> > It's based on the standar API for javascript >>>> > (https://github.com/ethereum/wiki/wiki/JavaScript-API) . >>>> > >>>> > It provides interaction with remote contracts, it do as well provides >>>> > a way >>>> > for navigating the architecture objects: blocks, transactions, >>>> > accounts and >>>> > contracts. >>>> > >>>> > I hope you find it useful. >>>> > >>>> > Feel free to fill the github issue tracker with anything you find :). >>>> > >>>> > >>>> > I will come to you with some new exciting news about ethereum soon :) >>>> > >>>> > Santiago. >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> >> >

Jan. 29, 2018

Re: [Pharo-dev] How to add a new rule?

by Stephane Ducasse

Ok vincent told me that he succeeded and we can use its example. We can also ask benoit how he extended renaku. I will set up a booklet. On Mon, Jan 29, 2018 at 1:42 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > > Sent from my iPad > >> On 28 Jan 2018, at 22:50, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Ok I will add your email next time. >> >> >>> On Sun, Jan 28, 2018 at 8:57 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>> Hi Stef. >>> >>> First of all, please include my email in the recipients list. Iâm committed to maintain the Rule infrastructure, but I rarely manage to read through Pharo dev. I was nice that Myroslava told me about this email. >> >> Ok I will add your email next time. >> >>> Secondly I suppose that you are working on Pharo 7, because Pharo 6 mostly follows the old approach. >> >> I do not know since it was not on my machine but most probably pharo 70 > > If it is Pharo 6 then you can just follow the old smalllint strategy, but you may need to reset the cache. > >> >>> >>> One thing that can cause a rule not showing up is caching, and although it should be automatically invalidated upon the addition of a new rule, you can manually clear it by searching for âRenrakuâ in settings and pressing the âReset rule cacheâ button. >> >> Ahhhhhh this is what we suspected. >> >>> You should not subclass RBTransformationRule, you should subclass ReNodeRewriteRule. In fact if you check, there are no subclasses of RBTransformationRule. >> >> This is strange because I remember that ifNotNilDo was a subclass. >> But again is was on a machine with super small fonts :) >> >>> >>> Now about documentation. I suspect that my IWST presentation and the Renraku paper (Thesis chapter) are not enough, but the problem is that nobody tried to create rules and give me a feedback about that so far. As you are adding new rules, I think that this is a nice opportunity to write some kind of a booklet, because rules are really powerful and we should share the knowledge of how to create them (and we should also simplify the creation process). >> >> Yes I would love to have a booklet on that. Do you want to join effort? > > Yes, but I need user experience. Because I already tried to document Renraku here and there but I donât know what is not clear. Also I expect that Myroslava can join. > >> >> >>> Right now there is a âRenraku Quality Rulesâ help group in the main Pharo help browser that provides a brief description of how to create rules and run them. I think that this is a good starting point because I tried to put there the essential information needed to start with rule creation. >> >> Excellent we will read it. >> >> >>> P.S. what would be nice is to generate booklets from Pharo help, because I does not make sense to have 2 sources of documentation. >> >> Yes we are working on Pillar and we will get there. Now a booklet for >> three or four pages of description is not worth. >> So may be the inverse is better. What we could do is to extend the >> help to display the pillar booklet inside the image. But slowing.... >> >> >>> Cheers. >>> Uko >>> >>>> On 27 Jan 2018, at 16:19, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>>> >>>> Hi yuriy >>>> >>>> We defined a new rule subclass of RBTransformationRule and we did not >>>> get why the rule >>>> was not taken into account. >>>> >>>> We put an halt in another class such as ifNotNilDo: in >>>> - initialize (is there a cache)? >>>> - checkMethod: >>>> >>>> and it did not stop. >>>> We started to >>>> to watch your ESUG videos >>>> to read your PhD >>>> >>>> but it did not help us. >>>> >>>> Stef >>>> >>> >>> >> >

Jan. 29, 2018

Re: [Pharo-dev] How to get rid of empty XML nodes?

by Stephane Ducasse

Tx monty. I will update it because I do not want to lose all the pds if bintray collapse. I plan to revise all the booklets since I will put them on lulu so that people can get them printed. Stef On Mon, Jan 29, 2018 at 2:00 PM, monty <monty2(a)programmer.net> wrote: > I attached a commit patch (apply with `git am ...`) to the 'books.pharo.org' repo to update the Scraping .pdf link. (The .pdf it links to now is obsolete.) > >> Sent: Friday, January 26, 2018 at 2:30 PM >> From: "Stephane Ducasse" <stepharo.self(a)gmail.com> >> To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> Subject: Re: [Pharo-dev] How to get rid of empty XML nodes? >> >> Tx Monty! >> This is a really important addition :) >> Because a super frequent scenario. >> >> Stef >> >> On Fri, Jan 26, 2018 at 8:37 AM, monty <monty2(a)programmer.net> wrote: >> > See #removeAllFormattingNodes and its comment in the latest version. >> > >> > And instances of SAXHandler and subclasses are meant to be created with #on: (or another "instance creation" message), _not #new_, otherwise they won't be properly initialized. The class comment is clear about this, but I should have overridden #new to raise an error like Stream does. Your misuse was helpful in bringing this to my attention, and I added a Stream-like #new implementation to SAXHandler. >> > >> >> Sent: Friday, December 08, 2017 at 9:21 AM >> >> From: "Stephane Ducasse" <stepharo.self(a)gmail.com> >> >> To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> >> Subject: Re: [Pharo-dev] How to get rid of empty XML nodes? >> >> >> >> Hi monty >> >> >> >> >> >> On Fri, Dec 8, 2017 at 9:03 AM, monty <monty2(a)programmer.net> wrote: >> >> > By "empty XML nodes," do you mean whitespace-only string nodes? >> >> >> >> Yes >> >> >> >> > Those are included because all in-element whitespace is assumed significant by the spec: https://www.w3.org/TR/xml/#sec-white-space >> >> >> >> I know. There was a discussion a while ago. I just lost a couple of >> >> hours understanding that :( >> >> >> >> But this is a super super super annoying practices. >> >> We had to test each nodes to see if it is a empty nodes so it makes >> >> everything a lot more complex without real justification >> >> beside the fact that these standardizers probably never implemented >> >> some real cases. >> >> This standard is a really out of reality from that perspective. >> >> >> >> > The exception is if the element is declared in the DTD as only having element children ("element content"): https://www.w3.org/TR/xml/#dt-elemcontent >> >> >> >> Well the XML files that I had (I did not choose XML because I would >> >> have prefer JSON :) ), had no DTD :( >> >> >> >> So at the end of the day, this wonderful standard puts all the stress >> >> and burden to people. >> >> >> >> > >> >> > For example, if you declare an element like this: >> >> > >> >> > <!ELEMENT one (two,three*,four?)> >> >> > >> >> > Any whitespace around a "two," "three," or "four" element child of a "one" element is insignificant and ignored (unless #preservesIgnorableWhitespace: is true). Other parsers, like LibXML2 and Xerces, behave the same way. >> >> > >> >> > I'll see if I can come up with some easier way to deal with this, like an optional parser setting, new enumeration methods, or maybe a tree transformation. >> >> >> >> It would be A HUGE PLUS!!!!!!!!!!!!!!!!!! >> >> >> >> >> >> Because reality is that people have XML files with just nodes and no >> >> empty nodes and they are forced to >> >> Let me know because I could try. >> >> >> >> I was showing how to use Pharo to import code to pharo learners and >> >> this was a big drag. >> >> >> >> Stef >> >> >> >> >> >> I tried to set some values in the parser but it did not work. >> >> BTW I saw that the configuration logic forces to write the following >> >> >> >> | parser doc visitor | >> >> parser := XMLDOMParser new >> >> on: self xmlContents; >> >> preservesIgnorableWhitespace: true. >> >> >> >> and not >> >> >> >> | parser doc visitor | >> >> parser := XMLDOMParser new >> >> preservesIgnorableWhitespace: true. >> >> on: self xmlContents; >> >> >> >> >> >> > >> >> >> Sent: Tuesday, December 05, 2017 at 8:29 AM >> >> >> From: "Stephane Ducasse" <stepharo.self(a)gmail.com> >> >> >> To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> >> >> Subject: [Pharo-dev] How to get rid of empty XML nodes? >> >> >> >> >> >> )Hi >> >> >> >> >> >> we are manipulating an XML document and I would like to get rid of the >> >> >> spurious empty string. >> >> >> We saw that the gt panes are doing it. >> >> >> >> >> >> (aNodeWithElements isStringNode >> >> >> and: [aNodeWithElements isEmpty >> >> >> or: [aNodeWithElements isWhitespace]] >> >> >> >> >> >> Is there a way not to produce empty nodes? >> >> >> Is there a simple way not to have to handle them >> >> >> >> >> >> Now each time we are dealing with a node with have to check. >> >> >> >> >> >> Stef >> >> >> >> >> >> >> >> > >> >> >> >> >> > >> >>

Jan. 29, 2018

Re: [Pharo-dev] [ANN] Fog - Ethereum driver

by Santiago Bragagnolo

Hi Rafael! Events are not yet supported sadly. If you are willing to do something about, we can discuss. By my side I will be kind of busy during february. I hope to be able to do something about on march, but i cannot guarantee it Santiago On Mon, 29 Jan 2018 at 17:40 Rafael Luque <rafael.luque.leiva(a)gmail.com> wrote: > Hi Santiago, > > I'm currently playing with Dapps on Ethereum using Truffle and web3.js, > but it would be great to be able to use Pharo. > > I've downloaded Fog and started to read the tests and code, but I don't > see support for events that is something I need for my current use cases. > Maybe I don't know where to look or events are not (yet) supported? > > In any case, thank you for this contribution. > > > 2017-03-14 9:51 GMT+00:00 Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com>: > >> You are welcome :). We are doing some experiments for looking some >> research branches on it. >> So, writing some Dapps but not really productive. or not yet. >> Any way, we still using solidity as language for the contracts. >> >> Santiago >> >> >> >> On Mon, 13 Mar 2017 at 19:44 Esteban A. Maringolo <emaringolo(a)gmail.com> >> wrote: >> >>> Very Nice! Thank you for building it. >>> >>> I started a similar project for the Bitcoin blockchain, but then I >>> drifted away and never got back to it. >>> >>> Are you writing DAPPs? >>> >>> Best regards, >>> >>> Esteban A. Maringolo >>> >>> >>> 2017-03-13 12:00 GMT-03:00 Santiago Bragagnolo < >>> santiagobragagnolo(a)gmail.com>: >>> > Hi all. Im happy to announce a pre release of the Fog ethereum driver >>> that >>> > we develop in the space of an Inria project. >>> > >>> > It still not complete but is already usable for some experiments and >>> simple >>> > projects. >>> > >>> > You can downloadit from >>> > https://github.com/sbragagnolo/Fog/ >>> > (https://github.com/sbragagnolo/Fog/releases/tag/v0.1.1.1) >>> > >>> > Dependencies >>> > >>> > RHash >>> > >>> > sudo apt-get install rhash >>> > >>> > Solidity >>> > >>> > npm install solc >>> > >>> > Download code >>> > >>> > Iceberg / Baseline >>> > >>> > Metacello >>> > new >>> > baseline: 'Fog'; >>> > repository: 'github://sbragagnolo/Fog:v0.1.1.1/src'; >>> > load. >>> > >>> > By hand >>> > >>> > You may want to use this version for having access to some scripts and >>> > contracts samples. >>> > >>> > git checkout git@github.com:sbragagnolo/Fog.git >>> > >>> > git checkout v0.1.1.1 >>> > >>> > Metacello >>> > new >>> > baseline: 'Fog'; >>> > repository: 'filetree:///path/to/git-repository/Fog/src';; >>> > load. >>> > >>> > >>> > It's based on the standar API for javascript >>> > (https://github.com/ethereum/wiki/wiki/JavaScript-API) . >>> > >>> > It provides interaction with remote contracts, it do as well provides >>> a way >>> > for navigating the architecture objects: blocks, transactions, >>> accounts and >>> > contracts. >>> > >>> > I hope you find it useful. >>> > >>> > Feel free to fill the github issue tracker with anything you find :). >>> > >>> > >>> > I will come to you with some new exciting news about ethereum soon :) >>> > >>> > Santiago. >>> > >>> > >>> > >>> > >>> > >>> > >>> >>> >

Jan. 29, 2018

Re: [Pharo-dev] [ANN] Fog - Ethereum driver

by Rafael Luque

Hi Santiago, I'm currently playing with Dapps on Ethereum using Truffle and web3.js, but it would be great to be able to use Pharo. I've downloaded Fog and started to read the tests and code, but I don't see support for events that is something I need for my current use cases. Maybe I don't know where to look or events are not (yet) supported? In any case, thank you for this contribution. 2017-03-14 9:51 GMT+00:00 Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> : > You are welcome :). We are doing some experiments for looking some > research branches on it. > So, writing some Dapps but not really productive. or not yet. > Any way, we still using solidity as language for the contracts. > > Santiago > > > > On Mon, 13 Mar 2017 at 19:44 Esteban A. Maringolo <emaringolo(a)gmail.com> > wrote: > >> Very Nice! Thank you for building it. >> >> I started a similar project for the Bitcoin blockchain, but then I >> drifted away and never got back to it. >> >> Are you writing DAPPs? >> >> Best regards, >> >> Esteban A. Maringolo >> >> >> 2017-03-13 12:00 GMT-03:00 Santiago Bragagnolo < >> santiagobragagnolo(a)gmail.com>: >> > Hi all. Im happy to announce a pre release of the Fog ethereum driver >> that >> > we develop in the space of an Inria project. >> > >> > It still not complete but is already usable for some experiments and >> simple >> > projects. >> > >> > You can downloadit from >> > https://github.com/sbragagnolo/Fog/ >> > (https://github.com/sbragagnolo/Fog/releases/tag/v0.1.1.1) >> > >> > Dependencies >> > >> > RHash >> > >> > sudo apt-get install rhash >> > >> > Solidity >> > >> > npm install solc >> > >> > Download code >> > >> > Iceberg / Baseline >> > >> > Metacello >> > new >> > baseline: 'Fog'; >> > repository: 'github://sbragagnolo/Fog:v0.1.1.1/src'; >> > load. >> > >> > By hand >> > >> > You may want to use this version for having access to some scripts and >> > contracts samples. >> > >> > git checkout git@github.com:sbragagnolo/Fog.git >> > >> > git checkout v0.1.1.1 >> > >> > Metacello >> > new >> > baseline: 'Fog'; >> > repository: 'filetree:///path/to/git-repository/Fog/src';; >> > load. >> > >> > >> > It's based on the standar API for javascript >> > (https://github.com/ethereum/wiki/wiki/JavaScript-API) . >> > >> > It provides interaction with remote contracts, it do as well provides a >> way >> > for navigating the architecture objects: blocks, transactions, accounts >> and >> > contracts. >> > >> > I hope you find it useful. >> > >> > Feel free to fill the github issue tracker with anything you find :). >> > >> > >> > I will come to you with some new exciting news about ethereum soon :) >> > >> > Santiago. >> > >> > >> > >> > >> > >> > >> >>

Jan. 29, 2018