- Pharo-users - lists.pharo.org

Re: [Pharo-users] Commit to Monticello from the code browser

by stepharo

Hi federico We spent 8 months on this mooc so I think that there is a real value in it. All the people that followed it told me that it is great and the resources are freely accessible. Now I cannot watch it for others :) You should have a look at the [Live] videos [Live] Diffing and Merging in Pharo [Live] Understanding Images and Changes Files I checked and you see it in that one: http://rmod-pharo-mooc.lille.inria.fr/MOOC/Videos/W1/C019-W1S-Videos-Redo-C… Stef Le 2/9/16 Ã 22:14, Federico.Balaguer a Ã©crit : > Hello, > > > >From the Monticello chapter I had the impression that using the > package-cache as -default- repository would have the same effect on the > tools. > > After I created a file repository for my package (different from the > package-cache) and made a change to a method on that package I saw the > Commit menu option again in the context menu of the package. > > I didn't watch the videos and after you mention MOOC I didn't find the video > you mention (http://files.pharo.org/mooc/) Would you mind point me to the > right video. I am also trying to learn about Versionner. > > Thanks! Federico > > > > > -- > View this message in context: http://forum.world.st/Commit-to-Monticello-from-the-code-browser-tp4913844p… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Sept. 3, 2016

Re: [Pharo-users] Coding XPath as Smalltalk

by Tudor Girba

Hi, This is the latest stable version: spec name: 'XPath'; className: #ConfigurationOfXPath; versionString: #stable; repository: 'http://www.smalltalkhub.com/mc/PharoExtras/XPath/main'. Doru > On Sep 3, 2016, at 8:02 AM, stepharo <stepharo(a)free.fr> wrote: > > Hi monty > > In which repository this maintained version is? > > PharoExtras? > > Is it the entry in the catalog? > > Stef > > > > Le 3/9/16 Ã 07:54, monty a Ã©crit : >> Peter, you're using an ancient version with bugs that were fixed last fall. The newest version has more tests and correct behavior (checked against a reference implementation). Just download a new Moose image and you'll get it, along with an up to date XMLParser. (But if you insist on upgrading in your old image, run "XPath initialize" after) >> >> The binary syntax (there are keyword equivalents now) officially only supports XPath axis selectors like #/ and #// that take node test arguments where the node tests can be name tests like 'name,' '*', 'prefix:*' or type tests like 'text()', 'comment()', 'element(name)'. >> >> Filters aren't officially supported with that syntax, but you can always use select: on the result. ?? was removed, but I might add it back as shorthand. Filters are implemented differently now. >> >>> From: PBKResearch <peter(a)pbkresearch.co.uk> >>> To: pharo-users(a)lists.pharo.org >>> Subject: [Pharo-users] Coding XPath as Smalltalk >>> >>> Hello >>> I am using XPath as a way of dissecting web pages, especially from Wiktionary. Generally I get good results, but I could get useful extra flexibility by using the binary Smalltalk operators to represent XPath, as mentioned at the end of the class comment for XPath. However, the description there is very terse, and I am having difficulty seeing how to include more complex expressions, especially attribute tests. I have put some of my XPath expressions through the XPath compiler and looked at the output, and out of that I have found expressions which work but look very clumsy. As an example, I have used the fragment: >>> document xPath: '//div[@id=''catlinks'']//li//text()' >>> and found that an equivalent is: >>> document //'div' ?? [:node :x :y|(node attributeAt: 'id') = 'catlinks']//'li'//[:n| n isStringNode]]. >>> (I had to put two dummy arguments in the three-argument block to get it to work.) >>> Is there a more extensive explanation of the use of these binary operators? If not, could some kind person show me the most concise translation of the sample XPath above, to give me a start in working out more complex cases? >>> Many thanks for any help. >>> Peter Kenny >> > > -- www.tudorgirba.com www.feenk.com "What we can governs what we wish."

Sept. 3, 2016

Re: [Pharo-users] Coding XPath as Smalltalk

by HernÃ¡n Morales Durand

