Enabling remote access is an important next step but I haven't yet done any 
work in that area. 
I just checked out the github API and they give very convenient access to any 
object of a repository via JSON. So it should be pretty straight forward to tap 
github. What is probably not as easy is a more general approach with Git only. 
The design of Git is such that it is expected of a user to clone a repository 
(or part of it) to read / manipulate data. 
One solution there might be (I'm not 100% sure) to clone "on the fly", i.e. 
only clone the data explicitly requested. The data would then of course 
accumulate locally and also I don't know how performance would hold up for such 
an approach.

I'll defenitely try to come up with something to access github soon. It will 
probably not use OB though because that's just too much of a hack. Especially 
because it effectively disables the version browser for changes files.

Any suggestions are of course appreciated.

Cheers,
Max


On 15.03.2011, at 12:10, Adrian Lienhard wrote:

> Wow, very cool!
> 
> Just for others to realize what this is...
> 
> Let's assume you want to see the change history of HTTPSocket 
> class>>httpGetDocument:args:accept:request:. With blame you can see for each 
> line who changed it and when:
> 
> https://github.com/pharogenesis/pharogenesis/blame/pharo/HTTPSocket/class/get%20the%20page/httpGetDocument-3A-args-3A-accept-3A-request-3A-.cs
> 
> Or you can see diffs between particular versions. E.g., httpFileIn: was 
> changed in 2005 as follows:
> 
> https://github.com/pharogenesis/pharogenesis/commit/d88d2b9c9fdb234c7d6b977e513561a8d45d1c04#HTTPSocket/class/get
>  the page/httpFileIn-3A-.cs
> 
> 
> Could the method versions dialog be extended to grab this data from GitHub?
> 
> Cheers,
> Adrian
> 
> 
> On Mar 15, 2011, at 10:22 , Max Leske wrote:
> 
>> I just pushed the (hopefully) final version of Pharogenesis to github 
>> (github.com/pharogenesis/pharogenesis). I appologize to the followers for 
>> deleting and recreating the repository but that's the only way to keep the 
>> history clean.
>> 
>> Max
> 
> 


Reply via email to