On 29/12/14 08:54, stepharo wrote:
Le 19/11/14 15:19, Nicolai Hess a écrit :
2014-11-19 14:55 GMT+01:00 Marcus Denker
marcus.den...@inria.fr
mailto:marcus.den...@inria.fr:
On 19 Nov 2014, at 14:47, Peter Uhnák
i.uh...@gmail.com
mailto:i.uh...@gmail.com wrote:
how Pharo
I'm still missing the RB based formatter in Dolphin. It's comparable to
the Pharo one (layout wise) but created less line-break-noise :-)
;-)
I think that it should not be that difficult to arrive to a good compromise
It should be easy create an RBFormatter with the same settings in
Dolphin
On 29/12/14 14:32, stepharo wrote:
I'm still missing the RB based formatter in Dolphin. It's comparable to
the Pharo one (layout wise) but created less line-break-noise :-)
;-)
I think that it should not be that difficult to arrive to a good compromise
It should be easy create an RBFormatter
As far as I remember it was just the stock RB(Configurable?)Formatter
with custom settings. Let me dig out my Dolphin Image.
This is the same in Pharo. Lukas improved it.
Especially as the format hotkey doesn't work reliably on Mac OS X -
still have to chase why.
Yes I would like to have.
On 29 Dec 2014, at 15:30, stepharo steph...@free.fr wrote:
As far as I remember it was just the stock RB(Configurable?)Formatter with
custom settings. Let me dig out my Dolphin Image.
This is the same in Pharo. Lukas improved it.
I think the “too many line breaks” is actually a bug. It
Le 19/11/14 15:19, Nicolai Hess a écrit :
2014-11-19 14:55 GMT+01:00 Marcus Denker marcus.den...@inria.fr
mailto:marcus.den...@inria.fr:
On 19 Nov 2014, at 14:47, Peter Uhnák i.uh...@gmail.com
mailto:i.uh...@gmail.com wrote:
how Pharo source code is formatted
One could
Hi,
On Thu, 2014-11-20 at 16:47 +0100, Henrik Johansen wrote:
On 20 Nov 2014, at 2:39 , Jan Vrany jan.vr...@fit.cvut.cz wrote:
But as I said, I'm more interested in 'low level' details like I
mentioned:
- encoding of the source string
Best, Jan
IIRC, the .bin is the
Hi guys,
thanks for replies. I read books mentioned by Christophe years ago,
they're worth reading indeed.
But as I said, I'm more interested in 'low level' details like I
mentioned:
- tabs/spaces? How many spaces if spaces?
- encoding of the source string
- trailing newlines
- trailing
(but then again people do
use different styles so it might not apply).
Peter
-Original Message-
From: Jan Vrany jan.vr...@fit.cvut.cz
Sent: 11/20/2014 2:38 PM
To: pharo-dev@lists.pharo.org pharo-dev@lists.pharo.org
Subject: Re: [Pharo-dev] Source code formatting guidelines
Hi guys,
thanks
On 20 Nov 2014, at 2:39 , Jan Vrany jan.vr...@fit.cvut.cz wrote:
But as I said, I'm more interested in 'low level' details like I
mentioned:
- encoding of the source string
Best, Jan
IIRC, the .bin is the entire source string in Datastream-format, that is, is a
datatype
Hi guys,
is there any document I can read on how Pharo source code
is/should be formatted? I mean things like
- tabs/spaces? How many spaces if spaces?
- encoding of the source string
- trailing newlines
- trailing spaces
- ...
I don't care much about things like whether there should
be a
Hi
I find the formatting chapter of the 'Smalltalk best practices pattern, Kent
Beck' really nice but I cannot find a free pdf.
I just found
http://sdmeta.gforge.inria.fr/FreeBooks/WithStyle/SmalltalkWithStyle.pdf. There
is also a chapter about formatting. Should also be a good reading.
how Pharo source code is formatted
One could argue that this is equivalent to the default settings of Pharo
formatter.
On 19 Nov 2014, at 14:47, Peter Uhnák i.uh...@gmail.com wrote:
how Pharo source code is formatted
One could argue that this is equivalent to the default settings of Pharo
formatter.
Which is not good… e.g. it always adds too many line breaks…
Marcus
2014-11-19 14:55 GMT+01:00 Marcus Denker marcus.den...@inria.fr:
On 19 Nov 2014, at 14:47, Peter Uhnák i.uh...@gmail.com wrote:
how Pharo source code is formatted
One could argue that this is equivalent to the default settings of Pharo
formatter.
Which is not good… e.g. it always adds
15 matches
Mail list logo
