Re: [Pharo-dev] If all Pharo projects were on GitHub...

Hi Levente, Le 28/09/2015 23:54, Levente Uzonyi a écrit : On Sun, 27 Sep 2015, Ferlicot D. Cyril wrote: An other point is that git file tree will not work on Windows if we do not fix the problem of the stdio. And a lot of people out of the community use Windows, so this is not a issue we

Re: [Pharo-dev] If all Pharo projects were on GitHub...

Well, there is some kind of but I was tired and the stream broke as my internet connection went bust. (and I should have done the full setup). Ah these things pile up. Still, one can see the trainwreck over here: https://www.livecoding.tv/philippeback/videos/ Pick the things with "git" in the

Re: [Pharo-dev] If all Pharo projects were on GitHub...

On Sun, 27 Sep 2015, Ferlicot D. Cyril wrote: Le 27/09/2015 12:11, Dimitris Chloupis a écrit : we have more than a nice Git integration. I have been using Github for my pharo project for over a year now without any issue, the last few months I have been using gitfiltree which is making it even

Re: [Pharo-dev] Reflectivity: Links that de-install themselves (oneShot)

> On 20 Sep 2015, at 16:17, Marcus Denker wrote: > > >> On 19 Sep 2015, at 01:10, stepharo wrote: >> >> Marcus I have a API design question >> >> when you offer >> >> options: #(optionOneShot); >> >> versus >> >> optionOneShot >> >> Do you do a

Re: [Pharo-dev] PharoTouch Demo Video

