November 2015 - Pharo-users

Re: [Pharo-users] Basic versioning of GitHub repositories from within Pharo

by Thierry Goubier

Le 23/11/2015 18:40, Skip Lentz a Ã©crit : > >> On Nov 23, 2015, at 6:32 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >> >> Hi Skip, >> >> this is interesting. It would mean the ability to handle github issues querying/opening inside Pharo, no? > > Yes, if that part of the API is implemented. There are still a lot of extensions to be made. > I am planning to implement the bindings for pull requests in the near future. It would be very cool to be able to envision a git + pharo combination where going on the github website wouldn't be necessary. Creating and commenting on an issue directly from inside Pharo instead of logging in fogbugz... Commenting on a commit from inside Pharo... Would you be able to retrieve the same information from github that GitFileTree does when it extract package version history information? Thierry

Nov. 23, 2015

Re: [Pharo-users] Basic versioning of GitHub repositories from within Pharo

by Skip Lentz

> On Nov 23, 2015, at 6:32 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Hi Skip, > > this is interesting. It would mean the ability to handle github issues querying/opening inside Pharo, no? Yes, if that part of the API is implemented. There are still a lot of extensions to be made. I am planning to implement the bindings for pull requests in the near future.

Nov. 23, 2015

Re: [Pharo-users] Basic versioning of GitHub repositories from within Pharo

by Skip Lentz

> On Nov 23, 2015, at 5:32 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Ok, when I enter a username and password, I get "receiver of asDateAndTime is nilâ in #setDateAndTimeMapping:. I also debugged this and it appears to be a corner case for some repositories where the âpushed_atâ field is null for whatever reason. I did a commit which should fix this (It just checks if the field is nil).

Nov. 23, 2015

Re: [Pharo-users] Basic versioning of GitHub repositories from within Pharo

by Thierry Goubier

Hi Skip, this is interesting. It would mean the ability to handle github issues querying/opening inside Pharo, no? Thierry Le 23/11/2015 16:25, Skip Lentz a Ã©crit : > Hi everyone, > > As part of my internship I am creating bindings to the GitHub API in Pharo. > As a prototype and demo, I have created a small tool last week to do > some basic versioning, namely checking out a version, committing a > version and showing a log of commits along with a branch tree. > > Hereâs a screenshot: http://i.imgur.com/iMfWOvp.png > > The repository of the bindings and the tool is here: > http://smalltalkhub.com/#!/~Balletie/GitHub > To load the tool into your image, execute: > > (ConfigurationOfGitHub project version: #development) load: #tool > > Keep in mind that this is tied to GitHub, since internally it uses the > API. A nice side effect of this is that everything can be done > in-memory. That is, thereâs no local copy on the filesystem. One does > not even need git installed. > > That being said, feel free to take off with my prototype and make it > work with e.g. the LibGit bindings in Pharo. > > Known bug: > - When selecting a different repository from the dropdown while a > version is also selected in the log, one gets a DNU. To work around this > for the time being, just deselect the version before you switch > repositories. > > Let me know what you think and feel free to ask some questions. > > Skip

Nov. 23, 2015

Re: [Pharo-users] Basic versioning of GitHub repositories from within Pharo

by Skip Lentz

> On Nov 23, 2015, at 5:32 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > >> On 23 Nov 2015, at 16:55, Skip Lentz <skip.lentz(a)inria.fr> wrote: >> >> >>> On Nov 23, 2015, at 4:46 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>> >>> Is there any guide on how to use it? Iâve opened the tool, entered a username, left out the password field blank. Then I get nil exception because `self avatarUrl` of GHLoggedInUser returns nil. >> >> Ah yes, that part might not be clear. The idea is that you can either enter a username and password, or enter an access token for the API and leave the password field blank. I wasnât really sure how to convey that in the UI, perhaps this made it even more vague. >> >> After youâve entered the login details, the repositories you own are loaded into the dropdown list and a log is shown with the last 25 commits (yes, itâs limited to that for now). > > Ok, when I enter a username and password, I get "receiver of asDateAndTime is nilâ in #setDateAndTimeMapping:. > > (should it work on Pharo 5?) Hmm yes it should work in Pharo 5. I didnât get this error yet. Can you tell me what the receiver is of #setDateAndTimeMapping: when it occurs?

Nov. 23, 2015

Re: [Pharo-users] Basic versioning of GitHub repositories from within Pharo

by Skip Lentz

