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

2015-12-02 Thread stepharo
Why could not I publish code to a fossil repo using the same "conceptual" commands than git? Same question for Mercurial. So we are talking about abstraction over low-level APIs. Basic engineering practices. This is what we are doing with Athens (do not expose Cairo to the complete system)

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

2015-12-02 Thread stepharo
+ 1 It is about abstraction. Le 30/11/15 10:06, Christophe Demarey a écrit : Hi, Le 29 nov. 2015 à 20:00, Dimitris Chloupis a écrit : And there lies the trap. If you end up making something that works with everything, you will create something that just works with everything instead of

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

2015-11-30 Thread Christophe Demarey
Hi, Le 29 nov. 2015 à 20:00, Dimitris Chloupis a écrit : > And there lies the trap. > > If you end up making something that works with everything, you will create > something that just works with everything instead of something that works > very well with one thing. could be. But we do not

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

2015-11-30 Thread EuanM
Well, personally, I far prefer Mercurial. Which also dethroned SVN. Mercurial has all the power of Git, while providing a more usable API. My mind works like a Smalltalker's, not like Linus's. It's true, some of the more abstruse functions of git require a longer chain of user actions in

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

2015-11-30 Thread EuanM
We want a system of small objects with loose-coupling, and simple webs of message-sends. This allows us power, flexibility, maintainability *and* the opportunity to accommodate new requirements. We always need to bear this in mind. Build for the inevitable changes of environment and changes of

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

2015-11-30 Thread Offray Vladimir Luna Cárdenas
Hi, On 29/11/15 14:00, Dimitris Chloupis wrote: And there lies the trap. If you end up making something that works with everything, you will create something that just works with everything instead of something that works very well with one thing. Right now Git is by very far the undisputed

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

2015-11-30 Thread Offray Vladimir Luna Cárdenas
Hi, On 30/11/15 12:34, Dimitris Chloupis wrote: let me give you the thinking of someone that comes from another language "What is this ? Ah Pharo What features it has ? Ah thats some nice cool features, live coding looks sweet How about version control ? Hmm no its too weak and their website

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

2015-11-30 Thread Dimitris Chloupis
just for the usual note, thats my personal opinion and in no way try to discourage people just offer a different perspective to this. I always welcome any effort to improve pharo in any way, even for ways I dont care about so much. So keep up the amazing work you guys are doing with Pharo. On

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

2015-11-30 Thread Dimitris Chloupis
let me give you the thinking of someone that comes from another language "What is this ? Ah Pharo What features it has ? Ah thats some nice cool features, live coding looks sweet How about version control ? Hmm no its too weak and their website for hosting repos is problematic in many cases Maybe

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

2015-11-29 Thread Dimitris Chloupis
And there lies the trap. If you end up making something that works with everything, you will create something that just works with everything instead of something that works very well with one thing. Right now Git is by very far the undisputed king of version control and has completely dethroned

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

2015-11-29 Thread stepharo
What I would like for Pharo is to avoid to be bound to a given back-end for its versionning. This master is a step in the right direction http://www.hpi.uni-potsdam.de/fileadmin/hpi/source/Technische_Berichte/HPI_54.pdf Stef

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

2015-11-24 Thread Thierry Goubier
Hi Skip, Trying here, especially interested to see how it handles metadata-less filetree. - I have no authentification issues (but I had the feeling the GUI wasn't working for a little while) - I don't get all my repositories (well, in practice allmost none, however I get all the pharo books),

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

2015-11-23 Thread 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

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

2015-11-23 Thread 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: >>> >>>

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

2015-11-23 Thread 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

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

2015-11-23 Thread 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

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

2015-11-23 Thread 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

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

2015-11-23 Thread 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,

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

2015-11-23 Thread 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

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

2015-11-23 Thread 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

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

2015-11-23 Thread 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

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

2015-11-23 Thread 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

2015-11-23 Thread 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

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

2015-11-23 Thread 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

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

2015-11-23 Thread 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

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

2015-11-23 Thread 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

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

2015-11-23 Thread 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

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

2015-11-23 Thread 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”

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

2015-11-23 Thread 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?

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

2015-11-23 Thread 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

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

2015-11-23 Thread 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