purepd WAS: Re: [PD] comport and bascom avr / ascii2any

[Frank Barknecht]

Hallo,
Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:

> On Nov 18, 2005, at 6:14 PM, Frank Barknecht wrote:
> >At first I thought: No way, you'd need at least [list2symbol] for
> >that, which is impossible to build with just internal objects. Then I
> >said to myself: Hm, maybe it's not impossible? Then I said down and it
> >wasn't even that hard to do a [list2symbol] clone using just builtins:
> >list-2s.pd is attached. Oops, there goes another external previously
> >used in RRADical ... ;)
> 
> That's great!  I've started a project I call "PurePd".  Whenever I get  
> inspired, I write a Pd patch that is a clone of a useful external.  I  
> just added it to abstractions/purepd and the build system.  It would be  
> great if you could contribute this patch as [list2symbol] and anything  
> else that you can think of.  I have a Max-style [counter], [speedlim],  
> and even a [metro] in the works.

I already added it to the [list]-abs renamed to "list-l2s", because
maybe there will be a "list-s2l" later, too. Although I currently
think: No way to do this without externals, but who knows ... ;) 

I think, in this case it feel natural to put it in [list]-abs, as it
is dealing with [list] and is technically very similar to the other
list abstractions I did. 

I'm not really convinced that the PurePd objects should carry the same
name as the externals they replace. I see, that these makes them
instant replacements, however some externals like the infamous
[counter] and [scale] are already in name-clash with differing
functionality, and to add another version then doesn't seem right. I'd
tend to prefer a prefix-namespace for such stuff, like I did for
list-abs and also in rrad.ical (which has a rrad.scale.pd for
example). 

I like the sound of something like [pure.scale], which is attached
(though still missing the log. scaling...)

Ciao
-- 
 Frank Barknecht                 _ ______footils.org_ __goto10.org__
-------------- next part --------------
#N canvas 236 224 830 538 10;
#X obj 166 328 expr ($f1-$f2)*($f4-$f5)/($f2-$f3)+$f4;
#X obj 252 286 f \$1;
#X obj 402 288 f \$4;
#X obj 352 284 f \$3;
#X obj 302 284 f \$2;
#X obj 252 197 inlet;
#X obj 302 197 inlet;
#X obj 352 197 inlet;
#X obj 402 197 inlet;
#X obj 166 129 inlet;
#X obj 166 369 outlet;
#X text 510 173 ARGS;
#X text 520 197 1: input_low_border;
#X text 520 219 2: input_high_border;
#X text 520 245 3: output_low_border;
#X text 520 267 4: output_high_border;
#X obj 273 243 t b;
#X obj 298 171 loadbang;
#X obj 166 156 t f b;
#N canvas 586 431 389 352 once 0;
#X obj 139 41 inlet;
#X obj 169 200 outlet;
#X obj 169 164 spigot 1;
#X obj 139 69 t b a;
#X obj 220 140 0;
#X connect 0 0 3 0;
#X connect 2 0 1 0;
#X connect 3 0 4 0;
#X connect 3 1 2 0;
#X connect 4 0 2 1;
#X restore 196 186 pd once;
#X text 229 132 scale linearily [from_low \, from_hi] to [to_low \,
to_hi];
#X text 165 412 [pc once] is only used \, because autogenerated objects
don't receive loadbangs \, and I needed to initialise this object even
when using internal message generation.;
#X connect 0 0 10 0;
#X connect 1 0 0 1;
#X connect 2 0 0 4;
#X connect 3 0 0 3;
#X connect 4 0 0 2;
#X connect 5 0 1 0;
#X connect 6 0 4 0;
#X connect 7 0 3 0;
#X connect 8 0 2 0;
#X connect 9 0 18 0;
#X connect 16 0 1 0;
#X connect 16 0 3 0;
#X connect 16 0 4 0;
#X connect 16 0 2 0;
#X connect 17 0 16 0;
#X connect 18 0 0 0;
#X connect 18 1 19 0;
#X connect 19 0 16 0;