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

[Skip Lentz]

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

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

[Ben Coman]

On Mon, Nov 23, 2015 at 11:25 PM, Skip Lentz  wrote:
> Hi everyone,
>
> As part of my internship I am creating bindings to the GitHub API in Pharo.

Sounds cool.  Do you mean the REST api?  Can you provide a link to the API docs?
cheers -ben

> 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

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

[Yuriy Tymchuk]

The project can be loaded like this:

Metacello new
smalltalkhubUser: #Balletie project: #GitHub;
configuration: #GitHub;
version: #development;
load: #tool

> On 23 Nov 2015, at 16:37, Skip Lentz  wrote:
> 
> 
>> On Nov 23, 2015, at 4:34 PM, Ben Coman  wrote:
>> 
>> On Mon, Nov 23, 2015 at 11:25 PM, Skip Lentz  wrote:
>>> Hi everyone,
>>> 
>>> As part of my internship I am creating bindings to the GitHub API in Pharo.
>> 
>> Sounds cool.  Do you mean the REST api?  Can you provide a link to the API 
>> docs?
> 
> Yes, the REST API. Here you go: https://developer.github.com/v3/

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

[Skip Lentz]

> On Nov 23, 2015, at 4:34 PM, Ben Coman  wrote:
> 
> On Mon, Nov 23, 2015 at 11:25 PM, Skip Lentz  wrote:
>> Hi everyone,
>> 
>> As part of my internship I am creating bindings to the GitHub API in Pharo.
> 
> Sounds cool.  Do you mean the REST api?  Can you provide a link to the API 
> docs?

Yes, the REST API. Here you go: https://developer.github.com/v3/

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

[Yuriy Tymchuk]

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.

Cheers.
Uko

> On 23 Nov 2015, at 16:42, Yuriy Tymchuk  wrote:
> 
> The project can be loaded like this:
> 
> Metacello new
>   smalltalkhubUser: #Balletie project: #GitHub;
>   configuration: #GitHub;
>   version: #development;
>   load: #tool
> 
>> On 23 Nov 2015, at 16:37, Skip Lentz  wrote:
>> 
>> 
>>> On Nov 23, 2015, at 4:34 PM, Ben Coman  wrote:
>>> 
>>> On Mon, Nov 23, 2015 at 11:25 PM, Skip Lentz  wrote:
 Hi everyone,
 
 As part of my internship I am creating bindings to the GitHub API in Pharo.
>>> 
>>> Sounds cool.  Do you mean the REST api?  Can you provide a link to the API 
>>> docs?
>> 
>> Yes, the REST API. Here you go: https://developer.github.com/v3/
> 
> 

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

[Skip Lentz]

> On Nov 23, 2015, at 4:46 PM, Yuriy Tymchuk  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).

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..

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

