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

Re: [Pharo-users] [Pharo-dev] TechTalk Dates for the rest of 2017

by Serge Stinckwich

On Tue, Aug 22, 2017 at 8:31 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 21 Aug 2017, at 19:08, serge.stinckwich(a)gmail.com wrote: > > > > I'm not sure Pharo tech talk is the good place but would love to see > such a presentation. > > > Why not? I am sure Alex will have some code in there.. " programming, from > scratch, a small artificial intelligenceâ > if done with Pharo would be a very nice thing todo for the tech talk. > > âI thought that Pharo tech talk was only for core Pharo technologies. âBut Alex proposal is really great. -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Aug. 24, 2017

Re: [Pharo-users] [Pillar] Installed the Pillar document preparation system into 6.1, how do I start using it?

by H. Hirzel

Fine, thank you, Stephane. I have Pillar now installed in 6.1. And a PetitParser version which supports YAML, but in a different 6.1 image. One issue is that I can have both in the same image - 1) Pillar loaded through the catalog 2) a good recent PetitParser version See also my email to Tudor Girba this morning --Hannes On 8/22/17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Yes we need input (but most importantly time). I will allocate time > because Pillar is important for me. > > On Fri, Aug 18, 2017 at 10:18 PM, Cyril Ferlicot > <cyril.ferlicot(a)gmail.com> wrote: >> >> On ven. 18 aoÃ»t 2017 at 22:09, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>> >>> Exactly. >>> >>> Section 7 of >>> >>> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >>> >>> has an example >>> >>> >>> | wiki | >>> wiki := '!My Document'. >>> PRPillarParser parse: wiki >>> >>> >>> Or >>> >>> PRPillarParser parse: (FileSystem workingDirectory / 'foo.pillar') >>> readStream >>> >>> >>> and then >>> >>> >>> PRHTMLWriter write: document >>> >>> >>> This put together gives >>> >>> PRHTMLWriter write: ( >>> PRPillarParser parse: (FileSystem workingDirectory / >>> 'welcome.pillar') >>> ) >>> >>> >>> If I inspect the result of this expression I get the HTML string. >>> >>> Thank you Cyril. This is what I was looking for. >>> >>> --Hannes >> >> >> >> Happy to see it still works :) >> >> I know there was work on Pillar after I wrote this. Maybe there is some >> functionalities that will need more than those simple examples. By I am >> not >> sure and I know that Stephane want to simplify it further. >> -- >> Cyril Ferlicot >> https://ferlicot.fr >> >> http://www.synectique.eu >> 2 rue Jacques PrÃ©vert 01, >> 59650 Villeneuve d'ascq France > >

Aug. 24, 2017

PetitParser catalog entry for Pharo 6.0/6.1? (Re: YAML parser (2017))

by H. Hirzel

Hello Doru Stephane Ducasse pointed out that you maintain PetitParser [1] The Pharo 6 catalog does not contain an entry for the PetitParser package. I installed in manually in order to have a good version of a YAML parser (all tests green). This is what I did: a) I loaded ConfigurationOfPetitParser-TudorGirba.80 through the Monticello Browser (not the catalog) into Pharo 6 b) Then I executed ConfigurationOfPetitParser load c) I manually loaded Name: PetitYAML-PhilippeBack.11 Author: PhilippeBack Time: 29 May 2017, 12:53:55.994195 pm UUID: d7658233-112c-754c-81a7-d60139bb9549 My need: I'd like to have a Pillar installation in 6.0 together with a PetitParser version which supports the YAML parser version with the latest fixes by Philippe Back. At the moment I have Pillar and the manually loaded PetitParser in two different Pharo 6.1 images. Thank you in advance Regards Hannes On 8/22/17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi Hannes > > you should report this to doru. > > Stef > > On Sat, Aug 19, 2017 at 8:36 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> On 8/19/17, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >>> On Sat, Aug 19, 2017 at 02:45:28PM +0200, H. Hirzel wrote: >>>> Peter, thanks for the confirmation that in your installation of the >>>> PetitYAML grammar all tests are green. >>>> >>>> I wonder how you did it. >>>

Aug. 24, 2017

Re: [Pharo-users] [Pharo-dev] TechTalk Dates for the rest of 2017

by Marcus Denker

Yes! https://association.pharo.org/event-2642664 > On 23 Aug 2017, at 08:39, Norbert Hartl <norbert(a)hartl.name> wrote: > > I would be in, too. It'll be on 17th of october fix? > > Norbert > >> Am 21.08.2017 um 18:38 schrieb Alexandre Bergel <alexandre.bergel(a)me.com>: >> >> Hi! >> >> I am currently giving a lecture on Neural Networks and Genetic Algorithm/Programming. >> Maybe I could turn this into an express 2 hours mini-lecture. Would this work? >> >> Anyone is interesting in programming, from scratch, a small artificial intelligence? >> >> Cheers, >> Alexandre >> >> >>> On Aug 21, 2017, at 10:32 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> Hi, >>> >>> We have added dates for tech talk discussions / Demos for the rest of 2017: >>> https://association.pharo.org/events >>> >>> We need to find some topics. In the past we had often formal âtalksâ or demos about >>> a topic with discussion afterwards, but a more relaxed form of just an open discussion >>> about a topic is possible, too, >>> >>> If you like to lead one of the dates (all but the November dates are available still), this >>> would be great. >>> >>> If a date does find a topic, we keep it as an open discussion round. >>> >>> Marcus >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >

Aug. 24, 2017

Re: [Pharo-users] Brea wiki software

by H. Hirzel

Offray Thanks for the two answers and in particular. Fossil is as a data store and version control system is a good solution. But I have to use a JSON data store. So my interest is that I can hook that up to Brea. (or as a first step just keep the objects in the image -- image persistence) Next week is fine. Regards Hannes On 8/24/17, Offray <offray.luna(a)mutabit.com> wrote: > Meanwhile, you can check at [1], a Grafoscopio notebook where I documented > Brea and the problem is trying to solve. > > [1] http://mutabit.com/repos.fossil/gig/dir?ci=tip > > Cheers, > > Offray > > El 23 de agosto de 2017 20:15:38 GMT-05:00, Offray <offray.luna(a)mutabit.com> > escribiÃ³: >>Hi Hannes, >> >>I will improve docs and test, but for the moment I'll be away of my >>computer at least until Friday. Image persistance is not implemented. >> >>Cheers, >> >>Offray >> >>El 23 de agosto de 2017 13:44:46 GMT-05:00, "H. Hirzel" >><hannes.hirzel(a)gmail.com> escribiÃ³: >>>On 8/23/17, Offray <offray.luna(a)mutabit.com> wrote: >>>> Hi, >>>> >>>> On the Teapot + Mustache integration, Hannes, you may want to see my >>>early >>>> prototype: >>>> >>>> http://smalltalkhub.com/#!/~Offray/Brea >>>> >>>> At some point, it will contain distributed wiki, backed by Fossil, >>>now that >>>> we're thinking in empower community driven wiki like documentation. >>>> >>>> Offray >>> >>> >>>Hi Offray >>> >>>I found Name: Brea-OffrayLuna.8 >>>Author: OffrayLuna >>>Time: 1 June 2017, 4:18:20.860411 pm >>> >>>There is no test to show me how to use it and I none of the class >>>comments of the 4 classes gives enough clues. >>> >>> >>>Interesting method so far >>> >>>routes >>> "I define how the website behaves accordingly to particular routes." >>> self server >>> serveStatic: 'demo' from: '/opt/gig/'; >>> GET: 'members/test' -> [ :req | BreaMember new renderTestUserAsHtml >>>]; >>> GET: 'members/add' -> [ :req | BreaMember new htmlInput ]; >>> POST: 'members/summit' -> [ :req | self processNewMember: req ] >>> >>> >>>May I ask you to give a few hints how to start it? >>>Is it possible to use it without Fossil, just with image persistence? >>> >>>Regards >>>Hannes >> >>-- >>Enviado desde mi dispositivo Android con K-9 Mail. Por favor, disculpa >>mi brevedad. > > -- > Enviado desde mi dispositivo Android con K-9 Mail. Por favor, disculpa mi > brevedad.

Aug. 24, 2017

Re: [Pharo-users] Where do I find a Pillar syntax summary?

by H. Hirzel

