May 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Fwd: [Pharo-project] XPath issue ?

by HernÃ¡n Morales Durand

I submitted a fix, please check with the latest version at http://ss3.gemstone.com/ss/XPath.html cheers, HernÃ¡n El 14/05/2013 4:46, Herve Verjus escribiÃ³: > Hello, > > Erwan gave me a piece of code I will test in the next couple of days :-) > > Thanks > > Herve > > StÃ©phane Ducasse wrote: >> HI guys may be this mail passed under the radar >> >> Stef >> >> Begin forwarded message: >> >>> *From: *Herve Verjus <herve.verjus(a)univ-savoie.fr >>> <mailto:herve.verjus@univ-savoie.fr>> >>> *Subject: **[Pharo-project] XPath issue ?* >>> *Date: *May 8, 2013 11:23:01 PM GMT+02:00 >>> *To: *Pharo-project(a)lists.gforge.inria.fr >>> <mailto:Pharo-project@lists.gforge.inria.fr> >>> *Reply-To: *Pharo-project(a)lists.gforge.inria.fr >>> <mailto:Pharo-project@lists.gforge.inria.fr> >>> >>> Dear All, >>> >>> I try a very simple example: >>> >>> mydoc.xml document: >>> >>> >>> <?xml version="1.0" encoding="UTF-8" ?> >>> >>> <first> >>> <second> >>> <item type="attvalue">nodevalue</item> >>> </second> >>> </first> >>> >>> >>> And the Pharo code found in the book.pharo-project.org >>> <http://book.pharo-project.org>: >>> >>> | doc results | >>> doc := XMLDOMParser parseFileNamed: 'mydoc.xml'. >>> results := ( XPath for: 'first' ) in: doc. >>> results explore >>> >>> >>> As a result, I obtain an empty OrderedCollection...It should contain >>> an element. Then a make some changes using different XPath expressions >>> (i.e. '/first/second/item/@type", etc.) but no way. >>> >>> Then I discover the first element of the XPath expression must not be >>> the root of the XML doc. If I change the mydoc.xml, introducing a new >>> root element: >>> >>> >>> <?xml version="1.0" encoding="UTF-8" ?> >>> >>> <foo> >>> <first> >>> <second> >>> <item type="attvalue">nodevalue</item> >>> </second> >>> </first> >>> </foo> >>> >>> Everything is ok (the same code as above). Here, XPath assumes that >>> the first tag we are looking for is not the root of the doc, otherwise >>> it fails. I'm not so sure but it seems that such implementation >>> doesn't follow the XPath specs. I tried another example from >>> http://www.w3schools.com/xpath/xpath_syntax.asp and same results: I >>> obtain an empty collection when using an XPath expression beginning >>> with the 'bookstore' tag, the root element of the doc: >>> >>> | doc results | >>> doc := XMLDOMParser parseFileNamed: 'books.xml'. >>> results := ( XPath for: '/bookstore' ) in: doc. >>> results explore >>> >>> Maybe, I missed something... >>> >>> Note: I have had to replace the isTag (deprecated) with isElement in >>> some piece of XPath code. >>> >>> Cheers, >>> >>> Herve >>> >> > >

May 18, 2013

Re: [Pharo-dev] collaborActive book refers to SS

by stephane ducasse

Ok I imagine that this is the right one. Stef On May 18, 2013, at 7:50 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > Hi Stef, > > I mean this guy: > https://github.com/SquareBracketAssociates/PharoByExample-english/pull/19 > > frank > > On 18 May 2013 15:52, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >> frank you are about Pharo by example (which is hosted on github)? >> >> I'm checking because PBE2 is on github but this is an old version since I moved the chapter to svn. >> >> Stef >> >> >> On May 16, 2013, at 12:44 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >> >>> >>> On May 16, 2013, at 12:13 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>> >>>> On 16 May 2013 10:38, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>>>> >>>>> On May 16, 2013, at 11:23 AM, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>>>> >>>>>> http://book.pharo-project.org/book/Tidbits/FAQ/Packages/ >>>>>> >>>>>> talks about how you can create a SqueakSource project. Presumably we >>>>>> want this to explain either how to create an SS3 project or a StHub >>>>>> project? >>>>>> >>>>>> If all I need to do is issue a pull request to >>>>>> https://github.com/SquareBracketAssociates/PharoByExample-english/ I'm >>>>>> happy to update it to whichever you prefer. >>>>> >>>>> please do :) >>>> >>>> I'm guessing you'd want to point to StHub? >>> >>> yes >>> >>>> (I use ss3 for everything, >>>> but it seems most of the Pharo devs are pushing for StHub.) >>> >>> Yes >>> >>> >> >> >

May 18, 2013

Re: [Pharo-dev] collaborActive book refers to SS

by Frank Shearar

Hi Stef, I mean this guy: https://github.com/SquareBracketAssociates/PharoByExample-english/pull/19 frank On 18 May 2013 15:52, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > frank you are about Pharo by example (which is hosted on github)? > > I'm checking because PBE2 is on github but this is an old version since I moved the chapter to svn. > > Stef > > > On May 16, 2013, at 12:44 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > >> >> On May 16, 2013, at 12:13 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: >> >>> On 16 May 2013 10:38, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>>> >>>> On May 16, 2013, at 11:23 AM, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>>> >>>>> http://book.pharo-project.org/book/Tidbits/FAQ/Packages/ >>>>> >>>>> talks about how you can create a SqueakSource project. Presumably we >>>>> want this to explain either how to create an SS3 project or a StHub >>>>> project? >>>>> >>>>> If all I need to do is issue a pull request to >>>>> https://github.com/SquareBracketAssociates/PharoByExample-english/ I'm >>>>> happy to update it to whichever you prefer. >>>> >>>> please do :) >>> >>> I'm guessing you'd want to point to StHub? >> >> yes >> >>> (I use ss3 for everything, >>> but it seems most of the Pharo devs are pushing for StHub.) >> >> Yes >> >> > >

May 18, 2013

Re: [Pharo-dev] Small Methods dont need comments , true or myth ?

by stephane ducasse

> > Yes that is a screenshot. MessageTrace is just a subclass of the > classic MessageSet which, when the user highlights a chunk of code in > the bottom pane and presses i(m)plementors, rather than opening a new > window or pane, the implementors are listed in the top-half of the > same browser, indented below the currently selected message. > > Likewise, when the user selects (s)enders on a message in the upper > pane, it outdents those senders above the selected message. Multiple > paths of flow can be built. > > Since it does not do type-inference, heavily overloaded selectors will > cause many extra senders/implementors to be put into the browser -- so > to handle this the UI merely allows the user to easily trim unwanted > messages with a couple of simple gestures (swipe select + Command-d). > > The result is a single window that encapsulates the method flow of a > single piece of functionality (e.g., a "Trace") that the user can > comprehend because of the way it is presented. > > Try it out in Squeak is the best way to appreciate it. The code for > it is not complicated I'm sure it could be adapted into Pharo.. Thanks for the explanation. I will try it in squeak because when I thought about that browser I was concerned with the senders/multiple implementors display. Stef

May 18, 2013

Re: [Pharo-dev] Small Methods dont need comments , true or myth ?

by Chris Muller

Hi, >> That's why I use Squeak's MessageTrace, it handles this better than >> anything else in any Smalltalk. It is a "lightweight" way, in terms >> of gestures and UI elements, to trace through code without getting >> lost. I wish Pharo would consider implementing a tool like this. > > Can you explain it? This is the screenshot? > The top line the sender for ensureSecondaryLinkConfigured > then see its senders? > Its self sends? > Because I want (and I was thinking about that too for long time) something like that. Yes that is a screenshot. MessageTrace is just a subclass of the classic MessageSet which, when the user highlights a chunk of code in the bottom pane and presses i(m)plementors, rather than opening a new window or pane, the implementors are listed in the top-half of the same browser, indented below the currently selected message. Likewise, when the user selects (s)enders on a message in the upper pane, it outdents those senders above the selected message. Multiple paths of flow can be built. Since it does not do type-inference, heavily overloaded selectors will cause many extra senders/implementors to be put into the browser -- so to handle this the UI merely allows the user to easily trim unwanted messages with a couple of simple gestures (swipe select + Command-d). The result is a single window that encapsulates the method flow of a single piece of functionality (e.g., a "Trace") that the user can comprehend because of the way it is presented. Try it out in Squeak is the best way to appreciate it. The code for it is not complicated I'm sure it could be adapted into Pharo..

May 18, 2013

Re: [Pharo-dev] Small Methods dont need comments , true or myth ?

by kilon

