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)
OS
+ 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 som
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 f
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 Mon,
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
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 r
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 Mercuri
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
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 wa
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 S
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
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), s
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 ver
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/1
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
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,
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
Pha
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
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 h
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
extension
> 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
> 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 whatev
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 creat
> 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.
> 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
>> ba
> 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
> 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 GHLoggedI
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 ve
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.
> 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.
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 th
> 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?
Ye
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?
cheers -ben
> As a prototype and demo, I have created a small tool l
34 matches
Mail list logo