[PD] Re: PD-list digest, Vol 1 #1485 - 14 msgs

[Macciza Macpherson]

HighAll, High Rod,
Just a couple of quick thoughts.
Maybe leverage OSC's messaging for communications and develop a rich 
expressive address space for your project ala SC.
This also raises the whole question of networks. Pass duties to various 
machines in a client server relationship each doing there own little 
bit for the greater good.
Just thought I'd throw in my two bobs worth.
Cheers,
Macciza

On Tuesday, October 19, 2004, at 12:11 AM, pd-list-request at iem.at wrote:
>    2. Managing really big PD projects?? Style guide or best practice 
> etc? (rodney)
> Message: 2
> From: "rodney" <rodney at atr.jp>
> To: <pd-list at iem.at>
> Date: Mon, 18 Oct 2004 15:58:08 +0900
> Subject: [PD] Managing really big PD projects?? Style guide or best 
> practice etc?
>
> HI all,
>
> I have been building a project  in pd and lately it has got difficult 
> to
> manage because of the complex web of spagetti all over the place.
>
> I'd like to hear others' advice on sensible architectures for PD =
> projects to
> prevent them becoming unweildy and confusing.
>
> Especially, how you deal with:
> - lots of abstractions with multiple instances
> - send and receive objects and remembering where they all go to - come 
> =
> from
> - identifying where slow-downs occur in big patch networks
> - keeping notes of your project in a way that makes sense after not =
> looking
> at it for a month or two. :)
>
> I would be keen to collect all these pearls of wisdom into one doc for 
> =
> the
> wiki or somewhere, if one does not already exist.
>
> Cheers,
> 	  Rod
>
> Rodney Berry
> ATR Media Information Science Laboratories
> Kyoto Japan