Store organisation

Created by: marcus-oscarsson

Good morning,

I thought it would be a good idea to separate "server-side data" and "presentation data" in the store. With "server-side data" I mean data that represents something on the server like motors, the queue, etc and with "presentation data" something that is related to the state of a component.

I think this will lead to a clearer organization of the data where its easier to share data between different parts of the application. This will remove the problem of potential discrepancies between data. I'm as you know currently working on unifying the queue used by the SampleGrid and the SampleQueue. However the same also applies to the list of samples and motors.

My suggestion would be to use the beamline store for everything related to beamline hardware and the queue store for the queue and list of samples.

This means that the things related to the state of the SampleQueue components needs to be moved from the queue store to a new store called for instance SampleQueueView. Further, the motors needs to be moved from sampleview to beamline.

What do you think about this idea ?

Regards, Marcus