WTKX IDs are not exposed outside the serializer (except via the
serializer's Dictionary interface). We could try to repurpose them to
suit this use case as well, but I don't think that's the right
approach, since it would preclude performing automated testing on UIs
that were created in code (not via WTKX).
In order to support what you are describing, we might want to add an
"automationID" property to Component. External code could use this
obtain a reference to a component and then invoke methods on it.
In this way we could also expose a sort of Macro/Scriptable System for
Pivot (without a macro language, ok but this is a detail at the
moment) ... cool.
Rather than creating a new macro language, why not simply take
advantage of the existing scripting facilities in the JVM?
