- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] GitHub API Bindings: new version

by Thierry Goubier

Hi Skip, this is great; I think you have something important there, and I'm just sad to have far too much to do to contribute... I'd just have a question then: is it possible to use it in anonymous mode? I would like to explore if it could be used as a way to get delivery mode (read-only access) to packages with history/versionning (reusing GitFileTree `build MC metadata from git log` code). Regards, Thierry 2016-01-21 11:30 GMT+01:00 Skip Lentz <skip.lentz(a)inria.fr>: > Hi everyone, > > I am announcing a new version for the API bindings to GitHub in Pharo. > For documentation and information on how to load it, see the new project > homepage: > > https://balletie.github.io/GitHub/ (generated with Pillar. Plug for > Damien and Cyril) > > For a list of changes in this release, follow this link: > https://github.com/Balletie/GitHub/releases/tag/v0.5 > > To load absolutely everything, including the tests and the tool, evaluate: > > Metacello new > baseline: 'GitHub'; > repository: 'github://Balletie/GitHub:master'; > load: #(tests tool) > > If you have loaded the tool, it can be opened via the world > menu, under âToolsâ. > > Feedback welcome :) >

Jan. 21, 2016

Re: [Pharo-dev] [ANN] GitHub API Bindings: new version

by Skip Lentz

Hi Mariano, 1) By default it lists the repositories of which you are 1. the owner, 2. a collaborator and 3. an organization member. So even though you might not contribute to some projects, they are shown in there because you are member of the organization which owns it. I opened an issue for allowing filters in the bindings when listing repositories: https://github.com/Balletie/GitHub/issues/26 <https://github.com/Balletie/GitHub/issues/26>. 2) Thereâs an open issue in the repository for implementing pagination. See here: https://github.com/Balletie/GitHub/issues/1 <https://github.com/Balletie/GitHub/issues/1>. Right now, not all repositories are shown because another request should be made to the API for the next âpageâ of results, like in the web UI. The same holds for commits by the way: not all commits in the log of the tool are shown because pagination has to be implemented. Would be cool to use something like FastTable or FastTree to load new pages on the fly. Hope I answered your questions :) Skip > On Jan 21, 2016, at 12:40 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > Hi Skip, > > Very cool! Thanks! > BTW, I am trying the UI tool and I found 2 problems: > > 1) It lists projects that I have nothing to do with them > 2) It does not list some of MY projects > > Am I doing something wrong? > > On Thu, Jan 21, 2016 at 8:18 AM, Dimitris Chloupis <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: > As usual I can only agree with Sven, this is documentation is for seminars how to write proper documentation. Great work, will give it a try :) > > On Thu, Jan 21, 2016 at 1:03 PM Skip Lentz <skip.lentz(a)inria.fr <mailto:skip.lentz@inria.fr>> wrote: > Thanks for the kind words :). > If you feel like thereâs some doc missing I will write something for it, just tell me. > > > On Jan 21, 2016, at 11:46 AM, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: > > > > Wow, great work, beautiful documentation. > > > > An excellent example of the right way to do a Pharo add-on library ! > > > > Thank you. > > > >> On 21 Jan 2016, at 11:30, Skip Lentz <skip.lentz(a)inria.fr <mailto:skip.lentz@inria.fr>> wrote: > >> > >> Hi everyone, > >> > >> I am announcing a new version for the API bindings to GitHub in Pharo. > >> For documentation and information on how to load it, see the new project homepage: > >> > >> https://balletie.github.io/GitHub/ <https://balletie.github.io/GitHub/> (generated with Pillar. Plug for Damien and Cyril) > >> > >> For a list of changes in this release, follow this link: https://github.com/Balletie/GitHub/releases/tag/v0.5 <https://github.com/Balletie/GitHub/releases/tag/v0.5> > >> > >> To load absolutely everything, including the tests and the tool, evaluate: > >> > >> Metacello new > >> baseline: 'GitHub'; > >> repository: 'github://Balletie/GitHub:master'; > >> load: #(tests tool) > >> > >> If you have loaded the tool, it can be opened via the world menu, under âToolsâ. > >> > >> Feedback welcome :) > > > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/>

Jan. 21, 2016

Re: [Pharo-dev] [ANN] GitHub API Bindings: new version

by Mariano Martinez Peck

