Skip to content

Communication between VD-Widgets #3

Description

@aleastChs

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]

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions