- Pharo-users - lists.pharo.org

Re: [Pharo-users] Request for Windows test

by HernÃ¡n Morales Durand

Running Windows 8.1 here. Success, no problem at all. Impressive work BTW! Cheers, HernÃ¡n 2018-07-11 7:19 GMT-03:00 Hilaire <hilaire(a)drgeo.eu>: > Hi, > > A Windows user reported to me difficulty to start Dr. Geo. > > Although I had success to run it in a Windows system, I will be glad if > some of you would mind testing it on their windows system, and report to > me success or failure along the used Windows system. > > -> http://www.drgeo.eu/download > > Thanks a lot > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > >

July 12, 2018

Re: [Pharo-users] XML support for pharo

by PBKResearch

Hi Oswall Well, you have located the correct node, which is some kind of XMLNode, so all you need is to access its content. If you browse the class and look at its ÂaccessingÂ protocol, you see the method XMLNode>>#contentString, which will give you, in your test case, Â2014Â as a string. If you want to enter it in the database as a number, asNumber will do thatÂ HTH Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of oswall arguedas Sent: 12 July 2018 18:35 To: 'Any question about pharo is welcome' <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] XML support for pharo Hello Peter, Thanks for your help. The value I get is: <year> 2014 </ year> What I need is to extract the atomic value of the node, which is: 2014 To assign it to variables and create objects. I can not find how to obtain that punctual value 2014. The main purpose is to read many xml files and create smalltak objects with that data, then save them in DB and process the data. _____ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org> > en nombre de PBKResearch <peter(a)pbkresearch.co.uk <mailto:peter@pbkresearch.co.uk> > Enviado: jueves, 12 de julio de 2018 11:17:41 Para: 'Any question about pharo is welcome' Asunto: Re: [Pharo-users] XML support for pharo Hi Oswall What sort of failure did you get? It helps with this sort of thing to execute the code in a playground and inspect the result. One thing you need to know is that the result of xpath is almost always some sort of XMLCollection, even when there is only one element. I would expect the result you want if you write yearmem := (tree xpath: Âcardset/card/yearÂ) first. Note that you should not need a slash at the start; xpath starts searching in the children of the top node. Also you do not need to give every step of the hierarchy; you can always skip levels provided the result specifies a unique route to the node you want. So in this case you can write: yearmem := (tree xpath: Â//yearÂ) first. Hope this helps Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org> > On Behalf Of oswall arguedas Sent: 12 July 2018 17:09 To: pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> Subject: Re: [Pharo-users] XML support for pharo Regards, I practice with the example of the book. I can not read the atomic values of the nodes. For example, with this piece of the example: <cardset> <card> <cardname lang = "en"> Arcane Lighthouse </ cardname> <types> Land </ types> <year> 2014 </ year> To get the atomic value of the node year and assign it to the variable yearmem, I do it like this: yearmem: = tree xpath: '/ cardset / card / year'. But it fails. How do I get the 2014 value? Thank you Oswall _____ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org> > en nombre de oswall arguedas <oswallcr(a)hotmail.com <mailto:oswallcr@hotmail.com> > Enviado: miÃ©rcoles, 11 de julio de 2018 20:17:55 Para: pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> Asunto: Re: [Pharo-users] XML support for pharo Thanks Franz and Monty. I'm working on it, everything is going very well. The feedback when I master it. Oswall _____ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org> > en nombre de monty <monty2(a)programmer.net <mailto:monty2@programmer.net> > Enviado: miÃ©rcoles, 11 de julio de 2018 03:32 Para: pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> Asunto: Re: [Pharo-users] XML support for pharo This is the latest version of the XML/XPath Scraping Booklet: <https://files.pharo.org/books-pdfs/booklet-Scraping/2018-01-07-scrapingbook .pdf> <https://files.pharo.org/books-pdfs/booklet-Scraping/2018-01-07-scrapingbook .pdf> Scraping HTML with XPath - files.pharo.org files.pharo.org 1.6 Alargeexample Â Siblings.Siblingsarechildnodesthathavethesameparent.Thecard-name,types,year, rarity,expansionandcardtextelementsareallsib- ___ montyos.wordpress.com

July 12, 2018

Re: [Pharo-users] XML support for pharo

by oswall arguedas