Alistair, Thank you for the link to the Pillar syntax summary http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet and the confirmation that the constructs there work in Pharo 6 & 7 for basic cases. This is fine for me at the moment. Stephan D Thanks for being ready to check the full feature support in Pillar. A suggestion: A new style sheet could come as well together with a test document (with version indication included) for the Pillar parser. Then it is straightforward to determine if a particular Pillar installation supports a particular Pillar markup version. The Pillar-Tests-PetitPillar package tests individual features but not all in one go. If we have a test case which tests all features in one go it has a triple function: 1) It is a syntax summary of all features. 2) It serves as a living documentation. 3) It helps to determine if a particular pillar installation in an image supports a particular Pillar version. --Hannes On 8/23/17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > +Handling all the cases: summing a die/die handle with a die/die > handle > .>file://figures/DieDoubleDispatchFull.pdf|width=70|label=figDieDoubleDispatchFull+ > > See Figure *@figDieDoubleDispatchFull* for internal ref is missing. > > Two Column is missing. I do not know it works in Latex. > > I will try to create one a new style sheet. > > > On Wed, Aug 23, 2017 at 9:46 PM, Alistair Grant <akgrant0710(a)gmail.com> > wrote: >> On Wed, Aug 23, 2017 at 09:11:47PM +0200, H. Hirzel wrote: >>> Thanks, it is useful. >>> Date is 24 June 2014. >>> Not sure if it is the latest version for what I have now in Pharo 6. >>> >>> --Hannes >> >> True, but it only covers the basic text mark-up and I don't think that >> has changed recently. Anyway, I haven't found anything wrong with it in >> Pharo 6 & 7 (admittedly, with only basic pillar usage). >> >> Cheers, >> Alistair >> >> >>> On 8/23/17, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>> > How about: >>> > >>> > http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet >>> > >>> > Cheers, >>> > Alistair >> > >

Aug. 24, 2017

Re: [Pharo-users] Glorp: Is there some way to do insert-or-update?

by herby＠mailbox.sk

On August 24, 2017 7:26:00 AM GMT+02:00, "jtuchel(a)objektfabrik.de" <jtuchel(a)objektfabrik.de> wrote: >Am 23.08.17 um 11:08 schrieb Herby VojÄÃk: >> jtuchel wrote: >>> Herby, >>> >>> as Esteban already said, UPSERT doesn't make any sense in an ORM. It >> >> I don't know... I just create new object (with same "primary key") >and >> register it (yes, I know I get an error - maybe I should be able to >> set the policy to "overwrite" and it would makes sense; or not?). >> >What I mean is that for an ORM, an object can only be new or old. It >can >only be sure an object is Old if either >a) The ORM itself has loaded it from the database >b) the user forcibly tells it that an object is old > >There is no maybe in an ORM's world, because the consequences of maybe >can make the whole thing brittle. Maybe would make optimistic locking >and other mechanisms obsolete. > >>> either knows the object as one that has been read in this session or >>> not. If not, it is new and needs to be inserted. >>> >>> You could, of course, try and see what happens if you let Glorp's >insert >>> operation always issue an UPSERT. This is probably very easy to do >and >>> at first sight there isn't too much I could think of that could go >wrong >>> with it. >>> >>> But I guess including a check for existence of an object as Esteban >>> suggests isn't too bad from the performance and "safety" POV. not >sure I >>> understand how a Dictionary Mapping could help here.... >> >> Similarly to what was posted above: I can simply at:put: and I don't >> care if I created the new key-value pair or overwritten the old value > >> (in cases where simply putting new object under a key is feasible, >> which is in this case). > >Still don't understand. An object has its attributes that are used as >its identification for the corresponding row in the DB (the primary key > >thereof). That is also true for objects that are the value of an >Asscoiation. The Smalltalk Dictionary is translated to something that >holds references to objects by their primary key (Haven't used Dict Yes, this cannot be avoided. But in cases where I want to write over the item, I am not forced to choose between two different approaches and just use at:put:. So it IMO helps from client code PoV. >mappings yet, but I'd guess it's a link table). So I don't see how that > >would solve your problem an object's primary key is either known in a >session or it isn't. If it is, the object is known to have existed in >the database at read time, if not, it's assumed to be new. > >If it is assumed to be new, the DB provides a mechanism for avoiding >damage by its Uniqueness constraint and the ORM can only rely on that. > > >Joachim

Aug. 24, 2017

Re: [Pharo-users] new chapter on double dispatch for new book :)

by herby＠mailbox.sk

On August 23, 2017 10:09:02 PM GMT+02:00, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >On Wed, Aug 23, 2017 at 9:20 PM, Herby VojÄÃk <herby(a)mailbox.sk> wrote: >> Maybe in general sumWithFoo: => addSelfToFoo: to make clues clearer. > >I see now it should be more >addSelfWithFoo: or sumSelfWithFoo: because we do not modify the argument. I argue you should preserve original order of operands, otherwise there's a confusion that dd is only usable wjen you want to switch them. So with xWithY: form, it should addFooWithSelf: / sumFooWithSelf:. Herby > >Stef

