Grey Nodes as Components

i've playing with manipulating single 'objects' within an image. an 'object' here is defined as a single element or part of a composite image, such as a single branch of a tree image or the mist in my waterfall filter. and, it occured to me that almost every single grey node of something like a perlin noise shld be a separate component. scale, stretch, angle, rotate, variation, detail, repeat, mirror, flip, etc, could all, and perhaps shld all, be made into components all by themselves. or perhaps it would be even better to combine all those into one component. you could call it a master control component or something.

the point is, i was trying to use the stretch in a perlin to stretch the source input and couldnt do it and i couldnt find any other way to do it, either. but if i had a component that was just called 'stretch' and it simply did that function to a source input, how simple. and that led to looking at all the rest of the gray node functions. we've certainly asked for some of these in the past. it can get very, very difficult to do some of these functions using the normal filters. look at uber's any angle rotate. it's a brilliant filter, but quite large and cumbersome. that function shld be a component.

and, there are others. a 'zoom' function has been done in several filters, but it shld really be a component. 'bend' comes to mind too as do several other distortion controls. in other words, the current internal gray node functions function on a given filter's internals, but not the source input. we need something to handle the source input manipulation.

ok, i know some of all this are redundant requests, but it just occurred to me that darn near every gray node function shld be a global function (acting on source images directly) as opposed to just internal functions to a given component.