Hello Peter, Thanks for your help. The value I get is: <year> 2014 </ year> What I need is to extract the atomic value of the node, which is: 2014 To assign it to variables and create objects. I can not find how to obtain that punctual value 2014. The main purpose is to read many xml files and create smalltak objects with that data, then save them in DB and process the data. ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org> en nombre de PBKResearch <peter(a)pbkresearch.co.uk> Enviado: jueves, 12 de julio de 2018 11:17:41 Para: 'Any question about pharo is welcome' Asunto: Re: [Pharo-users] XML support for pharo Hi Oswall What sort of failure did you get? It helps with this sort of thing to execute the code in a playground and inspect the result. One thing you need to know is that the result of xpath is almost always some sort of XMLCollection, even when there is only one element. I would expect the result you want if you write yearmem := (tree xpath: âcardset/card/yearâ) first. Note that you should not need a slash at the start; xpath starts searching in the children of the top node. Also you do not need to give every step of the hierarchy; you can always skip levels provided the result specifies a unique route to the node you want. So in this case you can write: yearmem := (tree xpath: â//yearâ) first. Hope this helps Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of oswall arguedas Sent: 12 July 2018 17:09 To: pharo-users(a)lists.pharo.org Subject: Re: [Pharo-users] XML support for pharo Regards, I practice with the example of the book. I can not read the atomic values of the nodes. For example, with this piece of the example: <cardset> <card> <cardname lang = "en"> Arcane Lighthouse </ cardname> <types> Land </ types> <year> 2014 </ year> To get the atomic value of the node year and assign it to the variable yearmem, I do it like this: yearmem: = tree xpath: '/ cardset / card / year'. But it fails. How do I get the 2014 value? Thank you Oswall ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org<mailto:pharo-users-bounces@lists.pharo.org>> en nombre de oswall arguedas <oswallcr(a)hotmail.com<mailto:oswallcr@hotmail.com>> Enviado: miÃ©rcoles, 11 de julio de 2018 20:17:55 Para: pharo-users(a)lists.pharo.org<mailto:pharo-users@lists.pharo.org> Asunto: Re: [Pharo-users] XML support for pharo Thanks Franz and Monty. I'm working on it, everything is going very well. The feedback when I master it. Oswall ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org<mailto:pharo-users-bounces@lists.pharo.org>> en nombre de monty <monty2(a)programmer.net<mailto:monty2@programmer.net>> Enviado: miÃ©rcoles, 11 de julio de 2018 03:32 Para: pharo-users(a)lists.pharo.org<mailto:pharo-users@lists.pharo.org> Asunto: Re: [Pharo-users] XML support for pharo This is the latest version of the XML/XPath Scraping Booklet: <https://files.pharo.org/books-pdfs/booklet-Scraping/2018-01-07-scrapingbook…> Scraping HTML with XPath - files.pharo.org<https://files.pharo.org/books-pdfs/booklet-Scraping/2018-01-07-scrapingbook…> files.pharo.org 1.6 Alargeexample â¢ Siblings.Siblingsarechildnodesthathavethesameparent.Thecard-name,types,year,rarity,expansionandcardtextelementsareallsib- ___ montyos.wordpress.com

July 12, 2018

Re: [Pharo-users] XML support for pharo

by PBKResearch

Hi Oswall What sort of failure did you get? It helps with this sort of thing to execute the code in a playground and inspect the result. One thing you need to know is that the result of xpath is almost always some sort of XMLCollection, even when there is only one element. I would expect the result you want if you write yearmem := (tree xpath: Âcardset/card/yearÂ) first. Note that you should not need a slash at the start; xpath starts searching in the children of the top node. Also you do not need to give every step of the hierarchy; you can always skip levels provided the result specifies a unique route to the node you want. So in this case you can write: yearmem := (tree xpath: Â//yearÂ) first. Hope this helps Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of oswall arguedas Sent: 12 July 2018 17:09 To: pharo-users(a)lists.pharo.org Subject: Re: [Pharo-users] XML support for pharo Regards, I practice with the example of the book. I can not read the atomic values of the nodes. For example, with this piece of the example: <cardset> <card> <cardname lang = "en"> Arcane Lighthouse </ cardname> <types> Land </ types> <year> 2014 </ year> To get the atomic value of the node year and assign it to the variable yearmem, I do it like this: yearmem: = tree xpath: '/ cardset / card / year'. But it fails. How do I get the 2014 value? Thank you Oswall _____ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org> > en nombre de oswall arguedas <oswallcr(a)hotmail.com <mailto:oswallcr@hotmail.com> > Enviado: miÃ©rcoles, 11 de julio de 2018 20:17:55 Para: pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> Asunto: Re: [Pharo-users] XML support for pharo Thanks Franz and Monty. I'm working on it, everything is going very well. The feedback when I master it. Oswall _____ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org> > en nombre de monty <monty2(a)programmer.net <mailto:monty2@programmer.net> > Enviado: miÃ©rcoles, 11 de julio de 2018 03:32 Para: pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> Asunto: Re: [Pharo-users] XML support for pharo This is the latest version of the XML/XPath Scraping Booklet: <https://files.pharo.org/books-pdfs/booklet-Scraping/2018-01-07-scrapingbook .pdf> <https://files.pharo.org/books-pdfs/booklet-Scraping/2018-01-07-scrapingbook .pdf> Scraping HTML with XPath - files.pharo.org files.pharo.org 1.6 Alargeexample Â Siblings.Siblingsarechildnodesthathavethesameparent.Thecard-name,types,year, rarity,expansionandcardtextelementsareallsib- ___ montyos.wordpress.com

July 12, 2018

Re: [Pharo-users] XML support for pharo

by oswall arguedas

Regards, I practice with the example of the book. I can not read the atomic values of the nodes. For example, with this piece of the example: <cardset> <card> <cardname lang = "en"> Arcane Lighthouse </ cardname> <types> Land </ types> <year> 2014 </ year> To get the atomic value of the node year and assign it to the variable yearmem, I do it like this: yearmem: = tree xpath: '/ cardset / card / year'. But it fails. How do I get the 2014 value? Thank you Oswall ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org> en nombre de oswall arguedas <oswallcr(a)hotmail.com> Enviado: miÃ©rcoles, 11 de julio de 2018 20:17:55 Para: pharo-users(a)lists.pharo.org Asunto: Re: [Pharo-users] XML support for pharo Thanks Franz and Monty. I'm working on it, everything is going very well. The feedback when I master it. Oswall ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org> en nombre de monty <monty2(a)programmer.net> Enviado: miÃ©rcoles, 11 de julio de 2018 03:32 Para: pharo-users(a)lists.pharo.org Asunto: Re: [Pharo-users] XML support for pharo This is the latest version of the XML/XPath Scraping Booklet: <https://files.pharo.org/books-pdfs/booklet-Scraping/2018-01-07-scrapingbook…> Scraping HTML with XPath - files.pharo.org<https://files.pharo.org/books-pdfs/booklet-Scraping/2018-01-07-scrapingbook…> files.pharo.org 1.6 Alargeexample â¢ Siblings.Siblingsarechildnodesthathavethesameparent.Thecard-name,types,year,rarity,expansionandcardtextelementsareallsib- ___ montyos.wordpress.com

July 12, 2018

Pharo TechTalk at 5pm (UTC+2)

by Serge Stinckwich

I will start my techtalk at 5pm (UTC+2) about Pharo&Tensorflow: https://association.pharo.org/event-2973748 on Youtube live: https://www.youtube.com/channel/UCtelfhEzvzvsNjXrGesm2fA Questions on Discord, channel #techtalk: http://discord.gg/Sj2rhxn Thank you. -- Serge Stinckwich UMI UMMISCO 209 (SU/IRD/UY1) "Programs must be written for people to read, and only incidentally for machines to execute."http://www.doesnotunderstand.org/

July 12, 2018

Re: [Pharo-users] Naming parameters - conventions?

by Esteban A. Maringolo

On 11/07/2018 21:21, Sean P. DeNigris wrote: > Paul DeBruicker wrote >> It also seems like a "how much milk do you like in your coffee?" choice >> where the tradeoffs between one vs the other isn't high and the code in >> action will let you know whether you've got it right. > > +1. I also use both. My heuristic is for shorter methods, and methods with > one argument, I tend to lean toward fullNameString and when I need to > differentiate multiple arguments or reference the arg way down in a method > (probably a good sign to refactor) I lean the other way. But I think Paul > said it best that it's probably more a personal style/aesthetic choice than > anything worth spending a lot of energy on. +1 to both. Although a in method like: #setFirstName:lastName: I usually use firstNameString and lastNameString respectively, mostly to not clash with instance variables firstName and lastName. Another criteria is to never name a parameter as aSomething if Something isn't a class (and of course the class of the passed argument). The same applies to #asSomething. And _never_ use anObject as name, unless it really can hold any class of object. -- Esteban A. Maringolo

July 12, 2018

Re: [Pharo-users] Naming parameters - conventions?

by Tim Mackinnon

Having refreshed my memory by rereading that section of the style book - I see the source of my discomfort... I donât find the guidelines on parameters very strong - and I think (like others) I side more with guideline 25 most of the time where itâs sensible (not just for multiple similar parameters). Thus my preference seems to be for semantic typed naming eg: fullNameString, sourceCollection, ageNumber (this one feels weird though), indexingInteger Iâm still a little unsure by using a/an as a prefix when doing semantic typed naming - I think the style book is suggesting that prefix is for typed names (exclusively?). I think the risk of collision with inst var names is low (and guideline 9 and itâs introduction seem to favour semantic naming for inst vars anyway) but I do recall once seeing someone use a prefix âmyâ on all inst vars. That was kind of cute, and seemed to read ok - and sort of encouraged you to add the setter/getter (without my) when needed. But maybe safer to avoid that convention Iâm guessing? Tim Sent from my iPhone > On 12 Jul 2018, at 12:27, Tim Mackinnon <tim(a)testit.works> wrote: > > Sounds like what Iâve been doing is what others do too - I just wasnât sure if my memory had served me well. It was great to be reminded about some of the subtleties though - hadnât thought about a/an stopping inst var collisions. > > I actually have an original copy of that style book, I was working at OTI at the time and knew Suzanne and Dave and we were all given a copy (probably worth a quick skim again) > > Thanks everyone > > Tim > > Sent from my iPhone > >> On 12 Jul 2018, at 11:09, Erik Stel <erik.stel(a)gmail.com> wrote: >> >> In the day, I learned from Smalltalk with Style: >> http://sdmeta.gforge.inria.fr/FreeBooks/WithStyle/SmalltalkWithStyle.pdf >> >> On PDF-page 13 naming starts. On PDF-page 29 parameter names are explained >> (but refers back to typed names for example). Naming ends at PDF-page 35. So >> quite elaborate explanation of naming ;-). >> >> In practice I also mix typed names (aCollection), semantic names (addresses) >> and a combination (anAddressCollection). I prefer the combination except for >> trivial situations or when the (class and) method name provide(s) enough >> context (name: aString). This later might in itself be less trivial if the >> context get broader than class and method (name). >> >> @Tim, the book might be useful for more than just naming since it covers >> quite some ground. >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

July 12, 2018

Re: [Pharo-users] Naming parameters - conventions?

by Tim Mackinnon

Sounds like what Iâve been doing is what others do too - I just wasnât sure if my memory had served me well. It was great to be reminded about some of the subtleties though - hadnât thought about a/an stopping inst var collisions. I actually have an original copy of that style book, I was working at OTI at the time and knew Suzanne and Dave and we were all given a copy (probably worth a quick skim again) Thanks everyone Tim Sent from my iPhone > On 12 Jul 2018, at 11:09, Erik Stel <erik.stel(a)gmail.com> wrote: > > In the day, I learned from Smalltalk with Style: > http://sdmeta.gforge.inria.fr/FreeBooks/WithStyle/SmalltalkWithStyle.pdf > > On PDF-page 13 naming starts. On PDF-page 29 parameter names are explained > (but refers back to typed names for example). Naming ends at PDF-page 35. So > quite elaborate explanation of naming ;-). > > In practice I also mix typed names (aCollection), semantic names (addresses) > and a combination (anAddressCollection). I prefer the combination except for > trivial situations or when the (class and) method name provide(s) enough > context (name: aString). This later might in itself be less trivial if the > context get broader than class and method (name). > > @Tim, the book might be useful for more than just naming since it covers > quite some ground. > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

July 12, 2018

Re: [Pharo-users] Naming parameters - conventions?

by Erik Stel

In the day, I learned from Smalltalk with Style: http://sdmeta.gforge.inria.fr/FreeBooks/WithStyle/SmalltalkWithStyle.pdf On PDF-page 13 naming starts. On PDF-page 29 parameter names are explained (but refers back to typed names for example). Naming ends at PDF-page 35. So quite elaborate explanation of naming ;-). In practice I also mix typed names (aCollection), semantic names (addresses) and a combination (anAddressCollection). I prefer the combination except for trivial situations or when the (class and) method name provide(s) enough context (name: aString). This later might in itself be less trivial if the context get broader than class and method (name). @Tim, the book might be useful for more than just naming since it covers quite some ground. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

July 12, 2018