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

On Tue, Sep 12, 2017 at 11:23 PM, Peter Uhnák wrote: > Just a random idea, how about each time writing timestamps to >> a different file name "timestamps.$HashOfClassSourceFile" >> Then git would never complain of a conflict(??). >> > > If I understand your proposal correctly,

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

> > Just a random idea, how about each time writing timestamps to > a different file name "timestamps.$HashOfClassSourceFile" > Then git would never complain of a conflict(??). > If I understand your proposal correctly, that would imo result in the following: accumulating endless list of

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

On Sun, Sep 10, 2017 at 5:06 PM, Esteban Lorenzano wrote: > > On 10 Sep 2017, at 10:56, Henrik-Nergaard wrote: > > Everyone who used filetree with metadata can tell it is super annoying and > > destroys the complete experience. > There has been a fix

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

A note: Both variants below do not look nice because of the code starting at the first column. Some of the method body code lines start in the first column: Morph class>>obtainArrowheadFor: aPrompt defaultValue: defaultPoint [ "Allow the user to supply a point to serve as an arrowhead size.

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

I read all the morph class and I like the ending ] at the beginning of the line (even if I know the rectangle concern for ifTrue beck formatting) Why because it identifies really well the end of a method. It is especially good for method finishing with conditionals. ] Esteban could you

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

So if you follow eliot suggestion methodDeclaration [ methodbody ] put the start in another line. because with methodDeclaration [ methodbody ] we do not identify the body as a rectangle I do not think that [ on the first line is a good idea. Remember that people will send code in

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

Yes and this is not really good for method with multiple and long selectors because you have to spot the end of the line Morph class>>obtainArrowheadFor: aPrompt defaultValue: defaultPoint [ "Allow the user to supply a point to serve as an arrowhead size. Answer nil if we fail to get a good

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

heh… the format I propose is like this: methodDeclaration [ methodbody ] I think that keeps good readability and I can parse it easily. > On 10 Sep 2017, at 18:23, Stephane Ducasse wrote: > > Hi esteban > for me having space around [ ] improves readibility. > I

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

Hi esteban for me having space around [ ] improves readibility. I preferred methodDeclaration [ methodbody ] over methodDeclaration [ methodbody ] Especially in case of method body is blockish like while true/exception. But this is ok if people prefer methodDeclaration [

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

On 09-09-17 19:43, Eliot Miranda wrote: I think this is a serious mistake. Time stamps and author marks are important (even more important if the unit of commit is a single file for the whole class). When converting repos from monticello to git we could add extra commits for groups of

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

Hi Henrik, Le 10/09/2017 à 10:56, Henrik-Nergaard a écrit : Everyone who used filetree with metadata can tell it is super annoying and destroys the complete experience. There has been a fix for this on the issue tracker for some time:

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

> On 10 Sep 2017, at 10:56, Henrik-Nergaard wrote: > >>> Everyone who used filetree with metadata can tell it is super annoying and > destroys the complete experience. > There has been a fix for this on the issue tracker for some time: >

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

>>Everyone who used filetree with metadata can tell it is super annoying and destroys the complete experience. There has been a fix for this on the issue tracker for some time: https://pharo.fogbugz.com/f/cases/20251/Write-out-filetree-metadata-in-order Best regards, Henrik -- Sent from:

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

> On 9 Sep 2017, at 19:35, Eliot Miranda wrote: > > > Point class >> x: anInt1 y: anInt2 > [ > ^ self new setX: anInt1 Y: anInt2] > > because trailing white space will only accumulate, something I see in Pharo > and Squeak code. > > Alternatively have the

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

at information either… just get it in a different way. Esteban > >> >> Esteban >> >>> >>> >>> Fra: Pharo-dev <pharo-dev-boun...@lists.pharo.org >>> <mailto:pharo-dev-boun...@lists.pharo.org>> på vegne av Esteban Lore

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

> On 10 Sep 2017, at 09:50, Norbert Hartl wrote: > > Hi! > >> Am 10.09.2017 um 05:44 schrieb Alexandre Bergel : >> >> Hi! >> >> I live very very much this idea! >> >> I am wondering why do we need the timestamp? Git knows about who has >>

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

Hi! > Am 10.09.2017 um 05:44 schrieb 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? > the

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

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

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

> > 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

eban >> Lorenzano <esteba...@gmail.com> >> Sendt: 9. september 2017 11:39:12 >> Til: Pharo Development List >> Emne: Re: [Pharo-dev] About Git support for windows >> >> >> > On 8 Sep 2017, at 22:02, Eliot Miranda <eliot.mira...@gmail.com> w

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

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

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

ember 2017 11:39:12 > Til: Pharo Development List > Emne: Re: [Pharo-dev] About Git support for windows > > > > On 8 Sep 2017, at 22:02, Eliot Miranda <eliot.mira...@gmail.com> wrote: > > > > Hi All, > > > >> On Sep 8, 2017, at 9:44 AM, Stephan

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

endt: 9. september 2017 11:39:12 Til: Pharo Development List Emne: Re: [Pharo-dev] About Git support for windows > On 8 Sep 2017, at 22:02, Eliot Miranda <eliot.mira...@gmail.com> wrote: > > Hi All, > >> On Sep 8, 2017, at 9:44 AM, Stephane Ducasse <stepharo.s...@gm

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

> 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] About Git support for windows

> 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 is still WIP: for example timestamp needs to go to avoid conflicts. > and it also shows one downside ---

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

for example here https://github.com/estebanlm/pharo-tonel/blob/master/src/Morphic-Core/Morph.class.st and it also shows one downside --- up until now we didn't care much about how many methods are in class (because it was just another file), but now we have 1 lines of code class. On Fri,

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

>From memory one class of class/trait and one for extension In class/Trait "class / trait comments comment" Special STON order for classes to minimic our logical order (ie package tag add the end). Class { } or Trait { name: #T } + Point class >> x: anInt1 y: anInt2 [ ^ self

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

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 nice class file format. So that we will > not have 2Gb of space on harddisc, problems