[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.

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

[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 
> 
> 
> 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

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

[Yuriy Tymchuk]

> On 23 Nov 2015, at 16:55, Skip Lentz  wrote:
> 
> 
>> On Nov 23, 2015, at 4:46 PM, Yuriy Tymchuk  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..

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

[Yuriy Tymchuk]

> On 23 Nov 2015, at 17:31, Peter Uhnak  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 
>> 
>> 
>> 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
> 

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

[Skip Lentz]

> On Nov 23, 2015, at 5:31 PM, Peter Uhnak  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 
>> 
>> 
>> 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.

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

[Skip Lentz]

> On Nov 23, 2015, at 5:32 PM, Yuriy Tymchuk  wrote:
> 
> 
>> On 23 Nov 2015, at 16:55, Skip Lentz  wrote:
>> 
>> 
>>> On Nov 23, 2015, at 4:46 PM, Yuriy Tymchuk  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?

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

[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

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

[Skip Lentz]

> On Nov 23, 2015, at 5:32 PM, Yuriy Tymchuk  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).

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

[Skip Lentz]

> On Nov 23, 2015, at 6:32 PM, Thierry Goubier  
> 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.

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

[Thierry Goubier]

Le 23/11/2015 18:40, Skip Lentz a écrit :



On Nov 23, 2015, at 6:32 PM, Thierry Goubier  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

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

[Sven Van Caekenberghe]

Yes, this is a cool project/approach.

I personally love it that it does not require a plugin and/or library that 
might not exist on all platforms.

Please keep going !

Sven

> On 23 Nov 2015, at 18:32, Thierry Goubier  wrote:
> 
> 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
> 
> 

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

[Yuriy Tymchuk]

Hi Skip,

The receiver is GHRepository.

Cheers.
Uko

> On 23 Nov 2015, at 17:46, Skip Lentz  wrote:
> 
>> 
>> On Nov 23, 2015, at 5:32 PM, Yuriy Tymchuk  wrote:
>> 
>> 
>>> On 23 Nov 2015, at 16:55, Skip Lentz  wrote:
>>> 
>>> 
 On Nov 23, 2015, at 4:46 PM, Yuriy Tymchuk  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?

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

[Dale Henrichs]

Very interesting ... if you put your project up on github, I would fork 
it and port it to tODE as this is something that has been on my todo 
list for awhile:)


Dale

On 11/23/2015 07:25 AM, 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

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

Re: [Pharo-users] Pharo for Data Visualization

[Volkert]

I have seen this ... looks promising.

Do we have a tutorial? i found only http://woden.ronie.cl.

What about mouse control and object selection. It that possible?

BW,
Volkert

On 22.11.2015 21:10, Alexandre Bergel wrote:

We have also put quite some effort on Woden, a 3d engine for Pharo…

Cheers,
Alexandre



On Nov 22, 2015, at 2:56 PM, Dimitris Chloupis  wrote:

its possible via my Ephestos project, to render to video or real time but the 
project is still very much a WIP. Its doable but require some python knowledge 
and knowledge of Blender UI and API. I will be making a true Pharo API for it 
fairly soon but as you can imagine these things take time.

On Sun, Nov 22, 2015 at 6:35 PM Volkert  wrote:
Is this possible with Pharo?

http://www.asterank.com/3d/

BW,
Volkert

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

[Alexandre Bergel]

Thanks Uko for trying 

Alexandre 


> Le 23 nov. 2015 à 13:32, Yuriy Tymchuk  a écrit :
> 
> 
>> On 23 Nov 2015, at 16:55, Skip Lentz  wrote:
>> 
>> 
>>> On Nov 23, 2015, at 4:46 PM, Yuriy Tymchuk  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..
> 
> 

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

[Alexandre Bergel]

Yes, keep going

Alexandre 

> Le 23 nov. 2015 à 15:05, Sven Van Caekenberghe  a écrit :
> 
> Yes, this is a cool project/approach.
> 
> I personally love it that it does not require a plugin and/or library that 
> might not exist on all platforms.
> 
> Please keep going !
> 
> Sven
> 
>> On 23 Nov 2015, at 18:32, Thierry Goubier  wrote:
>> 
>> 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
> 
> 

[Pharo-users] piping output from shell process to transcript

[Peter Uhnak]

Hi,

how can I pipe output from PipeableOSProcess to Transcript?

I tried doing:

(PipeableOSProcess command: 'my-command.sh') outputOn: Transcript.

However `#outputOn:` doesn't send `#endEntry` so I don't see anything,
and even if it would, the output is delivered there at the end anyway.

I would like to see the live result of the running commands.

Thanks,

-- 
Peter

Re: [Pharo-users] piping output from shell process to transcript

[john pfersich]

Try this:

| p |
p:= (PipeableOSProcess waitForCommand: 'whoami').
Transcript show: (p output).



On Mon, Nov 23, 2015 at 6:42 PM, Peter Uhnak  wrote:

> Hi,
>
> how can I pipe output from PipeableOSProcess to Transcript?
>
> I tried doing:
>
> (PipeableOSProcess command: 'my-command.sh') outputOn: Transcript.
>
> However `#outputOn:` doesn't send `#endEntry` so I don't see anything,
> and even if it would, the output is delivered there at the end anyway.
>
> I would like to see the live result of the running commands.
>
> Thanks,
>
> --
> Peter
>
>

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

[stepharo]

Hi thierry

Skip is working on a code review tool :)
and we decided after the experience of Griotte from thomas not to build 
our own again but interface with existing hence

we chose git and github like tools.
We want to support code review (publish metadata) on a publish code.

Stef


Le 23/11/15 18:55, Thierry Goubier a écrit :

Le 23/11/2015 18:40, Skip Lentz a écrit :


On Nov 23, 2015, at 6:32 PM, Thierry Goubier 
 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

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

[Julien Delplanque]

Awesome, I'll use it soon :)

On 23/11/15 16:25, 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 


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