Updating PLR API for machine interfaces discussion

[vcjdeboer]

@rickwierenga

Mostly a topic for the main architecture thread, but will answer briefly here. The idea is the Device (object user creates) will orchestrate different capabilities, so

class TecanInfinite:
  def __init__(self, ...):
    self.driver = TecanInfiniteDriver(...)
    self.absorbance_reader = AbsorbanceReader(backend=InfiniteAbsorbance(driver=self.driver))
    self.temperature_controller = TemperatureController(backend=InfiniteTemperatureController(driver=self.driver))
    self.shaker = Shaker(backend=InfiniteShaker(driver=self.driver))

The capabilities are universal, and mimic the existing front/backend pattern. In this specific example I assume we have different InfiniteAbsorbance, InfiniteTemperatureController, InfiniteShaker objects (I assume we want this for big backends), but we can also have TecanInfiniteDriver implement AbsorbanceReaderBackend etc. directly.

since you referred to this thread, i might as well reply here.

I think this Infinite example is confusing.

We can easily split concrete backends, but you are making abstract backends for specific devices. Can you clarify?