[PD] "get" method for Pd

[Jonathan Wilkes]

----- Original Message -----
> From: Hans-Christoph Steiner <hans at at.or.at>
> To: Miller Puckette <msp at ucsd.edu>
> Cc: pd-list at iem.at; IOhannes m zmoelnig <zmoelnig at iem.at>
> Sent: Thursday, November 17, 2011 1:01 PM
> Subject: Re: [PD] "get" method for Pd
> 
> 
> I like "info" too, maybe [pd info(.  I like Jonathan's ordering 
> because it also makes it easy to have a default receive symbol, so :

Miller said "object", so I'm assuming he meant [info] (though I don't think anyone 
else agreed that it would be the right approach).

Benefit:
* [info] would have a help patch, so it would be easier to document, plus avoid 
the confusion of the pd receive symbol with the [pd] canvas

Benefit of [; pd info(
* easier to code, plus it fits nicely with the extend implicit set methods katja 
mentioned -- [; pd dsp 1( etc. (i.e., using the currently existing methods to 
set attributes)

Maybe others have benefit/drawback ideas?

> 
> [;pd info(
> 
> would dump all the info to:
> 
> [receive pd]
> |
> [route info]
> 
> Then you could also specify specific things to request:
> 
> [; pd info dsp(
> 
> would dump:
> 
> [receive pd]
> |
> [route info]
> |
> [route dsp]
> 
> As for GUI-related things, I think 'pd-gui' should have its own 
> 'pd-gui' receive listener, so you direct GUI-related stuff to [send 
> pd-gui].

I agree these should be separated.

> 
> .hc
> 
> On Nov 17, 2011, at 12:13 PM, Miller Puckette wrote:
> 
>>  Unfortunately I already used the name "get" for something else 
> but I
>>  agree this should be an object, maybe 'get-info" or even just 
> "info".
>>  It could get and/or set info about the canvas it's in as well as about
>>  other canvases (by name) and Pd globally.  
>> 
>>  cheers
>>  Miller
>> 
>>  On Thu, Nov 17, 2011 at 03:12:08PM +0100, IOhannes m zmoelnig wrote:
>>>  -----BEGIN PGP SIGNED MESSAGE-----
>>>  Hash: SHA1
>>> 
>>>  On 2011-11-17 15:09, IOhannes m zmoelnig wrote:
>>>>  On 2011-11-17 14:53, Patrice Colet wrote:
>>>>>  Hello,
>>>>>  would this method provide patch window size and position?
>>>> 
>>>>>  [; pd get size pd-mpatch.pd rcv_name(
>>>>>  [; pd get pos pd-mpatch.pd rcv_name(
>>>> 
>>>>  now we are getting close to why i think using "get 
> <rcvname> ..." is
>>>>  better than "get <verb> <rcvname>"
>>> 
>>>  but of course jonathan and roman are right when they say that this is
>>>  not something you would ask "pd" about.
>>> 
>>>  fgamsdr
>>>  IOhannes
>>>  -----BEGIN PGP SIGNATURE-----
>>>  Version: GnuPG v1.4.11 (GNU/Linux)
>>>  Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>> 
>>>  iEYEARECAAYFAk7FFjgACgkQkX2Xpv6ydvRjGACeKhVGEDtrXIhGi3tZlmLBpVYx
>>>  nkwAn1JsM8C6tVj95ZTHCAAhbz0d7A1z
>>>  =XrRZ
>>>  -----END PGP SIGNATURE-----
>>> 
>> 
>> 
>> 
>>>  _______________________________________________
>>>  Pd-list at iem.at mailing list
>>>  UNSUBSCRIBE and account-management -> 
> http://lists.puredata.info/listinfo/pd-list
>> 
>> 
>>  _______________________________________________
>>  Pd-list at iem.at mailing list
>>  UNSUBSCRIBE and account-management -> 
> http://lists.puredata.info/listinfo/pd-list
> 
> 
> ----------------------------------------------------------------------------
> 
> Access to computers should be unlimited and total.  - the hacker ethic
> 
> 
> 
> _______________________________________________
> Pd-list at iem.at mailing list
> UNSUBSCRIBE and account-management -> 
> http://lists.puredata.info/listinfo/pd-list
>