Comment 3 for bug 1408937

@Anatoly (welcome back ;-)
I principally understand what you are saying and your suggested approach.
But I have to admit, that this is far beyond what I can invest (both knowledge and time) into the further development of SikuliX.

SikuliX in the first place is a tool, to setup visual workflows basically doing this repeatedly:
wait for some visual to appear on the screen
... and then act on some point on the screen (mouse or keyboard)

... but often complained about:
1. Currently it has no knowledge about what the visual might mean to the human, just a bunch of pixels.
2. No support for moving a workflow to a different environment that shows the visuals differently on the screen in terms of pixels or with a different timing/animation.

With version 2 I will (besides improving the implementation of the API in many aspects) address these 2 areas:
at 1: allow to add more information to a visual, that allows to handle it in different situations (other rendering or background, color variants)
at 2: allow to work with image sets for different environments and support for the setup of these different sets based on an existing workflow

I think this will increase the usability of SikuliX, while staying manageable for me.

Nevertheless: Any ideas or contributions are always welcome.