February 2014 - Pharo-users

[Pharo Consortium] New Sponsor: Object Profile

by Marcus Denker

The Pharo Consortium is very happy to announce that Object Profile is supporting the Pharo Consortium as a Sponsor. More about - Object Profile: http://objectprofile.com - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org ==== ( This actually happened some weeks ago alreadyâ¦ sorry for the late announce. There is already another member listed (to be announced) and yet another will be added soon. In addition, we are nearly finished with setting up the infrastructure for the consortium membersâ¦ so if you are one of those and wonder: Soon (as in: this week). Sorry for the delay! )

Feb. 25, 2014

Re: [Pharo-users] [Pharo-dev] New methods for the String class

by Pharo4Stef

Daniela you should try the method finder open it and select the example in the dropbox then you can type examples and see if a method already implement it for example âabcabâ . âaâ . âbcb' shows that copyWithoutAll: is the method. but it expects a character as second argument âabcabâ . $a . âbcbâ Stef On 24 Feb 2014, at 18:30, Daniela Meneses <daniela11290(a)gmail.com> wrote: > Hi to all, > > As you may know I'm working on in some improvements for the String class. Until now I implemented some missing tests. Right now I'm looking forward to add new methods that could be useful based on Ruby API (http://www.ruby-doc.org/core-2.1.0/String.html) These are a few of the methods that I'm planning to implement: > > chomp(separator=$/) -> new_str > chop() -> new_str > ljust(integer, padstr='') ->new_str > next -> new_str > partition(sep) -> [head, sep, tail] > > Could you help to find out if these methods are already available for the String class? > > If you have any idea of new methods for the string class, will be really welcome. > > -- > Cheers, > Daniela Meneses

Feb. 24, 2014

collecting Pharo Youtube videos...

by Marcus Denker

Hi, There are a lot of videos on youtube about pharoâ¦ from conferences, demos, jamesâ Smalltalk4U, fosdem, ESUG, and others. I am (very slowly) adding playlists for all of them to the Pharo Youtube channel: https://www.youtube.com/channel/UCp3mNigANqkesFzdm058bvw/playlists If you have videos that you want to see added, send me a mail. The channel itself is here: https://www.youtube.com/channel/UCp3mNigANqkesFzdm058bvw It could use some more subscribers ;-) Marcus

Feb. 24, 2014

New methods for the String class

by Daniela Meneses

