Resolve "Add the proposal session name"

Closes #52 (closed)

The attribute proposal is replaced by proposalname and proposalsession.

The state machine becomes

• OFF(1): nothing specified
• OFF(2): proposal name or session specified
• ON: proposal name and session specified
• STANDBY(1): proposal and sample are specified
• STANDBY(2): proposal, sample and dataset are specified (not started)
• RUNNING: proposal, sample and dataset are specified (started)

assigned to @denolf

added 2 commits

• e4dc36bd - typo
• a5474fee - add support proposal sessions

Compare with previous version

added 1 commit

• ad6a44ed - add support proposal sessions

Compare with previous version

changed the description

marked this merge request as ready

added 1 commit

• 69858a22 - add support proposal sessions

Compare with previous version

added 1 commit

• 10105ac9 - proposalName back to proposal

Compare with previous version

added 1 commit

• 8a2662f5 - proposalName back to proposal

Compare with previous version

added 1 commit

• 77d3a2ee - proposalName back to proposal

Compare with previous version

@holger.witsch Your macro's will be broken anyway, even if you keep proposal instead of proposalname.

Basically were there used to be one attribute, now there are two. I would say it even helps renaming proposal to proposalname because it will tell you exactly what parts of the spec macro's you need to change.

Using proposalname instead of proposal will prevent old Spec or Bliss versions from using the new API and vice versa. So I would say, keep proposalname.

added 1 commit

• a81a209f - proposalName back to proposal

Compare with previous version

added 1 commit

• ec84f8d7 - proposalName back to proposal

Compare with previous version

added 1 commit

• 01f5398b - Session and Beamline ID were inverted in the properties section of the code.

Compare with previous version

added 1 commit

• 723d1607 - proposalName back to proposal

Compare with previous version

merged

mentioned in commit 412dc66d