Investigate using factory pattern

[MarcusNoble]

For user's scripts, look into the possibility of using a factory pattern to enforce variable names and method names.

[Alex Buts]

Hi, Marcus,

If you doing this, the example of the implementation of this pattern in Mantid is in ​https://github.com/mantidproject/scripts/blob/master/test/runIndividualFromGUI.py

Row 45 has to be modified to check the users directory for the files user put into.

Rows 67-80 -- modified to identify the children of your interface class (e.g. have the methods you need)

and then rows 82-85 will run your interface commands.

[MarcusNoble]

Notes from chat with Alex:

• Factory pattern
• Add a location on autoreduce for mask files etc. Add this location to the Mantid datasearch.
• Look at Mantid defaultsave.directory and setdatasearchdirs
• WB could possibly be a different cycle (but mantid file opened should handle this)
• Specify paths (for masks etc.) in factory class's init?
• Specify in factory class that it is being run from WS (boolean flag)

[Alex Buts]

And I've analysed the way of running a factory methods if mantid is not available and it is easy as soon as Mantid imports are in try: except blocks. The only question is where to place the interface file to be available both for the server and for a Mantid user.

Minor edit is needed for my reduction wrapper decorators