- Pharo-users - lists.pharo.org

Re: [Pharo-users] remove the line at the bottom of the code pane in Nautilus in Pharo 5?

by stepharo

Hi Paul I checked you submission and we cannot simply remove the bar. For example people like me use a lot the format and and we should have a way to activate it. So either we propose a setting or we make sure that the format as you read button is available somewhere. Stef Le 5/9/16 Ã 00:26, Paul DeBruicker a Ã©crit : > I made issue 19039 and submitted a slice that does this to the Pharo50Inbox. > > SLICE-Issue-19039-Remove-the-source-code-annotation-pane-from-Nautilus-PaulDeBruicker.1 > > > > > > stepharo wrote >> Do not hesitate to submit a slice. >> >> Stef >> >> >>> Hi - >>> >>> I don't think I'll be changing the settings for >>> >>> format as you read >>> wrapping >>> line number >>> >>> or reading the cursor position/line number ever. >>> >>> Is there a way to remove that section from the nautilus code pane? >>> >>> >>> Thanks >>> >>> >>> Paul >>> >>> > > > > > -- > View this message in context: http://forum.world.st/remove-the-line-at-the-bottom-of-the-code-pane-in-Nau… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Sept. 5, 2016

Re: [Pharo-users] remove the line at the bottom of the code pane in Nautilus in Pharo 5?

by stepharo

Hi Paul Tx Pay attention that you should use the latest alpha version and publish in the pharo60 inbox. We cannot check all repositories this is too much works and the integration tool only look into one inbox. Stef Le 5/9/16 Ã 00:26, Paul DeBruicker a Ã©crit : > I made issue 19039 and submitted a slice that does this to the Pharo50Inbox. > > SLICE-Issue-19039-Remove-the-source-code-annotation-pane-from-Nautilus-PaulDeBruicker.1 > > > > > > stepharo wrote >> Do not hesitate to submit a slice. >> >> Stef >> >> >>> Hi - >>> >>> I don't think I'll be changing the settings for >>> >>> format as you read >>> wrapping >>> line number >>> >>> or reading the cursor position/line number ever. >>> >>> Is there a way to remove that section from the nautilus code pane? >>> >>> >>> Thanks >>> >>> >>> Paul >>> >>> > > > > > -- > View this message in context: http://forum.world.st/remove-the-line-at-the-bottom-of-the-code-pane-in-Nau… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Sept. 5, 2016

Lint Rule for Class-Side Method

by Sean P. DeNigris

I'm probably missing something obvious, but it seems like #checksMethod Lint Rules only get checked against instance-side methods. How does one check class-side methods? I converted it to a #checksClass rule, but then hits showed the class definition instead of the offending method source. Thanks. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Lint-Rule-for-Class-Side-Method-tp4914121.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 5, 2016

Re: [Pharo-users] remove the line at the bottom of the code pane in Nautilus in Pharo 5?

by Paul DeBruicker

I made issue 19039 and submitted a slice that does this to the Pharo50Inbox. SLICE-Issue-19039-Remove-the-source-code-annotation-pane-from-Nautilus-PaulDeBruicker.1 stepharo wrote > Do not hesitate to submit a slice. > > Stef > > >> Hi - >> >> I don't think I'll be changing the settings for >> >> format as you read >> wrapping >> line number >> >> or reading the cursor position/line number ever. >> >> Is there a way to remove that section from the nautilus code pane? >> >> >> Thanks >> >> >> Paul >> >> -- View this message in context: http://forum.world.st/remove-the-line-at-the-bottom-of-the-code-pane-in-Nau… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 4, 2016

Current Preferred Git Tool

by Sean P. DeNigris

I've mostly use bare filetree (so not to install anything), and sometimes GitFileTree (eliminates a few steps), but I see there's a lot of activity in other projects. Is anything production-ready? I'm thinking for projects where one needs it to "just work" and doesn't have the luxury of beta testing... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Current-Preferred-Git-Tool-tp4914110.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 4, 2016

Re: [Pharo-users] Comparing floats

by Alexandre Bergel

JUnit has the equivalent of: assert:equals:range: It could then be: self assert: 11.11 equals: 11.11 range: 0.0001 Alexandre > On Sep 2, 2016, at 7:21 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > 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 >> >> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 4, 2016

Re: [Pharo-users] UFFI cleanup of externally allocated memory (was Re: UFFI const, unsigned, opaque-ish types)