well i was thinking more like methods that do something ... but as i said, if the method is that obvious I am ok with not having it a comment. I would add a comment though for the sake of automatic documentation. Its a python habbit. even empty methods do get whats called as python doc strings , very similar to smalltalk its a string that can be used for generating later on hmtl documentation which makes things obviously a lot easier. And i think thats also another big plus for commenting even empty methods. I have no idea though if pharo has a documentation generation library from method comments. I assume it has . -- View this message in context: http://forum.world.st/Pharo-dev-Small-Methods-dont-need-comments-true-or-my… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 18, 2013

Re: [Pharo-dev] Small Methods dont need comments , true or myth ?

by Sean P. DeNigris

kilon wrote > EVERY method needs a comment , not because its that hard to read a few > lines of code but because its plain simpler and faster. -100. Prime example: AbstractBindings>>#initialize "Initialization code for AbstractHolder" That comment is totally redundant for everyone but novices (and maybe even for them). It's actually worse than that: a) I have to read it to find out it's a totally useless comment b) As you can see, it's already rotted. The class is called AbstractBindings, but the comment thinks it's AbstractHolder So, I agree that there may be a "why" in many cases that would be great to capture in a comment, it does not apply to *all* cases. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-dev-Small-Methods-dont-need-comments-true-or-my… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 18, 2013

Re: [Pharo-dev] collaborActive book refers to SS

by stephane ducasse

frank you are about Pharo by example (which is hosted on github)? I'm checking because PBE2 is on github but this is an old version since I moved the chapter to svn. Stef On May 16, 2013, at 12:44 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > > On May 16, 2013, at 12:13 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > >> On 16 May 2013 10:38, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>> >>> On May 16, 2013, at 11:23 AM, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>> >>>> http://book.pharo-project.org/book/Tidbits/FAQ/Packages/ >>>> >>>> talks about how you can create a SqueakSource project. Presumably we >>>> want this to explain either how to create an SS3 project or a StHub >>>> project? >>>> >>>> If all I need to do is issue a pull request to >>>> https://github.com/SquareBracketAssociates/PharoByExample-english/ I'm >>>> happy to update it to whichever you prefer. >>> >>> please do :) >> >> I'm guessing you'd want to point to StHub? > > yes > >> (I use ss3 for everything, >> but it seems most of the Pharo devs are pushing for StHub.) > > Yes > >

May 18, 2013

Re: [Pharo-dev] AsmJit-Core not in Pharo30 repository

by Marcus Denker

On May 17, 2013, at 3:58 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > marcus you will explain that to me so that I understand. > Oh, I think I just misunderstoodâ¦ there are some missing packages and the Smartsuggestions/NodeNavigation have their config as depend. I will first check to make sure that all the missing packages are in the repo. Marcus > Stef > > On May 17, 2013, at 3:53 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On May 17, 2013, at 3:35 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >> >>> ...and some other AsmJit packages, ConfigurationOfNodeNavigation and ConfigurationOfSmartSuggestions >>> >> >> Yes, we need to improve the setupâ¦ right now we commit to pharo and then merge later with upstream. >> This is not good. >> >>> -- Pavel >>> >>> On Fri, May 17, 2013 at 3:30 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >>> Hi, >>> >>> the package AsmJit-Core has in Smalltalkhub Pharo30 repository no version. >>> >>> Cheers, >>> -- Pavel >>> >> >

May 18, 2013

[update 3.0] #30144

by Marcus Denker

30144 ----- 10666 FileList should work on any FileSystem https://pharo.fogbugz.com/f/cases/10666 10664 Unify and clean a bit the CommandLine class comments https://pharo.fogbugz.com/f/cases/10664 10663 RPackageOrganizer out of sync https://pharo.fogbugz.com/f/cases/10663 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/UpdateStreamer-Core-MarcusDen… http://smalltalkhub.com/mc/Pharo/Pharo30/main/ToolsTest-MarcusDenker.denker… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1124.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-CommandLine-MarcusDenk… http://smalltalkhub.com/mc/Pharo/Pharo30/main/HudsonBuildTools20-MarcusDenk… http://smalltalkhub.com/mc/Pharo/Pharo30/main/FuelCommandLineHandler-Marcus… http://smalltalkhub.com/mc/Pharo/Pharo30/main/ConfigurationCommandLineHandl… http://smalltalkhub.com/mc/Pharo/Pharo30/main/AndreasProfiler-MarcusDenker.…

May 18, 2013