This is a great idea! I'll pursue creating an OutlineHandler component that forces itself to the highest z-order and then waits for other components to tell it where to draw an outline. Much better than having an outline component for every component.
This should work very well extending the AbstractVisionShape class, as it allows you to specify an area for mouse-hit testing. So I can make the bounds of the OutlineHandler the same as the Container it is on and give it no area at all, so that the mouse never hits it.
My Component Spotlight resource on the exchange behaves in this way. It maps every component in the window at initialization, and then dynamically creates a flashing, semi transparent, abstract vision shape around the component to highlight where it is in the window. It's scripted in Jython, so it won't directly translate to what you're doing, but it's possible that it would be useful to look at how it crawls through and maps nested components as well as components that are rendered by template canvases and repeaters so it can accurately place the shape no matter what it's relative placement within the window ends up being.