Hi to all, As you may know I'm working on in some improvements for the String class. Until now I implemented some missing tests. Right now I'm looking forward to add new methods that could be useful based on Ruby API ( http://www.ruby-doc.org/core-2.1.0/String.html) These are a few of the methods that I'm planning to implement: - chomp(separator=$/) -> new_str - chop() -> new_str - ljust(integer, padstr='') ->new_str - next -> new_str - partition(sep) -> [head, sep, tail] Could you help to find out if these methods are already available for the String class? If you have any idea of new methods for the string class, will be really welcome. -- Cheers , Daniela Meneses

Feb. 24, 2014

Re: [Pharo-users] Moose: Problem in Petit Parser

by PBK Research

Damien I have downloaded and skimmed through the chapter on PetitParser. It looks fine to me, it is a clear explanation of what PP does, but it does not go beyond what I have already found in the sources I mentioned. I recognised all the worked examples (expression parser, JSON parser etc.) as things I had come across before. I am not sure I had seen the section on testing before; that may mean I had skipped it because I am generally rather lazy about programming tests. What is clear to me, however, is that I was very unfair to say the documentation is sparse. As soon as I looked again at the Moose Book chapter, I saw an example which explained exactly the issue that tripped me up on 'not' vs. 'negate'. In other words, the only problem with the documentation is that I had not read it properly. I shall press on with my experiments, but I shall take good care to read everything I can find before raising queries. Thanks again Peter Kenny -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Damien Cassou Sent: 24 February 2014 12:13 To: Any question about pharo is welcome Subject: Re: [Pharo-users] Moose: Problem in Petit Parser On Mon, Feb 24, 2014 at 12:09 PM, PBK Research <peter(a)pbkresearch.co.uk> wrote: > c. The chapter in Lukas Renggli's PhD thesis. > It may be unfair to call this 'sparse'; the problem is perhaps my > inability to understand it. If you think 'Deep into Pharo' will give > me more than these sources, I may well get hold of it. please have a look at this chapter and please send us feedback (or better send us a patch for the chapter, I can give you access to the book sources). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 24, 2014

Re: [Pharo-users] Moose: Problem in Petit Parser

by Damien Cassou

On Mon, Feb 24, 2014 at 12:09 PM, PBK Research <peter(a)pbkresearch.co.uk> wrote: > c. The chapter in Lukas Renggli's PhD thesis. > It may be unfair to call this 'sparse'; the problem is perhaps my inability > to understand it. If you think 'Deep into Pharo' will give me more than > these sources, I may well get hold of it. please have a look at this chapter and please send us feedback (or better send us a patch for the chapter, I can give you access to the book sources). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 24, 2014

Re: [Pharo-users] Moose: Problem in Petit Parser

by PBK Research

Damien No, I haven't yet looked at that book. My main sources on PetitParser have been: a. Chapter 14 in the Moose Book; b. Two lengthy blog posts by Lukas Renggli referenced in the Moose documentation; c. The chapter in Lukas Renggli's PhD thesis. It may be unfair to call this 'sparse'; the problem is perhaps my inability to understand it. If you think 'Deep into Pharo' will give me more than these sources, I may well get hold of it. Thanks for your help Peter Kenny -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Damien Cassou Sent: 24 February 2014 09:33 To: Any question about pharo is welcome Subject: Re: [Pharo-users] Moose: Problem in Petit Parser On Sat, Feb 22, 2014 at 6:00 PM, PBK Research <peter(a)pbkresearch.co.uk> wrote: > The documentation is rather sparse did you read the dedicated book chapter of Deep into Pharo? http://deepintopharo.com/ -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 24, 2014

Re: [Pharo-users] Moose: Problem in Petit Parser

by Damien Cassou

On Sat, Feb 22, 2014 at 6:00 PM, PBK Research <peter(a)pbkresearch.co.uk> wrote: > The documentation is rather sparse did you read the dedicated book chapter of Deep into Pharo? http://deepintopharo.com/ -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 24, 2014

Re: [Pharo-users] The new versionner is cool

by HernÃ¡n Morales Durand

2014-02-21 8:25 GMT-03:00 Usman Bhatti <usman.bhatti(a)gmail.com>: > Hello, > > I found Versionner very productive tool. I was able to create a new > configuration "from scratch" within a few minutes with the packages that I > wanted to put into it. Though, I couldn't commit my new config through its > interface because Komitter kept asking for a issue number but I didn't have > it. > > You want to commit a new configuration through Kommiter?

Feb. 22, 2014

Re: [Pharo-users] Moose: Problem in Petit Parser

by PBK Research

Doru Many thanks. I knew it must be something simple. I was nearly there, because I had tried 'negated' as an alternative to 'not'. You may regret the invitation in your last line. The documentation is rather sparse, so there may well be more questions. I shall always try to solve it myself first, of course. Thanks also for the speedy answer - on a Saturday afternoon too! Peter _____ From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Tudor Girba Sent: 22 February 2014 16:38 To: Any question about pharo is welcome Subject: Re: [Pharo-users] Moose: Problem in Petit Parser Hi, For Moose related questions, there exists a dedicated mailing list: http://www.moosetechnology.org/about/contact Related to your problem, "not" does consume the input. You want to use "negate", which is implemented as: PPParser>>negate "Answer a new parser consumes any input token but the receiver." ^ self not , #any asParser ==> #second Keep the questions flowing :) Cheers, Doru On Sat, Feb 22, 2014 at 5:25 PM, PBK Research <peter(a)pbkresearch.co.uk> wrote: Hello All Not sure whether this is the right forum for this question - please excuse and point me in the right direction if I'm wrong. I have been playing with Moose 4.8, downloaded last October, mainly because I am interested in PetitParser. I have been constructing fairly trivial parsers to get to understand the system. I took as an example a typical HTML tag, i.e. any text enclosed in angle brackets <>. My first attempt was: ($< asParser, $> asParser not star, $> asParser). This seemed to send the parser into a loop, except in the case where there was no text between the brackets. Floundering around, I tried: ($< asParser, (PPPredicateObjectParser anyExceptAnyOf: '>') star, $> asParser). This worked as expected, but I was not happy with the apparent clumsiness of the middle term. So I tried: ($< asParser, (PPPredicateObjectParser char: $>) not star, $> asParser). This again sent the parser into a loop. It looks as though I have some fundamental misunderstanding of the function of 'not' in a parser, or else it is not working as specified. Could someone kindly explain to an inquisitive idiot what is going wrong? Many thanks in advance Peter Kenny -- www.tudorgirba.com "Every thing has its own flow"

Feb. 22, 2014