Thank you Monty for the clarification. I should say the original XPath package was written by Phil Hargett and I just added a couple of methods. Glad you rewrote the lib! Cheers, HernÃ¡n 2016-09-03 3:01 GMT-03:00 monty <monty2(a)programmer.net>: > > Hernan, the PharoExtras/XPath repo has a major rewrite of your package to > support all of XPath 1.0 + XPath 2.0 extensions like the element() and > attribute() type tests and namespace literals in name tests like > '{namespaceURI}localName'. A rewrite was needed because the old lib only > implemented a small subset of the spec and would infinite loop on some > inputs. > > *Sent:* Thursday, September 01, 2016 at 3:56 PM > *From:* "HernÃ¡n Morales Durand" <hernan.morales(a)gmail.com> > > *To:* "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> > *Subject:* Re: [Pharo-users] Coding XPath as Smalltalk > > > 2016-09-01 16:51 GMT-03:00 PBKResearch <peter(a)pbkresearch.co.uk>: >> >> Hi Hernan >> >> >> >> I donât understand your first question â I canât see a connection between >> SPARQL and what I am doing. >> >> >> > > You could get the Wikitionary data by querying a SPARQL endpoint > http://wiktionary.dbpedia.org/sparql instead of scrapping web pages > (which seems more difficult) > > >> >> >> I downloaded XPath from http://smalltalkhub.com/mc/PharoExtras/XPath/. >> However, I am probably using a somewhat out of date version; I downloaded >> it about a year ago. >> >> >> > > I don't know about that version. I copied an old version from SqueakSource > (with permission) and updated from time to time, but there is no much. > There is also a XPath2 repository which you may try. > > HernÃ¡n > > >> >> >> Peter >> >> >> >> *From:* Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] *On >> Behalf Of *HernÃ¡n Morales Durand >> *Sent:* 01 September 2016 18:54 >> *To:* Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >> *Subject:* Re: [Pharo-users] Coding XPath as Smalltalk >> >> >> >> Hi Peter, >> >> >> >> 2016-09-01 10:26 GMT-03:00 PBKResearch <peter(a)pbkresearch.co.uk>: >> >> Hello >> >> >> >> I am using XPath as a way of dissecting web pages, especially from >> Wiktionary. >> >> >> >> Any specific reason to not use the SPARQL endpoint? >> >> >> >> >> Generally I get good results, but I could get useful extra flexibility by >> using the binary Smalltalk operators to represent XPath, as mentioned at >> the end of the class comment for XPath. However, the description there is >> very terse, and I am having difficulty seeing how to include more complex >> expressions, especially attribute tests. >> >> >> >> Which XPath version are you using? How did you installed it? >> >> >> >> >> I have put some of my XPath expressions through the XPath compiler and >> looked at the output, and out of that I have found expressions which work >> but look very clumsy. As an example, I have used the fragment: >> >> >> >> document xPath: '//div[@id=''catlinks'']//li//text()' >> >> >> >> and found that an equivalent is: >> >> >> >> document //'div' ?? [:node :x :y|(node attributeAt: 'id') = >> 'catlinks']//'li'//[:n| n isStringNode]]. >> >> (I had to put two dummy arguments in the three-argument block to get it >> to work.) >> >> >> >> Is there a more extensive explanation of the use of these binary >> operators? If not, could some kind person show me the most concise >> translation of the sample XPath above, to give me a start in working out >> more complex cases? >> >> >> >> Many thanks for any help. >> >> >> >> Peter Kenny >> >> >> >> >> >

Sept. 3, 2016

Re: [Pharo-users] Comparing floats

by stepharo

would be nice to extend Sunit with that Le 3/9/16 Ã 00:21, Yuriy Tymchuk a Ã©crit : > how about having assert:closeTo: ? > >> On 02 Sep 2016, at 21:09, Henrik Nergaard <henrik.nergaard(a)uia.no> wrote: >> >> You could implement a custom assert in ConverterTest to do the comparison, something like >> >> assert: aNumber withPrecision: precision equals: otherNumber >> >> self >> assert: (aNumber round: precision) >> equals: otherNumber >> >> assert: aNumber closeTo: otherNumber >> >> assert: aNumber withPrecision: self defaultPrecision equals: otherNumber >> >> defaultPrecision >> ^ 2 >> >> >> Best regards, >> Henrik >> >> -----Original Message----- >> From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of stepharo >> Sent: Friday, September 2, 2016 8:41 PM >> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >> Subject: [Pharo-users] Comparing floats >> >> Hi >> >> I'm writing a simple converter between Celcius and Farhenheit as an example to start programming. >> >> >> Converter >> convertFarhenheit: anInteger >> ^ ((anInteger - 32) / 1.8) >> >> ConverterTest >> testFToC >> >> | converter | >> converter := TemperatureConverter new. >> self assert: ((converter convertFarhenheit: 86) = 30.0). >> self assert: ((converter convertFarhenheit: 50) = 10). >> self assert: ((converter convertFarhenheit: 52) = 11.11111111111111) >> >> >> My problem is with ((converter convertFarhenheit: 52) = 11.11111111111111) >> >> I do not want to have such ugly test. >> >> I tried either to control the output >> >> Converter >> convertFarhenheit: anInteger >> ^ ((anInteger - 32) / 1.8) roundDownTo: 0.1 >> >> Not a good idea >> >> Or to compare with closeTo: >> >> self assert: ((converter convertFarhenheit: 52) closeTo: 11.11) >> >> does not work because we cannot set the precision. >> >> So at ESUG I briefly discuss that with Nicolas Cellier and I need help. >> >> Should I introduce in pharo closeTo:interval: >> >> Any suggestions that a newby can understand is welcome. >> >> >> Stef >> >> >> > >

