On Sun, Aug 3, 2008 at 2:03 AM, Luke Iannini [EMAIL PROTECTED] wrote:
Sorry all for my silence!! I've been deadly busy this week and it
looks like it will continue for another few days. But, rest assured,
my obsession cannot be squashed and we'll need plenty of criticism to
make a useful
when I try to add a wiki page to the Style Guide folder. Could you or
IOhannes try, maybe?
i always thought i had already fixed this.
hmm, obviously not
I just discovered that you fixed it IOhannes, thanks very much! Back
to work then.
ah sorry that i haven't told anyone. i forgot
Sorry all for my silence!! I've been deadly busy this week and it
looks like it will continue for another few days. But, rest assured,
my obsession cannot be squashed and we'll need plenty of criticism to
make a useful guide, so fire away :).
Everyone's suggestions are wonderful so far. I'm so
Hallo,
Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
On Jul 29, 2008, at 2:04 PM, Frank Barknecht wrote:
I really cannot see where you got the impression that I'm squelching
Luke's suggestion, when I briefly expressed a certain personal
scepticism regarding style guides
On Tue, Jul 29, 2008 at 09:13:38AM +0200, IOhannes m zmoelnig wrote:
* When prepending $0 to a symbol, only add a - to separate it from
another number, like [r $0-1stSend]. Otherwise the symbol should
immediately follow, like [r $0mySend].
I like using a forward slash (/) since this is
Yo,
On Mon, Jul 28, 2008 at 10:31 PM, Frank Barknecht [EMAIL PROTECTED] wrote:
Hallo,
Luke Iannini hat gesagt: // Luke Iannini wrote:
There are some amazing sets of abstractions being released recently,
which has served to highlight the many extant styles of patching. I
was wondering if
On Mon, Jul 28, 2008 at 1:39 PM, Hans-Christoph Steiner [EMAIL PROTECTED]
wrote:
I think a style guide is a great idea. There have been some
discussions along these lines in the past. I'd say just start a
wiki folder on puredata.info in the /docs/ section and edit it up.
Something like
Hallo,
Luke Iannini hat gesagt: // Luke Iannini wrote:
On Mon, Jul 28, 2008 at 10:31 PM, Frank Barknecht [EMAIL PROTECTED] wrote:
Style:
* If giving $0 as an argument to an abstraction, it is always first in
the argument list [1]
I often put it last (and it's specified to be that way
Luke Iannini wrote:
On Mon, Jul 28, 2008 at 7:49 PM, Chris McCormick [EMAIL PROTECTED] wrote:
On Sun, Jul 27, 2008 at 06:34:05PM -0700, Luke Iannini wrote:
* Sends and Receives are written in camelCase, with R appended to
complementary receives (e.g. in GUIs, $0mySlider for the send and
Luke,
I like some of your ideas, but I'd offer the following:
Style:
* If giving $0 as an argument to an abstraction, it is always first in
the argument list [1]
I often put it last (and it's specified to be that way e.g. in
Memento)
My reasoning here is that $0 is probably the most
Hi Luke
Luke Iannini wrote:
There are some amazing sets of abstractions being released recently,
which has served to highlight the many extant styles of patching. I
was wondering if there was interest in establishing a set of
guidelines for patching in the vein of PEP 8 for Python; I've
I am quite pedantic in regard to spacing and aligning of objects. I
started to space all objects using ctrl+arrow keys. that way all objects
are spaced like on a grid and always a multiple of 10px away of each other.
I don't know if that should go into a style guide, but for official
patches
Date: Tue, 29 Jul 2008 10:02:05 -0400
From: marius schebella [EMAIL PROTECTED]
Subject: Re: [PD] Idiomatic Pd
To: pd-list@iem.at
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I am quite pedantic in regard to spacing and aligning of objects. I
Hallo,
Matt Barber hat gesagt: // Matt Barber wrote:
Yes, I am this way too -- but with font sizes sometimes being
different from one platform to the next, and even between extended and
vanilla, it's really hard to ensure that things will line up sweetly
every time you open it, everywhere.
A
Abstractions, whenever possible I think, should try not to conflict
with names in extended, even when the patch is designed for vanilla.
Also, I think it's helpful to include tilde in abstraction names when
audio signals are involved.
Also, I forgot to mention that I think abstractions (and
On Jul 29, 2008, at 1:31 AM, Frank Barknecht wrote:
Hallo,
Luke Iannini hat gesagt: // Luke Iannini wrote:
There are some amazing sets of abstractions being released recently,
which has served to highlight the many extant styles of patching. I
was wondering if there was interest in
Can I suggest using the MoinMoin wiki syntax? IMHO the python wikis
all have weak syntax compared to MediaWiki, but MoinMoin is the
closest to MediaWiki, which is a widely used and relatively easy to
use syntax. It is also what is used in most of the rest of the
'docs' section. To use
Hallo,
Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
On Jul 29, 2008, at 1:31 AM, Frank Barknecht wrote:
I think, it would be important to first collect every possible style
element in the wild and document what people are using in reality.
That would be interesting. I'm
Hans-Christoph Steiner wrote:
On Jul 29, 2008, at 1:31 AM, Frank Barknecht wrote:
Hallo,
Luke Iannini hat gesagt: // Luke Iannini wrote:
There are some amazing sets of abstractions being released recently,
which has served to highlight the many extant styles of patching. I
was wondering
On Jul 29, 2008, at 2:04 PM, Frank Barknecht wrote:
Hallo,
Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
On Jul 29, 2008, at 1:31 AM, Frank Barknecht wrote:
I think, it would be important to first collect every possible style
element in the wild and document what
On Jul 29, 2008, at 2:25 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
On Jul 29, 2008, at 1:31 AM, Frank Barknecht wrote:
Hallo,
Luke Iannini hat gesagt: // Luke Iannini wrote:
There are some amazing sets of abstractions being released
recently,
which has served to
Actually, reading this thread for me has shown me that one idea that I have
been using is a lot more common that I had thought. The idea of naming the
receives on an object with an r at the end (or whatever) to distinguish it
from the send was something that I wasn't really sure if it was a Pd
When 0.39 begins to wane (so [declare] can be used), ...
Careful here: [declare -path ...] is disabled inside of abstractions
in Pd-0.41.
Right -- but [declare -path ...] is terribly useful for not having a
patch's main directory cluttered with 100 abstractions, which was the
main
On Jul 29, 2008, at 4:29 PM, Matt Barber wrote:
When 0.39 begins to wane (so [declare] can be used), ...
Careful here: [declare -path ...] is disabled inside of abstractions
in Pd-0.41.
Right -- but [declare -path ...] is terribly useful for not having a
patch's main directory
There are some amazing sets of abstractions being released recently,
which has served to highlight the many extant styles of patching. I
was wondering if there was interest in establishing a set of
guidelines for patching in the vein of PEP 8 for Python; I've found
that document to be very
Hi Luke..
I think that is very useful
even better would it be to have that in a PD-Patch ;-)
so it is 100% clear what is meant and maybe easier to read...
Bye
Luigi
Am 28.07.2008 um 03:34 schrieb Luke Iannini:
There are some amazing sets of abstractions being released recently,
which
I think a style guide is a great idea. There have been some
discussions along these lines in the past. I'd say just start a
wiki folder on puredata.info in the /docs/ section and edit it up.
Something like /docs/style-guide/ I think that the main page could
lay out all of the possible
On Sun, Jul 27, 2008 at 06:34:05PM -0700, Luke Iannini wrote:
* Sends and Receives are written in camelCase, with R appended to
complementary receives (e.g. in GUIs, $0mySlider for the send and
$0mySliderR for the receive)
Will this even work? I think sends and receives have to be named the
On Mon, Jul 28, 2008 at 7:49 PM, Chris McCormick [EMAIL PROTECTED] wrote:
On Sun, Jul 27, 2008 at 06:34:05PM -0700, Luke Iannini wrote:
* Sends and Receives are written in camelCase, with R appended to
complementary receives (e.g. in GUIs, $0mySlider for the send and
$0mySliderR for the
Hallo,
Luke Iannini hat gesagt: // Luke Iannini wrote:
There are some amazing sets of abstractions being released recently,
which has served to highlight the many extant styles of patching. I
was wondering if there was interest in establishing a set of
guidelines for patching in the vein of
30 matches
Mail list logo
