December 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] xpath queries

by Alain Fischer

Do you know Pastell ? http://www.squeaksource.com/Pastell.html http://wiki.squeak.org/squeak/Pastell http://blog.corriga.net/2007/06/pastell-xpath-like-library-for-squeak.html http://astares.blogspot.com/2010/01/pharosqueak-and-xml.html On 19 dÃ©c. 11, at 12:43, Tudor Girba wrote: > Hi, > > Is there some solution for supporting XPath queries in Pharo? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Dec. 19, 2011

Re: [Pharo-project] xpath queries

by Tudor Girba

Thanks. It works now :) Regarding the wildcard expression (//), is it correct to assume that it does not work for now, or is there some hidden trigger? :) I tried this: xml := '<root> <top> <second/> </top> </root>'. element := PPXmlParser parse: xml. element find: '/top/second'. "--> this works fine" element find: '/top//second'. "--> this does not" Cheers, Doru On Mon, Dec 19, 2011 at 1:38 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > > El 19/12/2011, a las 9:11a.m., Tudor Girba escribiÃ³: > >> Thanks, Esteban. >> >> I gave it a try, but I cannot seem to make it work (and there are no tests :)). > > yes... I know that :( > I will add them when I can spare some time... and a couple of examples too :P > >> >> Here is an example of what I tried: >> xml := '<root> >> Â Â Â <topChild/> >> </root>'. >> element := PPXmlParser parse: xml. >> element find: 'root/topChild' > > there is a "known" issue (known by me :( ): > PetitXPath is ignoring "document root element"... this is a stupid error and I will fix it (real reason is that when I coded it, I assumed "first element is always unique, so... let's get rid of it"... and yes I know it was a stupid assumption... but I needed this working really fast or my client would became upset) > > So... if you do: > > element find: '/topChild' > > It should work... good thing is other ppl using this stuff encourages me to make it work as it should be :) > > cheers, > Esteban -- www.tudorgirba.com "Every thing has its own flow"

Dec. 19, 2011

Re: [Pharo-project] Time to rename Object>>#name ?

by Marcus Denker

On Dec 17, 2011, at 11:25 AM, Janko MivÅ¡ek wrote: > Hi guys, > > Isn't a time come to finally rename this unfortunate method #name in > Object to something more internal? Yes! But we need to check how this interats with Morphic name/externalName (which we should clean up, too) -- Marcus Denker -- http://marcusdenker.de

Dec. 19, 2011

Re: [Pharo-project] xpath queries

by Esteban Lorenzano

Hi, El 19/12/2011, a las 9:11a.m., Tudor Girba escribiÃ³: > Thanks, Esteban. > > I gave it a try, but I cannot seem to make it work (and there are no tests :)). yes... I know that :( I will add them when I can spare some time... and a couple of examples too :P > > Here is an example of what I tried: > xml := '<root> > <topChild/> > </root>'. > element := PPXmlParser parse: xml. > element find: 'root/topChild' there is a "known" issue (known by me :( ): PetitXPath is ignoring "document root element"... this is a stupid error and I will fix it (real reason is that when I coded it, I assumed "first element is always unique, so... let's get rid of it"... and yes I know it was a stupid assumption... but I needed this working really fast or my client would became upset) So... if you do: element find: '/topChild' It should work... good thing is other ppl using this stuff encourages me to make it work as it should be :) cheers, Esteban

Dec. 19, 2011

Re: [Pharo-project] xpath queries

by Tudor Girba

Thanks, Esteban. I gave it a try, but I cannot seem to make it work (and there are no tests :)). Here is an example of what I tried: xml := '<root> <topChild/> </root>'. element := PPXmlParser parse: xml. element find: 'root/topChild' I get an invalid index error in PPXPathIndexFilter>>resolveOn:. Am I doing something wrong? Also, wildcards do not seem to be suported by the XPath grammar just yet. Cheers, Doru On Mon, Dec 19, 2011 at 12:47 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi Doru, > > There is a PetitXPath... not complete (just the functionality I needed). And it relies on PetitXml, not html... but I can be easily adapted. > > cheers, > Esteban > > El 19/12/2011, a las 8:43a.m., Tudor Girba escribiÃ³: > >> Hi, >> >> Is there some solution for supporting XPath queries in Pharo? >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 19, 2011

Re: [Pharo-project] xpath queries

by Esteban Lorenzano

Hi Doru, There is a PetitXPath... not complete (just the functionality I needed). And it relies on PetitXml, not html... but I can be easily adapted. cheers, Esteban El 19/12/2011, a las 8:43a.m., Tudor Girba escribiÃ³: > Hi, > > Is there some solution for supporting XPath queries in Pharo? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Dec. 19, 2011

[Pharo-project] xpath queries

by Tudor Girba

