Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Communication between VD-Widgets #3

Open
aleastChs opened this issue Jun 20, 2018 · 0 comments
Open

Communication between VD-Widgets #3

aleastChs opened this issue Jun 20, 2018 · 0 comments
Labels
Milestone

Comments

@aleastChs
Copy link
Contributor

aleastChs commented Jun 20, 2018

Right now we have quite tricky structure for the model-information to get to APIVirtualDevice etc. Most is happening in backend/.../modelSupport/ModelService.scala and it would be nice to have a better structure for this.

One idea is to implement this information with the new Model-curcuit or in a new parallell circuit depending on the Model-Curcuit.

Suggestion of Curcuit-info

  • Current Model
  • All driverThings from model/ or all drivers with thingToDriver
  • All resources / resourceThings
  • All operationThings from model
  • All abilities from model
    Right now it is happening with operationToAbility
  • The states + status of the drivers
  • The states + connections between resource and driver
  • The states/conditions of the abilities
  • The states/conditions (or domain) of the operations

This Information is maybe needed

  • Current Runner?

[This issue is in progress]

@aleastChs aleastChs changed the title Communicatio between Widgets Circuit Communicatio between VD-Widgets Jun 20, 2018
@aleastChs aleastChs changed the title Communicatio between VD-Widgets Communication between VD-Widgets Jun 20, 2018
@aleastChs aleastChs added this to the ToDo milestone Jun 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant