Whenever I make a Dynamic Component, I feel very constrained… I wish I were just programming this in Ruby. Example, I needed a quadrant atan(), atan2() — it’s in Ruby, but not DC, so I had to create my own as a custom attribute. Or I need to compare different copies of a DC to compute something else. COPY is like being limited to a single index for loop. And attribute sharing is both limited (±1 level of inheritance) and opaque (random attributes are shared behind the scenes). Not to mention debugging, code organization, function encapsulation, etc.
So I can imagine a rich interface between the DC “porcelain” (esp. attribute editing and the interact tool) and a Ruby geometry plugin, including support for animate, etc. I understand from this discussion, that as of a couple years ago this simply wasn’t possible and other methods of user interaction were preferred by most plugin authors. Has this changed at all?
What’s a suitable workaround for wanting users to be able to use the “Interact” tool? Is there any callback possible from Interact to Ruby-land?