Hi, Is there some solution for supporting XPath queries in Pharo? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Dec. 19, 2011

Re: [Pharo-project] Newbie observations on use of Metacello

by Esteban Lorenzano

Hi, ages ago I did an extension for gofer, the "Gofer project loader", who does what Ben is asking for: Gofer project load: 'Seaside30'. it was incomplete, but working. I stopped working on this because no one (except Dale) showed interest on it, so I prefer to assign my time to things more useful for community (hehe, this sounds as a complain, but it is not: just a description of why I stopped working on that :) cheers, Esteban El 19/12/2011, a las 5:43a.m., StÃ©phane Ducasse escribiÃ³: > ben thanks for your feedback. > > Normally we should use the monticello repository browser and just click on a ConfigurationOf > > than did you read the forthcoming chapter? > https://gforge.inria.fr/frs/download.php/28462/Metacello.pdf (old version) > > Stef > > > > On Dec 19, 2011, at 5:15 AM, Ben Coman wrote: > >> Some observations from the perspective of as a newbie on Pharo Package Management. I'm likely to me missing in the philosophy of the design, but from the narrow view of my own usage.... >> >> 1. When I read about Metacello being the package management system, I expected there to be a "command"(*) Metacallo but instead I see Gopher being used. This is a mixed message that lowers my comfort level feeling I understand the system as I'm trying to pick up a bundle of new ideas. As I now understand it Metacello is more about a system of backend configuration than a front end user interface. I am now more comfortable using Gopher direct - but I reflect on how I felt the first time. >> >> (*) While technically a "command" is like a verb, and Gopher is like a noun rather than a verb - I can't yet completely disengage my prior learning that considers the first part of the statement to be a "command" - and I expect other newbies might find the same. >> >> 2. The strong convention of naming things ConfigurationOfXXXX is somewhat redundant from a user perspective. >> >> 3. If copy-paste into the Workspace from a web site a sample package load (for example b> below) and then highlight the whole thing and execute, it tells me >> "Unknown variable: ConfigurationOfSqueakDBX, please correct, or cancel" Duh! What? Oh, I need to execute it in two parts. No one wrote that down anywhere.... >> The alternative "(Smalltalk at: #ConfigurationOfSqueakDBX)" adds further complexity in the eyes of a newbie. >> >> Based on the above points, it would be nice to have... >> >> a> Metacello configuration: 'SqueakDBX' load >> >> rather than... >> >> b> Gofer new >> b> squeaksource: 'MetacelloRepository'; >> b> package: 'ConfigurationOfSqueakDBX'; >> b> load. >> b> ConfigurationOfSqueakDBX project latestVersion load. >> >> While only a small saving in typing, I think it significant for newbies in terms of polish and the marketing message that Metacello really is the chosen package management system. >> A very rough implementation (with much of the syntax likely wrong) might be just... >> >> c> Metacello class >> package: aPackage >> c> | packageConfig | >> c> packageConfig := 'ConfigurationOf', aPackage; >> c> Gopher new c> squeaksource: 'MetacelloRepository'; >> c> package: packageConfig >> c> load >> c> ^((Smalltalk at: (packageConfig asSymbol)) >> >> >> Now after I've written the above I contemplate that there must have been an early design decision to not implement a separate Metacello class to avoid duplication/overlap with Monticello. However perhaps now that the system is implemented as it is, a thin shim can be put over the top to assist getting the ConfigurationOfXXX files downloaded. Additional things this Metacello class might later provide: a. Improved reliability by downloading from a system of package repository mirrors. SqueakSource was having some issues and I found [1] a fortunate backup. b. A GUI for browsing package versions >> c. A GUI for browsing compatibility tables from a continuous integration system that tries different permutations of Montecello packages together. >> >> >> 4. It seems that every ConfigurationOfXXX has its own category in the SystemBrowser. Each of these categories has only one class. This seems to me like unneeded clutter of the System Browser. It would be neater if Metacello specified its configurations to be grouped under a single category "MetacelloConfigurations" or similar. >> >> 5. The sample Metacello PBE is very good in the detail for developers to provide configurations. However there is not much directed clearly at a 'mere' user. Even though Smalltalk makes us all developers, newbies all start as mere users while exploring the system. >> [1] Gofer new url: 'http://dsal.cl/squeaksource/MonticelloRedirect'; package: 'MontiRedirect'; load. MRManager redirectFrom: 'http://www.squeaksource.com/' to: 'http://dsal.cl/squeaksource/'. >> >> Cheers, Ben >> > >

Dec. 19, 2011

Re: [Pharo-project] Newbie observations on use of Metacello

by StÃ©phane Ducasse

