I think I found a way to make all connections wait to render themselves until after the pins have rendered. It assumes that when the connection is initializing itself, EITHER the is_safe_to_render() function will return true OR it is OK to at that moment start listening for the event that says when it will be safe. I think this works but that it would be more element with a promise. also I have not had a chance to test this yet
more edits, want to switch branches
Merge branch 'master' into sync-connections
connections get drawn! at least the first time...
working on it
fixed merge conflicts
working on it
fixing merge conflicts
it works to just refer to the node server by ws://localhost:8001
fixed typo in comment
merged in refactor-pins and made it so that it actually works.
comments and adding TODOs
just leave the connections in #field not in #container
reformatted and commented the debug log section of index.html
fixed the bug where the pin initializer was getting called twice for each connection directive. the problem was that having the html attribute data-sensor on the connection was also linking in the angular directive indicated by sensor, and the same thing for actuator. so i changed the html data attributes on the connection to be data-sensor_id and data-actuator_id to avoid this conflict
took out the TODO about the last bug I just fixed where i was calling the sensor and actuator pin constructors inadvertently
pins know whether they are connected without storing it on the pin in the overall
can connect and disconnect elements without maintaining redundant state
added TODO
use pin names, not pin ids, when asking to delete a connection