September 2016 - Pharo-users

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

Re: [Pharo-users] Comparing floats

by Henrik Nergaard

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] Comparing floats

by Esteban A. Maringolo

Why not use "equalsTo:"? Floats are tricky, you either round your result before comparing or change the comparison method. 0.333333333333333333 equalsTo: (1/3) "true" Regards! Esteban A. Maringolo 2016-09-02 15:41 GMT-03:00 stepharo <stepharo(a)free.fr>: > 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 stepharo

In my version there is commit in package menu (even if I never used it). Did you see the videos I did for the mooc that explains the versions/and more Le 2/9/16 Ã 18:14, Federico.Balaguer a Ã©crit : > Hello all, > > I am stuck with a silly issue but I can't figure it out. I am developing a > simple class as an example for using during a lecture. > > I want to play with different version of the code and I set the package to > use the package-cache on Monticello. So, I can save the package on the > package-cache from the Monticello Browser but I can't commit the package > from code Browser. > > I would like to do it and show my students how to do it from the browser :-) > > Thanks. Federico > > > > -- > View this message in context: http://forum.world.st/Commit-to-Monticello-from-the-code-browser-tp4913844.… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Sept. 2, 2016

Comparing floats

by stepharo

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

Commit to Monticello from the code browser

by Federico.Balaguer

Hello all, I am stuck with a silly issue but I can't figure it out. I am developing a simple class as an example for using during a lecture. I want to play with different version of the code and I set the package to use the package-cache on Monticello. So, I can save the package on the package-cache from the Monticello Browser but I can't commit the package from code Browser. I would like to do it and show my students how to do it from the browser :-) Thanks. Federico -- View this message in context: http://forum.world.st/Commit-to-Monticello-from-the-code-browser-tp4913844.… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 2, 2016

Re: [Pharo-users] Spec Text Emphasis

by Sean P. DeNigris

Sean P. DeNigris wrote > There must be some sort of guard inside TextModel that no-ops if the > string is the same, so changing the text works: This seems to be true of plain TextMorphs as well. More disturbingly, it seems that LabelMorphs *silently throw away any emphasis that isn't bold or italics* due to the implementation of LogicalFont>>#emphasized:. Argh... On another note, bare TextMorphs adapted for Spec successfully displayed the strikethrough, but I can't for the life of me figure out how to get them #hResizing: #spaceFill! I tried both: newRow: [:row | row newColumn: [ :col | col add: #checkbox ] width: 25; newColumn: [ :col | col add: #textField ] ] height: 35; and without the columns: newRow: [:row | row add: #checkbox width: 25; add: #textField ] height: 35; I've run out of time for this project. Thank you for your help. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spec-Text-Emphasis-tp4913688p4913834.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 2, 2016