Sept. 3, 2016

Re: [Pharo-users] Comparing floats

by stepharo

Thanks I will try that. Stef Le 2/9/16 Ã 21:09, Henrik Nergaard a Ã©crit : > You could implement a custom assert in ConverterTest to do the comparison, something like > > assert: aNumber withPrecision: precision equals: otherNumber > > self > assert: (aNumber round: precision) > equals: otherNumber > > assert: aNumber closeTo: otherNumber > > assert: aNumber withPrecision: self defaultPrecision equals: otherNumber > > defaultPrecision > ^ 2 > > > Best regards, > Henrik > > -----Original Message----- > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of stepharo > Sent: Friday, September 2, 2016 8:41 PM > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: [Pharo-users] Comparing floats > > Hi > > I'm writing a simple converter between Celcius and Farhenheit as an example to start programming. > > > Converter >> convertFarhenheit: anInteger > ^ ((anInteger - 32) / 1.8) > > ConverterTest >> testFToC > > | converter | > converter := TemperatureConverter new. > self assert: ((converter convertFarhenheit: 86) = 30.0). > self assert: ((converter convertFarhenheit: 50) = 10). > self assert: ((converter convertFarhenheit: 52) = 11.11111111111111) > > > My problem is with ((converter convertFarhenheit: 52) = 11.11111111111111) > > I do not want to have such ugly test. > > I tried either to control the output > > Converter >> convertFarhenheit: anInteger > ^ ((anInteger - 32) / 1.8) roundDownTo: 0.1 > > Not a good idea > > Or to compare with closeTo: > > self assert: ((converter convertFarhenheit: 52) closeTo: 11.11) > > does not work because we cannot set the precision. > > So at ESUG I briefly discuss that with Nicolas Cellier and I need help. > > Should I introduce in pharo closeTo:interval: > > Any suggestions that a newby can understand is welcome. > > > Stef > > >

Sept. 3, 2016

Re: [Pharo-users] Coding XPath as Smalltalk

by stepharo

Hi monty In which repository this maintained version is? PharoExtras? Is it the entry in the catalog? Stef Le 3/9/16 Ã 07:54, monty a Ã©crit : > Peter, you're using an ancient version with bugs that were fixed last fall. The newest version has more tests and correct behavior (checked against a reference implementation). Just download a new Moose image and you'll get it, along with an up to date XMLParser. (But if you insist on upgrading in your old image, run "XPath initialize" after) > > The binary syntax (there are keyword equivalents now) officially only supports XPath axis selectors like #/ and #// that take node test arguments where the node tests can be name tests like 'name,' '*', 'prefix:*' or type tests like 'text()', 'comment()', 'element(name)'. > > Filters aren't officially supported with that syntax, but you can always use select: on the result. ?? was removed, but I might add it back as shorthand. Filters are implemented differently now. > >> From: PBKResearch <peter(a)pbkresearch.co.uk> >> To: pharo-users(a)lists.pharo.org >> Subject: [Pharo-users] Coding XPath as Smalltalk >> >> Hello >> >> I am using XPath as a way of dissecting web pages, especially from Wiktionary. Generally I get good results, but I could get useful extra flexibility by using the binary Smalltalk operators to represent XPath, as mentioned at the end of the class comment for XPath. However, the description there is very terse, and I am having difficulty seeing how to include more complex expressions, especially attribute tests. I have put some of my XPath expressions through the XPath compiler and looked at the output, and out of that I have found expressions which work but look very clumsy. As an example, I have used the fragment: >> >> document xPath: '//div[@id=''catlinks'']//li//text()' >> >> and found that an equivalent is: >> >> document //'div' ?? [:node :x :y|(node attributeAt: 'id') = 'catlinks']//'li'//[:n| n isStringNode]]. >> (I had to put two dummy arguments in the three-argument block to get it to work.) >> >> Is there a more extensive explanation of the use of these binary operators? If not, could some kind person show me the most concise translation of the sample XPath above, to give me a start in working out more complex cases? >> >> Many thanks for any help. >> >> Peter Kenny >

Sept. 3, 2016