by Ben Coman

On Fri, Sep 2, 2016 at 10:04 PM, Pierce Ng <pierce(a)samadhiweb.com> wrote: > On Fri, Sep 02, 2016 at 12:40:06PM +0800, Ben Coman wrote: >> Referring to the example show_clang_version() below, cleanup is done >> with clang_disposeString(). How does UFFI hook into the object >> finalisation mechanism to call this when the object is garage >> collected. > > Ben, see if this addresses your query: > > http://www.samadhiweb.com/blog/2016.03.12.demoffi.html > > Pierce > Thanks Pierce. I've loaded DemoFFI and browsing it now. autorelease looks like part of what I need. I guess it is #finalize where I should call the libraryAPI_free() function? cheers -ben

Sept. 4, 2016

priority for startup actions

by i.uhnak＠gmail.com

Hi, Is there a way to specify a priority for startup scripts? I would like to setup some environment for all the startup scripts (related to cross-platform compatibility), but I donât really understand in what order are the startup scripts executed. Thanks, Peter

Sept. 4, 2016

Re: [Pharo-users] Coding XPath as Smalltalk

by PBKResearch

Hi Monty Just to say that I have obtained the Moose 6.0 image (Pharo5.0 Latest update: #50761) and installed the XMLHTMLParser, and I seem able to reproduce the nucleus of the results I had from my old image. Some of my old XPath strings do not work (e.g. it did not recognise [1]), but I have worked my way round that, and I should soon have worked out the new syntax. Thanks for your suggestions for the variable case; I can now see the way ahead for that. Thanks for all the help. @stef I have loaded the same version of TextLint as I had in the previous image. It was accepted with no problems. I have tested it for the limited uses I make of it (just the parsers, not the rules) and everything seems OK. So now I am upgraded to Pharo 5, so far with no problems! Peter Kenny -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of monty Sent: 03 September 2016 13:00 To: pharo-users(a)lists.pharo.org Subject: Re: [Pharo-users] Coding XPath as Smalltalk > Sent: Saturday, September 03, 2016 at 5:30 AM > From: PBKResearch <peter(a)pbkresearch.co.uk> > To: "'Any question about pharo is welcome'" <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] Coding XPath as Smalltalk > > Hi Monty > > Many thanks. I have picked up a project that I had not worked on for a while, which explains why I am using an old image. I shall try the latest Moose image, as you suggest. My only anxiety is that I need to be able to use a rather ancient package called TextLint, and I do not know whether it will load OK in a new Pharo. If not, I shall try to update my existing image. If you'd looked at CI job, you'd see that XPath builds on Pharo 5 through 3 (but should work back to 1.4). You can always start fresh with a clean, old image from http://files.pharo.org/image/ or the Moose website if TextLint doesn't work anymore. > With the latest XPath, will it be clear how to use the binary syntax to carry out node tests like the example of '//div[@id=''catlinks'']//' that I cited below? The case I am interested in is where the actual identifier ('catlinks' in this case) is a variable rather than a constant. It would be possible to do it in standard XPath by assembling the XPath string with a variable component, but it might be more convenient in the binary syntax. > You could do this: ((doc // 'div') select: [:each | (each attributeAt: 'id') = catlinks]) // 'li' // 'text()' where "catlinks" is a var. Or you could use xPath:context: with an XPath var that you dynamically bind using custom contexts: doc xPath: '//div[@id=$catlinks]//li//text()' context: (XPathContext variables: {'catlinks' -> catlinks}) The advantage over this: doc xPath: '//div[@id=''', catlinks, ''']//li//text()' is that the xPath: expression string is the same each time, so it's only compiled once, the first time, and cached for later uses (inspect 'XPath compiledXPathCache') instead of being compiled each time the xPath: expression string arg changes. > Many thanks for your help. > > Peter Kenny > > -----Original Message----- > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of monty > Sent: 03 September 2016 06:54 > To: pharo-users(a)lists.pharo.org > Subject: Re: [Pharo-users] Coding XPath as Smalltalk > > 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 stepharo

> Yes, I also moved XMLParserHTML and XMLParserStAX from PharoExtras/XMLParser to separate PharoExtras repos. PharoExtras could be the place for community-maintained standard libs. > This one the idea for at least the ones I tried to take care. Stef

Sept. 3, 2016