I made some net externals that use raw bytes instead of pd messages: http://puredata.info/Members/martinrp/netobjects They are based on netreceive and netsend. Maybe they could be incorporated into pd since they're using poll functions which are not officially exposed in m_pd.h. I'm working on packOSC and upackOSC which interface to these objects via lists of floats-constrained-to-be-bytes. unpackOSC will allow routing via route instead of OSCroute since the path will be separated into symbols and output as a list. The data will be output as a separate list.
Martin
Hallo, Martin Peach hat gesagt: // Martin Peach wrote:
I'm working on packOSC and upackOSC which interface to these objects via lists of floats-constrained-to-be-bytes. unpackOSC will allow routing via route instead of OSCroute since the path will be separated into symbols and output as a list. The data will be output as a separate list.
Hm, but [route] doesn't support wildcards like [OSCroute] does. Isn't this a step backwards?
Ciao
Frank Barknecht wrote:
Hallo, Martin Peach hat gesagt: // Martin Peach wrote:
I'm working on packOSC and upackOSC which interface to these objects via lists of floats-constrained-to-be-bytes. unpackOSC will allow routing via route instead of OSCroute since the path will be separated into symbols and output as a list. The data will be output as a separate list.
Hm, but [route] doesn't support wildcards like [OSCroute] does. Isn't this a step backwards?
You could just use a [route *] for the simplest wildcard type. But yes, probably a special OSCroute is still needed, but it needs to be settable by messages as well as creation arguments. Maybe I should redo OSCroute instead...
Martin
Ciao
On Apr 21, 2006, at 10:03 PM, Martin Peach wrote:
Frank Barknecht wrote:
Hallo, Martin Peach hat gesagt: // Martin Peach wrote:
I'm working on packOSC and upackOSC which interface to these objects via lists of floats-constrained-to-be-bytes. unpackOSC will allow routing via route instead of OSCroute since the path will be separated into symbols and output as a list. The data will be output as a separate list.
Hm, but [route] doesn't support wildcards like [OSCroute] does. Isn't this a step backwards?
You could just use a [route *] for the simplest wildcard type. But yes, probably a special OSCroute is still needed, but it needs to be settable by messages as well as creation arguments. Maybe I should redo OSCroute instead...
Both options would be nice to have. I think a better solution would be to make a generic route object that handles wildcards based on the existing route object. The [route] in Pd core also has some other issues, like [route list] not always outputting a list, so a new route object could be nice.
The more we translate everything into generic messages, the more flexible Pd becomes, IMHO.
.hc
________________________________________________________________________ ____
"Computer science is no more related to the computer than astronomy is related to the telescope." -Edsger Dykstra
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
The [route] in Pd core also has some other issues, like [route list] not always outputting a list, so a new route object could be nice.
[route list] actually never outputs a list-message with a "list"-selector (except implied lists like "1 2 3"), this is the expected and correct behaviour. [route list] in this regard is equivalent to [list trim].
Ciao
On Tue, 25 Apr 2006, Frank Barknecht wrote:
[route list] actually never outputs a list-message with a "list"-selector (except implied lists like "1 2 3"), this is the expected and correct behaviour. [route list] in this regard is equivalent to [list trim].
A few days ago I coded a [route2] which always outputs the same thing as the input, and then soon enough I'll also code a [route3] which replaces the selector by "list". This is so that abstractions become easier to code. I'd welcome better names than [route2] and [route3] if they're not too long.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada
Mathieu Bouchard wrote:
On Tue, 25 Apr 2006, Frank Barknecht wrote:
[route list] actually never outputs a list-message with a "list"-selector (except implied lists like "1 2 3"), this is the expected and correct behaviour. [route list] in this regard is equivalent to [list trim].
A few days ago I coded a [route2] which always outputs the same thing as the input, and then soon enough I'll also code a [route3] which replaces the selector by "list". This is so that abstractions become easier to code. I'd welcome better names than [route2] and [route3] if they're not too long.
the zexy-object corresponding to [route2] is called [relay]
mfg.asdr. IOhannes
On Apr 25, 2006, at 4:25 PM, IOhannes m zmoelnig wrote:
Mathieu Bouchard wrote:
On Tue, 25 Apr 2006, Frank Barknecht wrote:
[route list] actually never outputs a list-message with a "list"-selector (except implied lists like "1 2 3"), this is the expected and correct behaviour. [route list] in this regard is equivalent to [list trim].
A few days ago I coded a [route2] which always outputs the same thing as the input, and then soon enough I'll also code a [route3] which replaces the selector by "list". This is so that abstractions become easier to code. I'd welcome better names than [route2] and [route3] if they're not too long.
the zexy-object corresponding to [route2] is called [relay]
While [route2] is not a good name, I don't think [relay] makes sense there either.
WordNet (r) 2.0 relay n 1: the act of relaying something 2: electrical device such that current flowing through it in one circuit can switch on and off a current in a second circuit [syn: {electrical relay}] v 1: pass along; "Please relay the news to the villagers" 2: control or operate by relay
"route" is a perfect word for the concept, so I say add a descriptor to the word route.
.hc
________________________________________________________________________ ____
"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
Hans-Christoph Steiner wrote:
the zexy-object corresponding to [route2] is called [relay]
While [route2] is not a good name, I don't think [relay] makes sense there either.
WordNet (r) 2.0 relay n 1: the act of relaying something 2: electrical device such that current flowing through it in one circuit can switch on and off a current in a second circuit [syn: {electrical relay}] v 1: pass along; "Please relay the news to the villagers"
that is what i exactly what i head in mind: i thought "relaying the news to the villager" is like "pass the message to the object without modifying it"; however i english is not my primary language.
2: control or operate by relay"route" is a perfect word for the concept, so I say add a descriptor to the word route.
i tried to avoid [route_without_strip]...
mfg.asdr IOhannes
On Apr 25, 2006, at 6:20 PM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
the zexy-object corresponding to [route2] is called [relay]
While [route2] is not a good name, I don't think [relay] makes sense there either.
WordNet (r) 2.0 relay n 1: the act of relaying something 2: electrical device such that current flowing through it in one circuit can switch on and off a current in a second circuit [syn: {electrical relay}] v 1: pass along; "Please relay the news to the villagers"
that is what i exactly what i head in mind: i thought "relaying the news to the villager" is like "pass the message to the object without modifying it"; however i english is not my primary language.
relaying doesn't have any branches, relaying is just from one thing to another (from "me" to the "villagers").
relaying: () -> ()
routing: /-->() ()-|--->() -->()
Hope this wasn't too pedantic, I was just trying to be clear.
.hc
2: control or operate by relay"route" is a perfect word for the concept, so I say add a descriptor to the word route.
i tried to avoid [route_without_strip]...
mfg.asdr IOhannes
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
________________________________________________________________________ ____
"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
Hans-Christoph Steiner wrote:
that is what i exactly what i head in mind: i thought "relaying the news to the villager" is like "pass the message to the object without modifying it"; however i english is not my primary language.
relaying doesn't have any branches, relaying is just from one thing to another (from "me" to the "villagers").
relaying: () -> ()
routing: /-->() ()-|--->() -->()
Hope this wasn't too pedantic, I was just trying to be clear.
no i am fine with that, it is always good to learn something. i had a hard time to find a short and pregnant name for the object and when i finally found [relay] i was quite happy. in a way the object does relay from one object to 1 other object; being mail adminstrator i could see the "postman" functionality of the object: the postman gets a message for a person and passes it on depending on the address. this is not a 1-to-many form of distribution.
however, i will be happy to use a better name if somebody finds one...
mfg.asdr. IOhannes
On Tue, 25 Apr 2006, IOhannes m zmoelnig wrote:
no i am fine with that, it is always good to learn something. i had a hard time to find a short and pregnant name for the object and when i finally found [relay] i was quite happy. however, i will be happy to use a better name if somebody finds one...
[route2] makes it clear that this is supposed to be a variant of [route]. I don't think of the appended "2" to be sooo clever, but I prefer that rather than choosing another word.
OTOH, I *did* call [shunt] what used to be called [demux] because of a name conflict. We were used to semantics of jMax's [demux] and that's what available in [shunt]. I don't know whether I'd still take the same decision if I had the occasion to.
IMHO, having super clear names isn't that important as long as help files are just a click away. Eventually, help will be zero click away, given enough tooltips.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada
On Apr 30, 2006, at 11:10 PM, Mathieu Bouchard wrote:
On Tue, 25 Apr 2006, IOhannes m zmoelnig wrote:
no i am fine with that, it is always good to learn something. i had a hard time to find a short and pregnant name for the object and when i finally found [relay] i was quite happy. however, i will be happy to use a better name if somebody finds one...
[route2] makes it clear that this is supposed to be a variant of [route]. I don't think of the appended "2" to be sooo clever, but I prefer that rather than choosing another word.
OTOH, I *did* call [shunt] what used to be called [demux] because of a name conflict. We were used to semantics of jMax's [demux] and that's what available in [shunt]. I don't know whether I'd still take the same decision if I had the occasion to.
IMHO, having super clear names isn't that important as long as help files are just a click away. Eventually, help will be zero click away, given enough tooltips.
It should be memorable. If you can remember the object name, then the help file is not going to help you.
.hc ________________________________________________________________________ ____
"The arc of history bends towards justice." - Dr. Martin Luther King, Jr.
On Mon, 1 May 2006, Hans-Christoph Steiner wrote:
It should be memorable. If you can remember the object name, then the help file is not going to help you.
Oh yeah?
Interestingly, one has to know the object name in order to right-click-Help.
but I'm not just talking about writing patches. I'm also talking about reading them. If you see [242.mikr0s0ft] in a patch and you've never used it, the help file is going to help you. What if you remember seeing the name but don't recall what it does? that can happen both when writing patches and reading them.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada
On May 4, 2006, at 6:39 PM, Mathieu Bouchard wrote:
On Mon, 1 May 2006, Hans-Christoph Steiner wrote:
It should be memorable. If you can remember the object name, then the help file is not going to help you.
Oh yeah?
Interestingly, one has to know the object name in order to right-click-Help.
but I'm not just talking about writing patches. I'm also talking about reading them. If you see [242.mikr0s0ft] in a patch and you've never used it, the help file is going to help you. What if you remember seeing the name but don't recall what it does? that can happen both when writing patches and reading them.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada
That should have read:
It should be memorable. If you can NOT remember the object name, then the help file is not going to help you.
.hc
________________________________________________________________________ ____
¡El pueblo unido jamás será vencido!
Hallo, Mathieu Bouchard hat gesagt: // Mathieu Bouchard wrote:
A few days ago I coded a [route2] which always outputs the same thing as the input, and then soon enough I'll also code a [route3] which replaces the selector by "list".
Does this mean, "set x y" becomes "list x y" with [route3 set]?
Ciao
On Tue, 25 Apr 2006, Frank Barknecht wrote:
Mathieu Bouchard hat gesagt: // Mathieu Bouchard wrote:
A few days ago I coded a [route2] which always outputs the same thing as the input, and then soon enough I'll also code a [route3] which replaces the selector by "list".
Does this mean, "set x y" becomes "list x y" with [route3 set]?
Yeah. This is nice because then you can plug it into a messagebox without causing the messagebox to reprogram itself =)
It like a [list split 1] per output of [route].
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada
On Apr 25, 2006, at 11:54 AM, Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
The [route] in Pd core also has some other issues, like [route list] not always outputting a list, so a new route object could be nice.
[route list] actually never outputs a list-message with a "list"-selector (except implied lists like "1 2 3"), this is the expected and correct behaviour. [route list] in this regard is equivalent to [list trim].
I disagree that this behavior is expected or correct, but we can leave that discussion in the archive from the previous time.
.hc
________________________________________________________________________ ____
"Looking at things from a more basic level, you can come up with a more direct solution... It may sound small in theory, but it in practice, it can change entire economies." - Amy Smith
hello, this is what i was looking for to control a lanbox dmx controler. send object work, but i have problem with receive objects :
cc -DPD -O2 -funroll-loops -fomit-frame-pointer -Wall -W -Wshadow -Wstrict-prototypes -Werror -Wno-unused -Wno-parentheses -Wno-switch -I../../src -o udpreceive.o -c udpreceive.c cc1: warnings being treated as errors udpreceive.c: In function ‘udpreceive_read’: udpreceive.c:49: attention : pointer targets in passing argument 6 of ‘recvfrom’ differ in signedness make: *** [udpreceive.pd_linux] Erreur 1 cc -DPD -O2 -funroll-loops -fomit-frame-pointer -Wall -W -Wshadow -Wstrict-prototypes -Werror -Wno-unused -Wno-parentheses -Wno-switch -I../../src -o tcpreceive.o -c tcpreceive.c cc1: warnings being treated as errors tcpreceive.c: In function ‘tcpreceive_connectpoll’: tcpreceive.c:196: attention : pointer targets in passing argument 3 of ‘accept’ differ in signedness make: *** [tcpreceive.pd_linux] Erreur 1
could this object be found on the cvs?
thanks Cyrille
Martin Peach a écrit :
I made some net externals that use raw bytes instead of pd messages: http://puredata.info/Members/martinrp/netobjects They are based on netreceive and netsend. Maybe they could be incorporated into pd since they're using poll functions which are not officially exposed in m_pd.h. I'm working on packOSC and upackOSC which interface to these objects via lists of floats-constrained-to-be-bytes. unpackOSC will allow routing via route instead of OSCroute since the path will be separated into symbols and output as a list. The data will be output as a separate list.
Martin
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
changing int fromlen = sizeof(from); to unsigned int fromlen = sizeof(from);
make them to compile...
Cyrille
cyrille henry a écrit :
hello, this is what i was looking for to control a lanbox dmx controler. send object work, but i have problem with receive objects :
cc -DPD -O2 -funroll-loops -fomit-frame-pointer -Wall -W -Wshadow -Wstrict-prototypes -Werror -Wno-unused -Wno-parentheses -Wno-switch -I../../src -o udpreceive.o -c udpreceive.c cc1: warnings being treated as errors udpreceive.c: In function ‘udpreceive_read’: udpreceive.c:49: attention : pointer targets in passing argument 6 of ‘recvfrom’ differ in signedness make: *** [udpreceive.pd_linux] Erreur 1 cc -DPD -O2 -funroll-loops -fomit-frame-pointer -Wall -W -Wshadow -Wstrict-prototypes -Werror -Wno-unused -Wno-parentheses -Wno-switch -I../../src -o tcpreceive.o -c tcpreceive.c cc1: warnings being treated as errors tcpreceive.c: In function ‘tcpreceive_connectpoll’: tcpreceive.c:196: attention : pointer targets in passing argument 3 of ‘accept’ differ in signedness make: *** [tcpreceive.pd_linux] Erreur 1
could this object be found on the cvs?
thanks Cyrille
Martin Peach a écrit :
I made some net externals that use raw bytes instead of pd messages: http://puredata.info/Members/martinrp/netobjects They are based on netreceive and netsend. Maybe they could be incorporated into pd since they're using poll functions which are not officially exposed in m_pd.h. I'm working on packOSC and upackOSC which interface to these objects via lists of floats-constrained-to-be-bytes. unpackOSC will allow routing via route instead of OSCroute since the path will be separated into symbols and output as a list. The data will be output as a separate list.
Martin
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
cyrille henry wrote:
hello, this is what i was looking for to control a lanbox dmx controler. send object work, but i have problem with receive objects :
cc -DPD -O2 -funroll-loops -fomit-frame-pointer -Wall -W -Wshadow -Wstrict-prototypes -Werror -Wno-unused -Wno-parentheses -Wno-switch -I../../src -o udpreceive.o -c udpreceive.c cc1: warnings being treated as errors
If you take out the Werror it should compile.
udpreceive.c: In function ‘udpreceive_read’: udpreceive.c:49: attention : pointer targets in passing argument 6 of ‘recvfrom’ differ in signedness
Otherwise changing the line int fromlen = sizeof(from); to socklen_t fromlen = sizeof(from); will cure the problem. socklen_t is defined in sys/socket.h, or ws2tcpip.h on MSW.
make: *** [udpreceive.pd_linux] Erreur 1 cc -DPD -O2 -funroll-loops -fomit-frame-pointer -Wall -W -Wshadow -Wstrict-prototypes -Werror -Wno-unused -Wno-parentheses -Wno-switch -I../../src -o tcpreceive.o -c tcpreceive.c cc1: warnings being treated as errors tcpreceive.c: In function ‘tcpreceive_connectpoll’: tcpreceive.c:196: attention : pointer targets in passing argument 3 of ‘accept’ differ in signedness
Here again changing the line int fromlen = sizeof(from); to socklen_t fromlen = sizeof(from); will cure the problem.
make: *** [tcpreceive.pd_linux] Erreur 1
could this object be found on the cvs?
No, I don't have write access to the cvs. I'll post the corrected code today here: http://puredata.info/Members/martinrp/netobjects Of course anyone is welcome to put the files in cvs... Martin
thanks Cyrille
Martin Peach a écrit :
I made some net externals that use raw bytes instead of pd messages: http://puredata.info/Members/martinrp/netobjects They are based on netreceive and netsend. Maybe they could be incorporated into pd since they're using poll functions which are not officially exposed in m_pd.h. I'm working on packOSC and upackOSC which interface to these objects via lists of floats-constrained-to-be-bytes. unpackOSC will allow routing via route instead of OSCroute since the path will be separated into symbols and output as a list. The data will be output as a separate list.
Martin
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Would you like to have write access to the CVS? You are contributing quite a bit these days, so it makes sense.
.hc
On Apr 24, 2006, at 7:25 PM, Martin Peach wrote:
cyrille henry wrote:
hello, this is what i was looking for to control a lanbox dmx controler. send object work, but i have problem with receive objects :
cc -DPD -O2 -funroll-loops -fomit-frame-pointer -Wall -W -Wshadow - Wstrict-prototypes -Werror -Wno-unused -Wno-parentheses -Wno- switch -I../../src -o udpreceive.o -c udpreceive.c cc1: warnings being treated as errors
If you take out the Werror it should compile.
udpreceive.c: In function ‘udpreceive_read’: udpreceive.c:49: attention : pointer targets in passing argument 6 of ‘recvfrom’ differ in signedness
Otherwise changing the line int fromlen = sizeof(from); to socklen_t fromlen = sizeof(from); will cure the problem. socklen_t is defined in sys/socket.h, or ws2tcpip.h on MSW.
make: *** [udpreceive.pd_linux] Erreur 1 cc -DPD -O2 -funroll-loops -fomit-frame-pointer -Wall -W -Wshadow - Wstrict-prototypes -Werror -Wno-unused -Wno-parentheses -Wno- switch -I../../src -o tcpreceive.o -c tcpreceive.c cc1: warnings being treated as errors tcpreceive.c: In function ‘tcpreceive_connectpoll’: tcpreceive.c:196: attention : pointer targets in passing argument 3 of ‘accept’ differ in signedness
Here again changing the line int fromlen = sizeof(from); to socklen_t fromlen = sizeof(from); will cure the problem.
make: *** [tcpreceive.pd_linux] Erreur 1
could this object be found on the cvs?
No, I don't have write access to the cvs. I'll post the corrected code today here: http://puredata.info/Members/martinrp/netobjects Of course anyone is welcome to put the files in cvs... Martin
thanks Cyrille
Martin Peach a écrit :
I made some net externals that use raw bytes instead of pd messages: http://puredata.info/Members/martinrp/netobjects They are based on netreceive and netsend. Maybe they could be incorporated into pd since they're using poll functions which are not officially exposed in m_pd.h. I'm working on packOSC and upackOSC which interface to these objects via lists of floats-constrained-to-be-bytes. unpackOSC will allow routing via route instead of OSCroute since the path will be separated into symbols and output as a list. The data will be output as a separate list.
Martin
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
________________________________________________________________________ ____
Man has survived hitherto because he was too ignorant to know how to realize his wishes. Now that he can realize them, he must either change them, or perish. -William Carlos Williams
Hans-Christoph Steiner wrote:
Would you like to have write access to the CVS? You are contributing quite a bit these days, so it makes sense.
That would be very nice. What do I need to do to get that?
Martin
.hc
On Apr 24, 2006, at 7:25 PM, Martin Peach wrote:
cyrille henry wrote:
hello, this is what i was looking for to control a lanbox dmx controler. send object work, but i have problem with receive objects :
cc -DPD -O2 -funroll-loops -fomit-frame-pointer -Wall -W -Wshadow - Wstrict-prototypes -Werror -Wno-unused -Wno-parentheses -Wno- switch -I../../src -o udpreceive.o -c udpreceive.c cc1: warnings being treated as errors
If you take out the Werror it should compile.
udpreceive.c: In function ‘udpreceive_read’: udpreceive.c:49: attention : pointer targets in passing argument 6 of ‘recvfrom’ differ in signedness
Otherwise changing the line int fromlen = sizeof(from); to socklen_t fromlen = sizeof(from); will cure the problem. socklen_t is defined in sys/socket.h, or ws2tcpip.h on MSW.
make: *** [udpreceive.pd_linux] Erreur 1 cc -DPD -O2 -funroll-loops -fomit-frame-pointer -Wall -W -Wshadow - Wstrict-prototypes -Werror -Wno-unused -Wno-parentheses -Wno- switch -I../../src -o tcpreceive.o -c tcpreceive.c cc1: warnings being treated as errors tcpreceive.c: In function ‘tcpreceive_connectpoll’: tcpreceive.c:196: attention : pointer targets in passing argument 3 of ‘accept’ differ in signedness
Here again changing the line int fromlen = sizeof(from); to socklen_t fromlen = sizeof(from); will cure the problem.
make: *** [tcpreceive.pd_linux] Erreur 1
could this object be found on the cvs?
No, I don't have write access to the cvs. I'll post the corrected code today here: http://puredata.info/Members/martinrp/netobjects Of course anyone is welcome to put the files in cvs... Martin
thanks Cyrille
Martin Peach a écrit :
I made some net externals that use raw bytes instead of pd messages: http://puredata.info/Members/martinrp/netobjects They are based on netreceive and netsend. Maybe they could be incorporated into pd since they're using poll functions which are not officially exposed in m_pd.h. I'm working on packOSC and upackOSC which interface to these objects via lists of floats-constrained-to-be-bytes. unpackOSC will allow routing via route instead of OSCroute since the path will be separated into symbols and output as a list. The data will be output as a separate list.
Martin
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Man has survived hitherto because he was too ignorant to know how to realize his wishes. Now that he can realize them, he must either change them, or perish. -William Carlos Williams
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Hallo, Martin Peach hat gesagt: // Martin Peach wrote:
Hans-Christoph Steiner wrote:
Would you like to have write access to the CVS? You are contributing quite a bit these days, so it makes sense.
That would be very nice. What do I need to do to get that?
You need to create a Sourceforge user account, then an admin can add you to the project using that account name.
There also traditionally will be a certain period where we wait for other project admins to bring up possible objections against adding someone as a developer to the project, so you may want to give a short intro on who you are, what you intend to work on in the project etc.
I just repeat that I wouldn't have any objections.
Ciao
Frank Barknecht wrote:
Hallo, Martin Peach hat gesagt: // Martin Peach wrote:
Hans-Christoph Steiner wrote:
Would you like to have write access to the CVS? You are contributing quite a bit these days, so it makes sense.
That would be very nice. What do I need to do to get that?
You need to create a Sourceforge user account, then an admin can add you to the project using that account name.
I have the name mrpeach on sourceforge.
There also traditionally will be a certain period where we wait for other project admins to bring up possible objections against adding someone as a developer to the project, so you may want to give a short intro on who you are, what you intend to work on in the project etc.
OK, I'm currently working as a technician in the "Intermedia Cyberarts" program at Concordia University. see http://imca.concordia.ca/facilities.html I've coded some externals for OSC and networking and would like to add them to the collection in cvs. Possibly the net objects could be integrated into the pd core but I'm hesitant to do this myself, not wanting to screw things up and all... Martin
I just repeat that I wouldn't have any objections.
Ciao
On Apr 26, 2006, at 8:00 PM, Martin Peach wrote:
Frank Barknecht wrote:
Hallo, Martin Peach hat gesagt: // Martin Peach wrote:
Hans-Christoph Steiner wrote:
Would you like to have write access to the CVS? You are contributing quite a bit these days, so it makes sense.
That would be very nice. What do I need to do to get that?
You need to create a Sourceforge user account, then an admin can add you to the project using that account name.
I have the name mrpeach on sourceforge.
There also traditionally will be a certain period where we wait for other project admins to bring up possible objections against adding someone as a developer to the project, so you may want to give a short intro on who you are, what you intend to work on in the project etc.
OK, I'm currently working as a technician in the "Intermedia Cyberarts" program at Concordia University. see http://imca.concordia.ca/facilities.html I've coded some externals for OSC and networking and would like to add them to the collection in cvs. Possibly the net objects could be integrated into the pd core but I'm hesitant to do this myself, not wanting to screw things up and all... Martin
Something about yourself and your interest in Pd is always nice to see. That way we can know something about each other besides the regular pd-list emails...
.hc
I just repeat that I wouldn't have any objections. Ciao
________________________________________________________________________ ____
"Looking at things from a more basic level, you can come up with a more direct solution... It may sound small in theory, but it in practice, it can change entire economies." - Amy Smith
-
cyrille henry -
Frank Barknecht -
Hans-Christoph Steiner -
IOhannes m zmoelnig -
Martin Peach -
Mathieu Bouchard