On Thu, Jan 21, 2016 at 9:30 AM, Skip Lentz <[email protected]> wrote:
> 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. > > 2) There’s an open issue in the repository for implementing pagination. > See here: 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 :) > Hi Skip, Yes, thanks, you have answered both questions :) Damn, I want to browse my OSSubprocess repo ahahhaha. Keep the work going! > Skip > > On Jan 21, 2016, at 12:40 PM, Mariano Martinez Peck <[email protected]> > 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 <[email protected]> > 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 <[email protected]> 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 <[email protected]> >>> 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 <[email protected]> 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 > > > -- Mariano http://marianopeck.wordpress.com