On 28-09-15 16:22, Marcus Denker wrote: Pharo touch demo with the new OSWindows architecture, touch events, vector graphics using Athens and libsdl2. Thanks the people involved (specifically for the touch project Christopher Coat, Mervan Ougdane, Jan-Baptiste Arnaud, Eric Lepors and Mathieu

[Pharo-dev] [pharo-project/pharo-core] 306d76: 50345

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 306d7616cbcc0f10b4931ae71c3dc296869a8d35 https://github.com/pharo-project/pharo-core/commit/306d7616cbcc0f10b4931ae71c3dc296869a8d35 Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50345 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] If all Pharo projects were on GitHub...

On 9/27/15 11:53 PM, stepharo wrote: Le 27/9/15 15:33, Peter Uhnák a écrit : Because to me git is **really** complex. I do not talk about add push commit but rebase remote Git allows you to do complex things if you need them. But you can easily use git without ever needing

Re: [Pharo-dev] [pharo-project/pharo-core] 07c9a0: 50344

Yes, debug code left. I fixed it already… I should have seen it when going through the diff... > On 28 Sep 2015, at 15:57, Henrik Nergaard wrote: > > Yeah, that might be my mistake. > Looking into it now -> loading 16648 changes the color. > > Best regards, > Henrik

Re: [Pharo-dev] If all Pharo projects were on GitHub...

> On 28 Sep 2015, at 04:27, Ben Coman wrote: > > On Sun, Sep 27, 2015 at 8:59 PM, Esteban Lorenzano > wrote: >> Hi, >> >> I’ve been using git for all my projects since more than one year now, and >> frankly I found it really good… and the pull

Re: [Pharo-dev] If all Pharo projects were on GitHub...

2015-09-28 8:53 GMT+02:00 stepharo : > > > Le 27/9/15 15:33, Peter Uhnák a écrit : > > Because to me git is **really** complex. I do not talk about add push >> commit but rebase remote >> > > Git allows you to do complex things if you need them. > But you can easily use git

Re: [Pharo-dev] If all Pharo projects were on GitHub...

> > sure except that suddenly you do not know why you have to know the arcanes >> part. >> I think that git is not layered so you get exposed to a lot of details >> even when you avoid. >> > Hmm, I don't see that, but I've been using git for many years so I am not in position to judge it how

Re: [Pharo-dev] If all Pharo projects were on GitHub...

Le 28/09/2015 04:27, Ben Coman a écrit : I have a vague recollection that the problem was a particular file where data changed each commit and having the idea that this might be solved by: each commit writing metadata to a different file e.g. .metadata, and Monticello knows to pick up the

Re: [Pharo-dev] If all Pharo projects were on GitHub...

Le 27/9/15 15:33, Peter Uhnák a écrit : Because to me git is **really** complex. I do not talk about add push commit but rebase remote Git allows you to do complex things if you need them. But you can easily use git without ever needing rebase, filter-branch or whatnot.

Re: [Pharo-dev] World.st has a new admin

> On 24 Sep 2015, at 4:27 , Geert Claes wrote: > > The admin duties have now been handed over to Sean DeNigris who kindly > volunteered to look after the www.world.st web presence as well as the > Nabble archived mailing list forums on forum.world.st. > > As mentioned

Re: [Pharo-dev] [Pharo-users] Changing method icons priorities in nautilus

Peter Uhnák writes: > So would it make sense to swap the priority? I agree with you. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Re: [Pharo-dev] If all Pharo projects were on GitHub...

2015-09-28 13:57 GMT+02:00 Ben Coman : > On Mon, Sep 28, 2015 at 2:43 PM, Thierry Goubier > wrote: > > Le 28/09/2015 04:27, Ben Coman a écrit : > >> > >> > >> I have a vague recollection that the problem was a particular file > >> where data

Re: [Pharo-dev] If all Pharo projects were on GitHub...

On Mon, Sep 28, 2015 at 2:43 PM, Thierry Goubier wrote: > Le 28/09/2015 04:27, Ben Coman a écrit : >> >> >> I have a vague recollection that the problem was a particular file >> where data changed each commit and having the idea that this might be >> solved by: each

Re: [Pharo-dev] If all Pharo projects were on GitHub...

On 28-09-15 04:27, Ben Coman wrote: Git is very flexible which implies complexity for newcomers to it. What is required on top of git is a "well defined" workflow.I see sometimes on this mail-list that people design their tools for flexibility since they don't want to *impose* a workflow on

Re: [Pharo-dev] If all Pharo projects were on GitHub...

Video are good. But please, do not show trivial things. Show us an example with several users and conflict resolution. Alexandre > On Sep 28, 2015, at 10:59 AM, Damien Cassou wrote: > > > philippe.b...@highoctane.be writes: > >> It isn't.

Re: [Pharo-dev] If all Pharo projects were on GitHub...

Alexandre Bergel writes: > I have tried several times to use Git for my project. But I do not > want to spend time on configuring .gitattribute and other > configuration file. This does not go in the right direction I believe. > Why is it easier to use git with Java

Re: [Pharo-dev] If all Pharo projects were on GitHub...

philippe.b...@highoctane.be writes: > It isn't. It is actually very easy to use git. > > Time for a video :-) > > Expect that for tomorrow. tomorrow is today :-). We expect it! Thanks Philippe -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the

Re: [Pharo-dev] If all Pharo projects were on GitHub...

> > If there are so many windows users There are many windows users, there are NOT many windows + git users. Probably because everyone gives up on gitfiletree after ten minutes and switch to regular filetree. I think that none of the developers of Git in Pharo / gitfiletree use Windows, so some

Re: [Pharo-dev] If all Pharo projects were on GitHub...

Le 28/09/2015 23:54, Levente Uzonyi a écrit : > > If there are so many windows users, then how can it be that none of them > managed to explain what the actual problem with stdio handling is. I had > asked about the problem a while ago, but I still haven't got an answer: >

[Pharo-dev] TestAsserter>>assertCollection:hasSameElements:

How practical it is to do set-based comparison in TestAsserter>>assertCollection:hasSameElements: ? For example #(1 1 2) has same elements as #(1 2) which may make sense for sets, but not for bags. The main reason I was using it is that in tests the expected collection may be created by hand,

Re: [Pharo-dev] If all Pharo projects were on GitHub...

The big issue for git and windows (in general) is that there is a 255 character limit on the paths for files I recently pruned some file names for Metacello (on a win-hack branch) just to get Metacello to work with filetree .. Working with Github Desktop[1] for Windows makes the

Re: [Pharo-dev] If all Pharo projects were on GitHub...

On 09/28/2015 04:13 PM, Ferlicot D. Cyril wrote: Le 28/09/2015 23:54, Levente Uzonyi a écrit : If there are so many windows users, then how can it be that none of them managed to explain what the actual problem with stdio handling is. I had asked about the problem a while ago, but I still

Re: [Pharo-dev] If all Pharo projects were on GitHub...

On Tue, 29 Sep 2015, Ferlicot D. Cyril wrote: Le 28/09/2015 23:54, Levente Uzonyi a écrit : If there are so many windows users, then how can it be that none of them managed to explain what the actual problem with stdio handling is. I had asked about the problem a while ago, but I still

Re: [Pharo-dev] If all Pharo projects were on GitHub...

Le 28 sept. 2015 à 13:57, Ben Coman a écrit : > On Mon, Sep 28, 2015 at 2:43 PM, Thierry Goubier > wrote: >> Le 28/09/2015 04:27, Ben Coman a écrit : >>> >>> >>> I have a vague recollection that the problem was a particular file >>> where data changed each commit

Re: [Pharo-dev] If all Pharo projects were on GitHub...

On Mon, Sep 28, 2015 at 8:06 PM, Thierry Goubier wrote: > > > 2015-09-28 13:57 GMT+02:00 Ben Coman : >> >> On Mon, Sep 28, 2015 at 2:43 PM, Thierry Goubier >> wrote: >> > Le 28/09/2015 04:27, Ben Coman a écrit : >> >> >>

Re: [Pharo-dev] If all Pharo projects were on GitHub...

> On 28 Sep 2015, at 13:57, Ben Coman wrote: > > On Mon, Sep 28, 2015 at 2:43 PM, Thierry Goubier > wrote: >> Le 28/09/2015 04:27, Ben Coman a écrit : >>> >>> >>> I have a vague recollection that the problem was a particular file >>> where

[Pharo-dev] [pharo-project/pharo-core] 07c9a0: 50344

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 07c9a04969c9a4afbe64c1ca0dabfe5a1bee https://github.com/pharo-project/pharo-core/commit/07c9a04969c9a4afbe64c1ca0dabfe5a1bee Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50344 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] [pharo-project/pharo-core] 07c9a0: 50344

There is some strange side effect that now the menus have a very odd reddish color. I guess this is caused somehow by 16648 or maybe even 16647? I added a new issue tracker entry for that: https://pharo.fogbugz.com/f/cases/16652/Menues-now-have-a-very-strange-reddish-color > Log

Re: [Pharo-dev] [pharo-project/pharo-core] 07c9a0: 50344

Yeah, that might be my mistake. Looking into it now -> loading 16648 changes the color. Best regards, Henrik -Original Message- From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Marcus Denker Sent: Monday, September 28, 2015 3:44 PM To: Pharo Development List