ben thanks for your feedback. Normally we should use the monticello repository browser and just click on a ConfigurationOf than did you read the forthcoming chapter? https://gforge.inria.fr/frs/download.php/28462/Metacello.pdf (old version) Stef On Dec 19, 2011, at 5:15 AM, Ben Coman wrote: > Some observations from the perspective of as a newbie on Pharo Package Management. I'm likely to me missing in the philosophy of the design, but from the narrow view of my own usage.... > > 1. When I read about Metacello being the package management system, I expected there to be a "command"(*) Metacallo but instead I see Gopher being used. This is a mixed message that lowers my comfort level feeling I understand the system as I'm trying to pick up a bundle of new ideas. As I now understand it Metacello is more about a system of backend configuration than a front end user interface. I am now more comfortable using Gopher direct - but I reflect on how I felt the first time. > > (*) While technically a "command" is like a verb, and Gopher is like a noun rather than a verb - I can't yet completely disengage my prior learning that considers the first part of the statement to be a "command" - and I expect other newbies might find the same. > > 2. The strong convention of naming things ConfigurationOfXXXX is somewhat redundant from a user perspective. > > 3. If copy-paste into the Workspace from a web site a sample package load (for example b> below) and then highlight the whole thing and execute, it tells me > "Unknown variable: ConfigurationOfSqueakDBX, please correct, or cancel" Duh! What? Oh, I need to execute it in two parts. No one wrote that down anywhere.... > The alternative "(Smalltalk at: #ConfigurationOfSqueakDBX)" adds further complexity in the eyes of a newbie. > > Based on the above points, it would be nice to have... > > a> Metacello configuration: 'SqueakDBX' load > > rather than... > > b> Gofer new > b> squeaksource: 'MetacelloRepository'; > b> package: 'ConfigurationOfSqueakDBX'; > b> load. > b> ConfigurationOfSqueakDBX project latestVersion load. > > While only a small saving in typing, I think it significant for newbies in terms of polish and the marketing message that Metacello really is the chosen package management system. > A very rough implementation (with much of the syntax likely wrong) might be just... > > c> Metacello class >> package: aPackage > c> | packageConfig | > c> packageConfig := 'ConfigurationOf', aPackage; > c> Gopher new c> squeaksource: 'MetacelloRepository'; > c> package: packageConfig > c> load > c> ^((Smalltalk at: (packageConfig asSymbol)) > > > Now after I've written the above I contemplate that there must have been an early design decision to not implement a separate Metacello class to avoid duplication/overlap with Monticello. However perhaps now that the system is implemented as it is, a thin shim can be put over the top to assist getting the ConfigurationOfXXX files downloaded. Additional things this Metacello class might later provide: a. Improved reliability by downloading from a system of package repository mirrors. SqueakSource was having some issues and I found [1] a fortunate backup. b. A GUI for browsing package versions > c. A GUI for browsing compatibility tables from a continuous integration system that tries different permutations of Montecello packages together. > > > 4. It seems that every ConfigurationOfXXX has its own category in the SystemBrowser. Each of these categories has only one class. This seems to me like unneeded clutter of the System Browser. It would be neater if Metacello specified its configurations to be grouped under a single category "MetacelloConfigurations" or similar. > > 5. The sample Metacello PBE is very good in the detail for developers to provide configurations. However there is not much directed clearly at a 'mere' user. Even though Smalltalk makes us all developers, newbies all start as mere users while exploring the system. > [1] Gofer new url: 'http://dsal.cl/squeaksource/MonticelloRedirect'; package: 'MontiRedirect'; load. MRManager redirectFrom: 'http://www.squeaksource.com/' to: 'http://dsal.cl/squeaksource/'. > > Cheers, Ben >

Dec. 19, 2011

[Pharo-project] Escrow agreement Smalltalk projects

by StÃ©phane Ducasse

> From: Rob Vens <rob(a)sepher.nl> > Subject: [Esug-list] [Dutch] Escrow agreement Smalltalk projects > Date: December 18, 2011 2:31:11 PM GMT+01:00 > To: ESUG Members <esug-list(a)lists.esug.org> > > Dear Smalltalkers, > This issue has been raised by a small Dutch company that delivers (Pharo/Seaside) Smalltalk solutions. > When you, as an individual or small company, deliver Smalltalk solutions there is an implied risk for your customers in case of illness or such. > This risk can be mitigated through an agreement with other developers/companies in which they state that they are willing and able to take development and support upon themselves, temporary or (semi-) permanent. > Of course the process to get this formally agreed is a bit more complex, but this mail is only to ask whether there are (in this case preferably Dutch) Smalltalk developers willing to cooperate on this issue and possibly participate in some kind of legal agreement to provide more robust support to our customers. > Please reply to me personally, unless of course you want your response to benefit the broader Smalltalk community on this mailing list. > Rob Vens - rob(a)sepher.nl

Dec. 19, 2011