Derek Holzer wrote:

In the Pure Data FLOSS Manual, there are a naming couple conventions that I'm still uncertain about using there:

1. audio object vs [dataflow/message/non-audio/data/numeric] object

i would go for "message" object. "numeric" is wrong most of the time, "non-audio" seems clumsy, "data" is equally true for audio-objects as is "dataflow".

2. edit mode vs [play/perform/performance/non-edit] mode

personally is us "run" mode mostly. "play" is a bit non-interactive; non-edit is so negative; perform(ance) implies a performance boost rather than a different type of interaction.

gfam,drs IOhannes

On Sun, 14 Sep 2008, Derek Holzer wrote:

In the Pure Data FLOSS Manual, there are a naming couple conventions that I'm still uncertain about using there:

1. audio object vs [dataflow/message/non-audio/data/numeric] object

I like "message", I think that is pretty widely used. "dataflow", "data", and "numeric" are all not correct, so should be avoided IMHO. audio and message objects can have data, numeric data, and all are part of the dataflow.

2. edit mode vs [play/perform/performance/non-edit] mode

I think in the Pd manual, it's called "run" mode, but that doesn't make sense since Pd is always running. I like "play" mode.

.hc

We've already discussed "Pd vs PD" here. Anybody wanna give these others a shot to make one canonical?

Hopefully this won't get to out of hand... ;-) best, D. -- derek holzer ::: http://www.umatic.nl ::: http://blog.myspace.com/macumbista ---Oblique Strategy # 14: "Ask people to work against their better judgement"

---

Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

zen
   \
    \
     \