Use PropertyWidgets in Custom Dialogs

[Peter Parker]

The dynamically-generated algorithm dialogs use PropertyWidget objects. The customised algorithm dialogs (and perhaps others) should be made to use them too. This will make things more consistent, both visually and within the code, it will avoid code duplication, and will also allow make the #2480 functionality more widespread.

No work required:

• SmoothNeighbours - (Already uses PropertyWidgets fully)
• LoadDAE - (Deleted algorithm)
• LOQScriptInput - (Deleted algorithm)

Work required:

• CatalogPublish
• ConvertTableToMatrixWorkspace
• CreateSampleShape
• Fit
• LoadAscii
• Load
• LoadInstrument
• LoadRaw
• PlotAsymmetryByLogValue
• BinMD - (SlicingAlgorithmDialog)
• SliceMD - (SlicingAlgorithmDialog)
• StartLiveData

[Nick Draper]

Moved to Backlog at the code freeze of release 3.2

[Peter Parker]

Refs #9149 - Remove CustomDialog for CatalogPublish algorithm.

Instead use IPropertySetting objects to handle property complexities.

Eagle-eyed code reviewers will note that these changes don't work very well with composite catalogs, but neither did the custom algorithm dialog in its previous form. This will need to be revisited when composite catalogs are finished. In particular, what should be the allowed values of the InvestigationNumber property given multiple session IDs? How should the allowed values (as well as the default value) of the SessionID property change as well?

Also, for now, "FileName" and "InputWorkspace" are back to being on two separate rows in the dialog.

Changeset: 1ea0c96794db10400eda8d5285dafdb5f8764171

[Peter Parker]

Refs #9149 - WIP. Needs rebasing.

Changeset: c0903658d992371996beafa4f260408c2db28cb7

[Stuart Campbell]

This ticket has been transferred to github issue ​9992