Hi Skip, Very cool! Thanks! BTW, I am trying the UI tool and I found 2 problems: 1) It lists projects that I have nothing to do with them 2) It does not list some of MY projects Am I doing something wrong? On Thu, Jan 21, 2016 at 8:18 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > As usual I can only agree with Sven, this is documentation is for seminars > how to write proper documentation. Great work, will give it a try :) > > On Thu, Jan 21, 2016 at 1:03 PM Skip Lentz <skip.lentz(a)inria.fr> wrote: > >> Thanks for the kind words :). >> If you feel like thereâs some doc missing I will write something for it, >> just tell me. >> >> > On Jan 21, 2016, at 11:46 AM, Sven Van Caekenberghe <sven(a)stfx.eu> >> wrote: >> > >> > Wow, great work, beautiful documentation. >> > >> > An excellent example of the right way to do a Pharo add-on library ! >> > >> > Thank you. >> > >> >> On 21 Jan 2016, at 11:30, Skip Lentz <skip.lentz(a)inria.fr> wrote: >> >> >> >> Hi everyone, >> >> >> >> I am announcing a new version for the API bindings to GitHub in Pharo. >> >> For documentation and information on how to load it, see the new >> project homepage: >> >> >> >> https://balletie.github.io/GitHub/ (generated with Pillar. Plug for >> Damien and Cyril) >> >> >> >> For a list of changes in this release, follow this link: >> https://github.com/Balletie/GitHub/releases/tag/v0.5 >> >> >> >> To load absolutely everything, including the tests and the tool, >> evaluate: >> >> >> >> Metacello new >> >> baseline: 'GitHub'; >> >> repository: 'github://Balletie/GitHub:master'; >> >> load: #(tests tool) >> >> >> >> If you have loaded the tool, it can be opened via the world menu, >> under âToolsâ. >> >> >> >> Feedback welcome :) >> > >> > >> >> >> -- Mariano http://marianopeck.wordpress.com

Jan. 21, 2016

[ANN] Bounties for Pharo

by marcus.denker＠inria.fr

Hello, We have set up a Bountysource Team for Pharo. This means that everyone can suggest bounties or contribute money to existing bounties. Have a look here: https://www.bountysource.com/teams/pharo Existing bounties can be found here: https://www.bountysource.com/teams/pharo/issues New bounties can be created by adding an issue to the issue tracker here: https://github.com/pharo-project/pharo-bounties/issues To learn more about bounty source, see https://github.com/bountysource/core/wiki/Frequently-Asked-Questions Even though a service from the same website, this is separate of the Salt âgive money per monthâ announced earlier: bounties are solely between the people funding and the person solving the issue (the bounty hunter). So putting money on a bounty does not give it to the Pharo Association, instead it stays there waiting for someone to solve the issue, and is payed to the âbounty hunterâ in case of success. Marcus

Jan. 21, 2016

Re: [Pharo-dev] [ANN] GitHub API Bindings: new version

by Dimitris Chloupis

As usual I can only agree with Sven, this is documentation is for seminars how to write proper documentation. Great work, will give it a try :) On Thu, Jan 21, 2016 at 1:03 PM Skip Lentz <skip.lentz(a)inria.fr> wrote: > Thanks for the kind words :). > If you feel like thereâs some doc missing I will write something for it, > just tell me. > > > On Jan 21, 2016, at 11:46 AM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > > > Wow, great work, beautiful documentation. > > > > An excellent example of the right way to do a Pharo add-on library ! > > > > Thank you. > > > >> On 21 Jan 2016, at 11:30, Skip Lentz <skip.lentz(a)inria.fr> wrote: > >> > >> Hi everyone, > >> > >> I am announcing a new version for the API bindings to GitHub in Pharo. > >> For documentation and information on how to load it, see the new > project homepage: > >> > >> https://balletie.github.io/GitHub/ (generated with Pillar. Plug for > Damien and Cyril) > >> > >> For a list of changes in this release, follow this link: > https://github.com/Balletie/GitHub/releases/tag/v0.5 > >> > >> To load absolutely everything, including the tests and the tool, > evaluate: > >> > >> Metacello new > >> baseline: 'GitHub'; > >> repository: 'github://Balletie/GitHub:master'; > >> load: #(tests tool) > >> > >> If you have loaded the tool, it can be opened via the world menu, under > âToolsâ. > >> > >> Feedback welcome :) > > > > > > >

Jan. 21, 2016

Re: [Pharo-dev] [ANN] GitHub API Bindings: new version

by Skip Lentz

