Re: [Pharo-dev] Bloc Shock

2017-09-09 Thread Tudor Girba
:) > On Sep 9, 2017, at 7:30 PM, Sean P. DeNigris wrote: > > I was playing with Bloc when I came across the following: > > > I am taken aback by the elegance and utility of this widget, and also aware >

Re: [Pharo-dev] About Git support for windows

2017-09-09 Thread Alexandre Bergel
Hi! I live very very much this idea! I am wondering why do we need the timestamp? Git knows about who has committed each line and by whom. Why should we have some redundant information? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel

[Pharo-dev] Pending FileSystem PRs (was: [Pharo-users] Pharo 6 FileSystem>>changeDirectory: is missing)

2017-09-09 Thread Alistair Grant
Hi Stef, (I've moved this to pharo-dev) On Sat, Sep 09, 2017 at 11:09:55AM +0200, Stephane Ducasse wrote: > Alistair > > did I miss some pending PR to be integrated for FS? I'm not aware of any pending PRs at the moment. The issues that are still open are: - Default Working Directory

Re: [Pharo-dev] About Git support for windows

2017-09-09 Thread Peter Uhnák
> > I don't think it's even a problem > I do remember that I hated long classes because of git conflicts, but I suppose if we have good tooling for that it shouldn't be such a pain. Git can sometimes make the diff really weirdly... Peter

Re: [Pharo-dev] About Git support for windows

2017-09-09 Thread Eliot Miranda
Hi Esteban, > On Sep 9, 2017, at 8:04 AM, Esteban Lorenzano wrote: > > >> On 9 Sep 2017, at 12:28, Henrik Nergaard wrote: >> >> >> but this is still WIP: for example timestamp needs to go to avoid >> >> conflicts. >> why/how would this cause

Re: [Pharo-dev] About Git support for windows

2017-09-09 Thread Eliot Miranda
Hi Esteban, > On Sep 8, 2017, at 7:08 PM, Esteban Lorenzano wrote: > > > >> On 8 Sep 2017, at 22:35, Peter Uhnák wrote: >> >> for example here >> >> https://github.com/estebanlm/pharo-tonel/blob/master/src/Morphic-Core/Morph.class.st >> > but this

[Pharo-dev] Bloc Shock

2017-09-09 Thread Sean P. DeNigris
I was playing with Bloc when I came across the following: I am taken aback by the elegance and utility of this widget, and also aware of all the countless steps we took to have it appear there - Bloc, GT, etc, etc. It feels like

Re: [Pharo-dev] About Git support for windows

2017-09-09 Thread Esteban Lorenzano
> On 9 Sep 2017, at 12:28, Henrik Nergaard wrote: > > >> but this is still WIP: for example timestamp needs to go to avoid > >> conflicts. > why/how would this cause conflicts versus other changes? two people modifying same method could have a marge without conflict, but

Re: [Pharo-dev] STON: SortedCollection Bug?

2017-09-09 Thread Sven Van Caekenberghe
> On 9 Sep 2017, at 15:45, Sean P. DeNigris wrote: > > Sven Van Caekenberghe-2 wrote >> STON cannot serialise block closures. > > Oops, sorry. I see that now: > https://github.com/svenvc/ston/blob/master/ston-paper.md#limitations > > I wonder, in this case, there are no

Re: [Pharo-dev] STON: SortedCollection Bug?

2017-09-09 Thread Sean P. DeNigris
Sven Van Caekenberghe-2 wrote > STON cannot serialise block closures. Oops, sorry. I see that now: https://github.com/svenvc/ston/blob/master/ston-paper.md#limitations I wonder, in this case, there are no references in the block to any objects except its own arguments. Would it be possible to

Re: [Pharo-dev] About Git support for windows

2017-09-09 Thread Henrik Nergaard
>> but this is still WIP: for example timestamp needs to go to avoid conflicts. why/how would this cause conflicts versus other changes? Fra: Pharo-dev på vegne av Esteban Lorenzano Sendt: 9. september

Re: [Pharo-dev] About Git support for windows

2017-09-09 Thread Esteban Lorenzano
> On 8 Sep 2017, at 22:02, Eliot Miranda wrote: > > Hi All, > >> On Sep 8, 2017, at 9:44 AM, Stephane Ducasse wrote: >> >> Hi all >> >> At ESUG we discussed with Esteban, martin mcClure, Dale and (many many >> others :), esteban designed a

Re: [Pharo-dev] Changing pharo default branch to development

2017-09-09 Thread Stephane Ducasse
Thanks you guys! I will remove a lot of mistakes :) I think that when we can simplify without losing anything, it is a clear sign that we should do it. Stef On Sat, Sep 9, 2017 at 10:53 AM, Guillermo Polito wrote: > As we discussed in ESUG, and since this is a cheap

[Pharo-dev] Changing pharo default branch to development

2017-09-09 Thread Guillermo Polito
As we discussed in ESUG, and since this is a cheap change to do in the airport, we are making the development branch in pharo the default branch. This will help avoiding accidental pull requests targeting master instead of development. For those who may ask, we will not remove the master branch

Re: [Pharo-dev] STON: SortedCollection Bug?

2017-09-09 Thread Sven Van Caekenberghe
STON cannot serialise block closures. You would have to get creative to make this work. For SortedCollection, it would only work without a sort block. STON fromString: (STON toString: #(1 2 3) asSortedCollection). > On 9 Sep 2017, at 04:58, Sean P. DeNigris wrote: >