Aug. 24, 2017

Re: [Pharo-users] Glorp: Is there some way to do insert-or-update?

by jtuchel＠objektfabrik.de

Am 23.08.17 um 11:08 schrieb Herby VojÄÃk: > jtuchel wrote: >> Herby, >> >> as Esteban already said, UPSERT doesn't make any sense in an ORM. It > > I don't know... I just create new object (with same "primary key") and > register it (yes, I know I get an error - maybe I should be able to > set the policy to "overwrite" and it would makes sense; or not?). > What I mean is that for an ORM, an object can only be new or old. It can only be sure an object is Old if either a) The ORM itself has loaded it from the database b) the user forcibly tells it that an object is old There is no maybe in an ORM's world, because the consequences of maybe can make the whole thing brittle. Maybe would make optimistic locking and other mechanisms obsolete. >> either knows the object as one that has been read in this session or >> not. If not, it is new and needs to be inserted. >> >> You could, of course, try and see what happens if you let Glorp's insert >> operation always issue an UPSERT. This is probably very easy to do and >> at first sight there isn't too much I could think of that could go wrong >> with it. >> >> But I guess including a check for existence of an object as Esteban >> suggests isn't too bad from the performance and "safety" POV. not sure I >> understand how a Dictionary Mapping could help here.... > > Similarly to what was posted above: I can simply at:put: and I don't > care if I created the new key-value pair or overwritten the old value > (in cases where simply putting new object under a key is feasible, > which is in this case). Still don't understand. An object has its attributes that are used as its identification for the corresponding row in the DB (the primary key thereof). That is also true for objects that are the value of an Asscoiation. The Smalltalk Dictionary is translated to something that holds references to objects by their primary key (Haven't used Dict mappings yet, but I'd guess it's a link table). So I don't see how that would solve your problem an object's primary key is either known in a session or it isn't. If it is, the object is known to have existed in the database at read time, if not, it's assumed to be new. If it is assumed to be new, the DB provides a mechanism for avoiding damage by its Uniqueness constraint and the ORM can only rely on that. Joachim

Aug. 24, 2017

Re: [Pharo-users] Brea wiki software

by Offray

Meanwhile, you can check at [1], a Grafoscopio notebook where I documented Brea and the problem is trying to solve. [1] http://mutabit.com/repos.fossil/gig/dir?ci=tip Cheers, Offray El 23 de agosto de 2017 20:15:38 GMT-05:00, Offray <offray.luna(a)mutabit.com> escribiÃ³: >Hi Hannes, > >I will improve docs and test, but for the moment I'll be away of my >computer at least until Friday. Image persistance is not implemented. > >Cheers, > >Offray > >El 23 de agosto de 2017 13:44:46 GMT-05:00, "H. Hirzel" ><hannes.hirzel(a)gmail.com> escribiÃ³: >>On 8/23/17, Offray <offray.luna(a)mutabit.com> wrote: >>> Hi, >>> >>> On the Teapot + Mustache integration, Hannes, you may want to see my >>early >>> prototype: >>> >>> http://smalltalkhub.com/#!/~Offray/Brea >>> >>> At some point, it will contain distributed wiki, backed by Fossil, >>now that >>> we're thinking in empower community driven wiki like documentation. >>> >>> Offray >> >> >>Hi Offray >> >>I found Name: Brea-OffrayLuna.8 >>Author: OffrayLuna >>Time: 1 June 2017, 4:18:20.860411 pm >> >>There is no test to show me how to use it and I none of the class >>comments of the 4 classes gives enough clues. >> >> >>Interesting method so far >> >>routes >> "I define how the website behaves accordingly to particular routes." >> self server >> serveStatic: 'demo' from: '/opt/gig/'; >> GET: 'members/test' -> [ :req | BreaMember new renderTestUserAsHtml >>]; >> GET: 'members/add' -> [ :req | BreaMember new htmlInput ]; >> POST: 'members/summit' -> [ :req | self processNewMember: req ] >> >> >>May I ask you to give a few hints how to start it? >>Is it possible to use it without Fossil, just with image persistence? >> >>Regards >>Hannes > >-- >Enviado desde mi dispositivo Android con K-9 Mail. Por favor, disculpa >mi brevedad. -- Enviado desde mi dispositivo Android con K-9 Mail. Por favor, disculpa mi brevedad.

Aug. 24, 2017