Orange Restricted Mode

[mw25]

We usually have some people creating Orange workflows for certain evaluations. If they are happy with it, the workflow stays as it is and other people run it again and again with new data.

To make Orange as reduced as possible for the workflow executors, to avoid errors and to avoid changing the workflow (intentionally or by accident), I would like to see some kind of runtime mode for Orange with the following features:

• All categories at the sidebar are hidden (This is already possible via the settings).
• The workflow can no longer be changed (add and delete widgets and connections)
• Single selected widgets can still be configured, e.g. File Import.

Proposed realization:

• You can save a workflow as "locked" or "restricted" (Using the save as dialog).
• A new dialog appears, which lists all widgets of the workflow together with a checkbox. This can be used to set which widgets should remain configurable.
• This gives the .ows file a flag that the workflow is locked and each widget a flag if it is still configurable.
• When such a workflow is opened, Orange behaves as described above.

It's not about security (of course the flags in the .ows file could be reset by hand with an editor), but about ease of use and error prevention.

The topic is somewhat related to #144, but in contrast here the user should still be able to interact with the workflow (for data selection and evaluation he has to), but only at certain points.

Would you agree to such an extension in principle? I would take care of the implementation - if necessary with some startup help, since I have only developed my own widgets so far, but have not yet contributed to the Orange core.

[ajdapretnar]

That's a very interesting idea, thank you! I am generally in favour (but my vote has a low weight ;)).