Thanks for the kind words :). If you feel like thereâs some doc missing I will write something for it, just tell me. > On Jan 21, 2016, at 11:46 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Wow, great work, beautiful documentation. > > An excellent example of the right way to do a Pharo add-on library ! > > Thank you. > >> On 21 Jan 2016, at 11:30, Skip Lentz <skip.lentz(a)inria.fr> wrote: >> >> Hi everyone, >> >> I am announcing a new version for the API bindings to GitHub in Pharo. >> For documentation and information on how to load it, see the new project homepage: >> >> https://balletie.github.io/GitHub/ (generated with Pillar. Plug for Damien and Cyril) >> >> For a list of changes in this release, follow this link: https://github.com/Balletie/GitHub/releases/tag/v0.5 >> >> To load absolutely everything, including the tests and the tool, evaluate: >> >> Metacello new >> baseline: 'GitHub'; >> repository: 'github://Balletie/GitHub:master'; >> load: #(tests tool) >> >> If you have loaded the tool, it can be opened via the world menu, under âToolsâ. >> >> Feedback welcome :) > >

Jan. 21, 2016

Re: [Pharo-dev] [ANN] GitHub API Bindings: new version

by Sven Van Caekenberghe

Wow, great work, beautiful documentation. An excellent example of the right way to do a Pharo add-on library ! Thank you. > On 21 Jan 2016, at 11:30, Skip Lentz <skip.lentz(a)inria.fr> wrote: > > Hi everyone, > > I am announcing a new version for the API bindings to GitHub in Pharo. > For documentation and information on how to load it, see the new project homepage: > > https://balletie.github.io/GitHub/ (generated with Pillar. Plug for Damien and Cyril) > > For a list of changes in this release, follow this link: https://github.com/Balletie/GitHub/releases/tag/v0.5 > > To load absolutely everything, including the tests and the tool, evaluate: > > Metacello new > baseline: 'GitHub'; > repository: 'github://Balletie/GitHub:master'; > load: #(tests tool) > > If you have loaded the tool, it can be opened via the world menu, under âToolsâ. > > Feedback welcome :)

Jan. 21, 2016

[ANN] GitHub API Bindings: new version

by Skip Lentz

Hi everyone, I am announcing a new version for the API bindings to GitHub in Pharo. For documentation and information on how to load it, see the new project homepage: https://balletie.github.io/GitHub/ <https://balletie.github.io/GitHub/> (generated with Pillar. Plug for Damien and Cyril) For a list of changes in this release, follow this link: https://github.com/Balletie/GitHub/releases/tag/v0.5 <https://github.com/Balletie/GitHub/releases/tag/v0.5> To load absolutely everything, including the tests and the tool, evaluate: Metacello new baseline: 'GitHub'; repository: 'github://Balletie/GitHub:master'; load: #(tests tool) If you have loaded the tool, it can be opened via the world menu, under âToolsâ. Feedback welcome :)

Jan. 21, 2016

Re: [Pharo-dev] Bad layoutFrame>>#hash

by Henrik Nergaard

What about something like this? ^self species hash hashComposer add: leftFraction; add: leftOffset; add: topFraction; add: topOffset; add: rightOffset; add: bottomFraction; add: bottomOffset HashComposer>>#add: anObject ^hash := (hash + anObject hash) hashMultiply Best regards, Henrik -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Stephan Eggermont Sent: Wednesday, January 13, 2016 8:34 PM To: pharo-dev(a)lists.pharo.org Subject: Re: [Pharo-dev] Bad layoutFrame>>#hash On 13-01-16 18:38, David Allouche wrote: > Why did you use a single expression instead of using a temporary variable? I find it harder to understand. I did find it very slightly easier to understand. It is not a strong opinion however. The ideomatic smalltalk would be ^#(leftFraction leftOffset topFraction topOffset rightFraction rightOffset bottomFraction bottomOffset) inject: self species hash into: [:hashValue :selector | (hashValue + self perform: selector) hashMultiply ] but that would be slower. I would be tempted to add a binary message Integer>>+** aNumber ^(aNumber +self hash) hashMultiply (I'd prefer +#*, but that doesn't parse) hash ^self species hash +** leftFraction +** leftOffset +** topFraction +** topOffset +** rightFraction +** rightOffset +** bottomFraction +** bottomOffset Stephan

Jan. 21, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50538 Home: https://github.com/pharo-project/pharo-core

Jan. 21, 2016