Description
I'm currently working with my own job using vizicities 0.2.0 and found out that current VIZI.BlueprintSwitchboard supports only single input, single output. It's hard for me to understand why it's implemented (or even specified) this way, because current trigger configuring structure looks as though there are many independent inputs/outputs, and switchboards are designed to connect them sparsely. Wasn't that the reason you chose event (trigger)-driven messaging for ViziCities?
For example, let's have a look at the current basic-example. You may see there are three VIZI.BlueprintSwitchboard instances used for. Why are three instances necessary? One isn't enough?
I strongly desire multiple inputs/outputs support for VIZI.BlueprintSwitchboard, because the custom BlueprintOutput*****.js I'm currently working on requires multiple input source - image map tile and KML.
I've looked inside VIZI.BlueprintSwitchboard and found out that the current VIZI.BlueprintSwitchboard implementation ignores instantiating with input/output configuration (actually throws an Exception) where the key names aren't strictly "input" or "output". In the other side, trigger configurations require "triggerObject" element, which is expected to set "input" or "output" (strictly).
My opinion is to take away this name-based constriction. Make it available to set names like "input2" or "OSMTileInput" or something like that, and use the same name for "triggerObject" elements.