> On Nov 23, 2015, at 5:31 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > On Mon, Nov 23, 2015 at 04:25:28PM +0100, Skip Lentz wrote: >> Hi everyone, >> >> As part of my internship I am creating bindings to the GitHub API in Pharo. >> As a prototype and demo, I have created a small tool last week to do some basic versioning, namely checking out a version, committing a version and showing a log of commits along with a branch tree. >> >> Hereâs a screenshot: http://i.imgur.com/iMfWOvp.png <http://i.imgur.com/iMfWOvp.png> >> >> The repository of the bindings and the tool is here: http://smalltalkhub.com/#!/~Balletie/GitHub >> To load the tool into your image, execute: >> >> (ConfigurationOfGitHub project version: #development) load: #tool >> >> Keep in mind that this is tied to GitHub, since internally it uses the API. A nice side effect of this is that everything can be done in-memory. > > Do you have any plans to eventually make a "Git Tool" out of it, rather > than GitHub Tool? Who knows, I like the idea of it. Again, itâs a prototype/demo/experiment of a versioning tool other than Monticello within Pharo. It didnât take much time to create, so I decided to just try it out. > Why is it tied to GitHub in the first place? Are you planning to support > some github-specific features like issue tracker, etc? Because not being > able to have git repo localy is actually a hindrance and not a "nice > side effect" (unless of course you are using git as monticello). For my project I needed to implement the API bindings to open pull requests. I saw this as another use case of the API and decided to experiment with it, thatâs all really.

Nov. 23, 2015

Re: [Pharo-users] Basic versioning of GitHub repositories from within Pharo

by Yuriy Tymchuk

> On 23 Nov 2015, at 17:31, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > On Mon, Nov 23, 2015 at 04:25:28PM +0100, Skip Lentz wrote: >> Hi everyone, >> >> As part of my internship I am creating bindings to the GitHub API in Pharo. >> As a prototype and demo, I have created a small tool last week to do some basic versioning, namely checking out a version, committing a version and showing a log of commits along with a branch tree. >> >> Hereâs a screenshot: http://i.imgur.com/iMfWOvp.png <http://i.imgur.com/iMfWOvp.png> >> >> The repository of the bindings and the tool is here: http://smalltalkhub.com/#!/~Balletie/GitHub >> To load the tool into your image, execute: >> >> (ConfigurationOfGitHub project version: #development) load: #tool >> >> Keep in mind that this is tied to GitHub, since internally it uses the API. A nice side effect of this is that everything can be done in-memory. > > Do you have any plans to eventually make a "Git Tool" out of it, rather > than GitHub Tool? > > Why is it tied to GitHub in the first place? Are you planning to support I think that itâs tied to github because there are nice api. The goal is not to have a tool that helps you to work with git, but the one that allows you to browse git repos. This is a nice small project that can be a part of some larger one. > some github-specific features like issue tracker, etc? Because not being > able to have git repo localy is actually a hindrance and not a "nice > side effect" (unless of course you are using git as monticello). > > Peter >

Nov. 23, 2015

Re: [Pharo-users] Basic versioning of GitHub repositories from within Pharo

by Yuriy Tymchuk

> On 23 Nov 2015, at 16:55, Skip Lentz <skip.lentz(a)inria.fr> wrote: > > >> On Nov 23, 2015, at 4:46 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> Is there any guide on how to use it? Iâve opened the tool, entered a username, left out the password field blank. Then I get nil exception because `self avatarUrl` of GHLoggedInUser returns nil. > > Ah yes, that part might not be clear. The idea is that you can either enter a username and password, or enter an access token for the API and leave the password field blank. I wasnât really sure how to convey that in the UI, perhaps this made it even more vague. > > After youâve entered the login details, the repositories you own are loaded into the dropdown list and a log is shown with the last 25 commits (yes, itâs limited to that for now). Ok, when I enter a username and password, I get "receiver of asDateAndTime is nilâ in #setDateAndTimeMapping:. (should it work on Pharo 5?) Cheers. Uko > > One can then select a version and click checkout to load the packages listed on the right into the image. If all goes well you should see an arrow pointing at the currently loaded version in the list. After having done some changes, one can click commit which opens a Komitter window. (Committing is the least stable at the moment). > > It would be nice to be able to select and checkout versions without having to enter your username and password, but at the moment thatâs not supported..

Nov. 23, 2015

Re: [Pharo-users] Basic versioning of GitHub repositories from within Pharo

by Peter Uhnak

On Mon, Nov 23, 2015 at 04:25:28PM +0100, Skip Lentz wrote: > Hi everyone, > > As part of my internship I am creating bindings to the GitHub API in Pharo. > As a prototype and demo, I have created a small tool last week to do some basic versioning, namely checking out a version, committing a version and showing a log of commits along with a branch tree. > > Hereâs a screenshot: http://i.imgur.com/iMfWOvp.png <http://i.imgur.com/iMfWOvp.png> > > The repository of the bindings and the tool is here: http://smalltalkhub.com/#!/~Balletie/GitHub > To load the tool into your image, execute: > > (ConfigurationOfGitHub project version: #development) load: #tool > > Keep in mind that this is tied to GitHub, since internally it uses the API. A nice side effect of this is that everything can be done in-memory. Do you have any plans to eventually make a "Git Tool" out of it, rather than GitHub Tool? Why is it tied to GitHub in the first place? Are you planning to support some github-specific features like issue tracker, etc? Because not being able to have git repo localy is actually a hindrance and not a "nice side effect" (unless of course you are using git as monticello). Peter

Nov. 23, 2015

Re: [Pharo-users] Basic versioning of GitHub repositories from within Pharo

by Skip Lentz

I just committed a fix for when opening a repository with more than 25 commits (which is basically any repository). I already fixed this but did not commit it yet to the repository on smalltalkhub, oops.

Nov. 23, 2015