-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Also, while we are at it, [OSCroute], [sendOSC], and [dumpOSC] aren't
exactly the best names. How about something like [OSCroute],
[OSCsend], and [OSCreceive]. Or they could be in a libdir and be
[osc/route], [osc/send], and [osc/receive], but maybe that's getting
ahead of myself ;)
That's the way I'd like to see objects named in the future, using
common names for common concepts, like send, receive, route, with the
namespace selecting which one you are using. This is the way Java is,
for example, and it makes a lot of sense. It makes the knowledge more
modular. Once you know the Pd concept of send and receive, you can add
"pd", "net", "osc", or "~" depending on what you want to send and
receive. For example:
[pd/send], [pd/receive] [net/send], [net/receive] [osc/send], [osc/receive] [send~], [receive~]
.hc
On Nov 22, 2005, at 9:58 AM, B. Bogart wrote:
There are many things that I would like to see in the OSC for PD that are not in OSCx. What is liblo? Is there a standard OSC lib that impliments all the goodies, including the parameter query stuff?
b.
günter geiger wrote:
On Tue, 22 Nov 2005, Frank Barknecht wrote:
The license of OSC is fine (now), it could be shipped with Pd immediatly.
The license is fine, but the code is terrible. It would be better to
have a fresh implementation or something based on liblo.Günter
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
"Terrorism is not an enemy. It cannot be defeated. It's a tactic.
It's about as sensible to say we declare war on night attacks and
expect we're going to win that war. We're not going to win the war on
terrorism."
-
retired U.S. Army general, William Odom