Combine mxcubecore and mxcube3 queue handling
Created by: rhfogh
MXCuBE3 has done a lot of additional work on queue handling, wrappers etc. The main body is in utils/queue.py (was qutils.py), with a parallel queue representation made up of nested dictionaries, and a series of functions that make, populate and deal with queue entries using a dictionary representation of the class contents as parameters. This allows more flexible handling of the queue, and the dictionary parameters (whether they are attractive or not, in the abstract) are necessary to fit with the MXCuBE3 interface. If I am misrepresenting this, other people can hopefully correct me.
The question is whether we should move all this additional queue functionality into mxcubecore. The advantages would be having the queue in one place only without potential duplication, having all functionality available whatever UI and branch you were using, and having both branches work off a single queue model.It would however be a certain amount of work (which i am willing to contribute to), and there might in theory be problems with code that was designed for MXCuBE3 being either less useful or hard to generalise (not that I know of any such).
Anyway the big question is more strategic - how we want the queue to be organised, and how (and how fast) we want to move there. Could we have a discussion about that