|Luke Iannini||Jul 27, 2008 6:33 pm|
|Luigi Rensinghoff||Jul 28, 2008 4:01 am|
|Hans-Christoph Steiner||Jul 28, 2008 1:39 pm|
|Chris McCormick||Jul 28, 2008 7:48 pm|
|Luke Iannini||Jul 28, 2008 9:48 pm|
|Frank Barknecht||Jul 28, 2008 10:31 pm|
|Luke Iannini||Jul 28, 2008 11:07 pm|
|Luke Iannini||Jul 28, 2008 11:29 pm|
|Frank Barknecht||Jul 28, 2008 11:53 pm|
|IOhannes m zmoelnig||Jul 29, 2008 12:13 am|
|Matt Barber||Jul 29, 2008 12:18 am|
|Frank Barknecht||Jul 29, 2008 1:04 am|
|Enrique Erne||Jul 29, 2008 5:01 am|
|marius schebella||Jul 29, 2008 7:01 am|
|Matt Barber||Jul 29, 2008 7:28 am|
|Frank Barknecht||Jul 29, 2008 8:39 am|
|Matt Barber||Jul 29, 2008 9:41 am|
|Hans-Christoph Steiner||Jul 29, 2008 10:29 am|
|Hans-Christoph Steiner||Jul 29, 2008 10:33 am|
|Hans-Christoph Steiner||Jul 29, 2008 10:34 am|
|Frank Barknecht||Jul 29, 2008 11:04 am|
|marius schebella||Jul 29, 2008 11:23 am|
|marius schebella||Jul 29, 2008 11:25 am|
|Hans-Christoph Steiner||Jul 29, 2008 12:09 pm|
|Hans-Christoph Steiner||Jul 29, 2008 12:10 pm|
|Mike McGonagle||Jul 29, 2008 12:40 pm|
|Matt Barber||Jul 29, 2008 12:43 pm|
|Thomas Mayer||Jul 29, 2008 12:53 pm|
|Matt Barber||Jul 29, 2008 1:28 pm|
|Hans-Christoph Steiner||Jul 29, 2008 4:47 pm|
|Frank Barknecht||Jul 30, 2008 12:16 am|
|Frank Barknecht||Jul 30, 2008 1:01 am|
|Chris McCormick||Jul 30, 2008 1:46 am|
|Hans-Christoph Steiner||Jul 30, 2008 9:12 am|
|Frank Barknecht||Jul 30, 2008 10:10 am|
|marius schebella||Jul 30, 2008 12:14 pm|
|Frank Barknecht||Jul 30, 2008 12:34 pm|
|Roman Haefeli||Jul 30, 2008 4:49 pm|
|marius schebella||Jul 30, 2008 6:08 pm|
|Hans-Christoph Steiner||Jul 30, 2008 8:31 pm|
|Hans-Christoph Steiner||Jul 30, 2008 8:44 pm|
|Frank Barknecht||Jul 30, 2008 11:20 pm|
|IOhannes m zmoelnig||Jul 31, 2008 12:33 am|
|Damian Stewart||Jul 31, 2008 1:11 am|
|Roman Haefeli||Jul 31, 2008 1:16 am|
|Matt Barber||Jul 31, 2008 1:24 am|
|Roman Haefeli||Jul 31, 2008 1:56 am|
|Matt Barber||Jul 31, 2008 3:29 am|
|Frank Barknecht||Jul 31, 2008 8:14 am|
|Hans-Christoph Steiner||Aug 1, 2008 1:48 pm||.pd|
|Luke Iannini||Aug 3, 2008 2:02 am|
|marius schebella||Aug 3, 2008 12:32 pm|
|Luke Iannini||Aug 7, 2008 11:36 pm|
|IOhannes m zmölnig||Aug 7, 2008 11:54 pm|
|Luke Iannini||Sep 19, 2008 4:53 am|
|Subject:||Re: [PD] Idiomatic Pd|
|From:||Matt Barber (brbr...@gmail.com)|
|Date:||Jul 29, 2008 7:28:50 am|
Date: Tue, 29 Jul 2008 10:02:05 -0400 From: marius schebella <mari...@gmail.com> Subject: Re: [PD] Idiomatic Pd To: pd-l...@iem.at Message-ID: <488F...@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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 like tutorials it could be considered.
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.
If I work on big patches that run as installations (no interface) the parent patch is basically empty, it only shows piece information and credits, everything is in a subpatch called [MACHINE]. and that usually is more a visual representation of the space (according to positioning of sensors/speakers) or a basic overview of the patch structure with an short explanation of what the different subpatches are doing. even, if everybody says, pd patches are their own documentation, because everything is visible, that's not true, commenting should be an important part of patching (cyclone's comment allow differnt fonts, sizes, colors and width of comments).
This is a good point. In fact, for some patches e.g. for interactive pieces to be sent to musicians who don't do Pd for a living -- =o) -- I prefer to put everything in a subpatch which has a GOP control surface. I think it's productive to petition against the "spider web" style, but even too many objects and connections on the main patch seems wasteful somehow. It's nice to include a subpatch which can be opened with a bng, that is basically a readme. I do this for abstractions, too, but without the bng -- just something to describe how it works inside the patch itself, I suppose as a quick substitute for a help file.
Most of this is really personal, though, and I don't think it should be codified.
then, for patches that rely on abstractions, *maybe* it would be good to give them either unique names or put them into subfolders. (I have to say, I do not really stick with this rule. but at least one thing: the main patch should always be recognizable, I usually put it in capital letters, so that people know, which patch to start.
resources (images, textfiles, data) could be kept in a subfolder, too. (just think of the GEM examples, how often one of the images or videos can not be found. - at least in the past).
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.
When 0.39 begins to wane (so [declare] can be used), it might be productive to keep abstractions in subfolders, and possibly control in one and tilde in another. Same, as you suggest, with textfiles, qlists, images, and soundfiles. This way the main patch is there cleanly for anyone who might need to use the patch besides you, and especially nice for musicians.
Again, not essential, but ergonomic.