Removal of QT from OpenMS core

[dmccloskey]

Description

Several core classes utilize QT components. The use of QT in the core OpenMS API is not desirable due to QT licensing considerations. Replacement of QT components with standard types or custom types (e.g., QTString with std::string) or sandboxing of QT reliant classes (e.g., Mascot) during build would be desirable. The end goal is to allow a user to utilize the core OpenMS packages without the need for integration with QT.

Objectives

• [ ] Replace as many QT components with standard types in the core OpenMS API as possible
• [ ] Sandbox QT reliant classes during build

[dmccloskey]

Step 1: action plan for removing/isolating QT dependencies

• What classes are using QT? What QT modules within the classes are being used?
• What alternatives are there to the QT modules?