Re: [Pharo-users] Coding XPath as Smalltalk

by monty

Sept. 3, 2016

Re: [Pharo-users] Coding XPath as Smalltalk

by monty

Peter, you're using an ancient version with bugs that were fixed last fall. The newest version has more tests and correct behavior (checked against a reference implementation). Just download a new Moose image and you'll get it, along with an up to date XMLParser. (But if you insist on upgrading in your old image, run "XPath initialize" after) The binary syntax (there are keyword equivalents now) officially only supports XPath axis selectors like #/ and #// that take node test arguments where the node tests can be name tests like 'name,' '*', 'prefix:*' or type tests like 'text()', 'comment()', 'element(name)'. Filters aren't officially supported with that syntax, but you can always use select: on the result. ?? was removed, but I might add it back as shorthand. Filters are implemented differently now. > From: PBKResearch <peter(a)pbkresearch.co.uk> > To: pharo-users(a)lists.pharo.org > Subject: [Pharo-users] Coding XPath as Smalltalk > > Hello > > I am using XPath as a way of dissecting web pages, especially from Wiktionary. Generally I get good results, but I could get useful extra flexibility by using the binary Smalltalk operators to represent XPath, as mentioned at the end of the class comment for XPath. However, the description there is very terse, and I am having difficulty seeing how to include more complex expressions, especially attribute tests. I have put some of my XPath expressions through the XPath compiler and looked at the output, and out of that I have found expressions which work but look very clumsy. As an example, I have used the fragment: > > document xPath: '//div[@id=''catlinks'']//li//text()' > > and found that an equivalent is: > > document //'div' ?? [:node :x :y|(node attributeAt: 'id') = 'catlinks']//'li'//[:n| n isStringNode]]. > (I had to put two dummy arguments in the three-argument block to get it to work.) > > Is there a more extensive explanation of the use of these binary operators? If not, could some kind person show me the most concise translation of the sample XPath above, to give me a start in working out more complex cases? > > Many thanks for any help. > > Peter Kenny

Sept. 3, 2016

Re: [Pharo-users] Comparing floats

by Yuriy Tymchuk

how about having assert:closeTo: ? > On 02 Sep 2016, at 21:09, Henrik Nergaard <henrik.nergaard(a)uia.no> wrote: > > You could implement a custom assert in ConverterTest to do the comparison, something like > > assert: aNumber withPrecision: precision equals: otherNumber > > self > assert: (aNumber round: precision) > equals: otherNumber > > assert: aNumber closeTo: otherNumber > > assert: aNumber withPrecision: self defaultPrecision equals: otherNumber > > defaultPrecision > ^ 2 > > > Best regards, > Henrik > > -----Original Message----- > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of stepharo > Sent: Friday, September 2, 2016 8:41 PM > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: [Pharo-users] Comparing floats > > Hi > > I'm writing a simple converter between Celcius and Farhenheit as an example to start programming. > > > Converter >> convertFarhenheit: anInteger > ^ ((anInteger - 32) / 1.8) > > ConverterTest >> testFToC > > | converter | > converter := TemperatureConverter new. > self assert: ((converter convertFarhenheit: 86) = 30.0). > self assert: ((converter convertFarhenheit: 50) = 10). > self assert: ((converter convertFarhenheit: 52) = 11.11111111111111) > > > My problem is with ((converter convertFarhenheit: 52) = 11.11111111111111) > > I do not want to have such ugly test. > > I tried either to control the output > > Converter >> convertFarhenheit: anInteger > ^ ((anInteger - 32) / 1.8) roundDownTo: 0.1 > > Not a good idea > > Or to compare with closeTo: > > self assert: ((converter convertFarhenheit: 52) closeTo: 11.11) > > does not work because we cannot set the precision. > > So at ESUG I briefly discuss that with Nicolas Cellier and I need help. > > Should I introduce in pharo closeTo:interval: > > Any suggestions that a newby can understand is welcome. > > > Stef > > >

Sept. 2, 2016

Re: [Pharo-users] Commit to Monticello from the code browser

by Federico.Balaguer

Hello, >From the Monticello chapter I had the impression that using the package-cache as -default- repository would have the same effect on the tools. After I created a file repository for my package (different from the package-cache) and made a change to a method on that package I saw the Commit menu option again in the context menu of the package. I didn't watch the videos and after you mention MOOC I didn't find the video you mention (http://files.pharo.org/mooc/) Would you mind point me to the right video. I am also trying to learn about Versionner. Thanks! Federico -- View this message in context: http://forum.world.st/Commit-to-Monticello-from-the-code-browser-tp4913844p… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 2, 2016