Move IInteractive into separate module

[cbjeukendrup]

Some parts were in global, some parts in ui, some parts in ui/qml/Muse/Ui/Dialogs. Move as much as possible into a new interactive module. Only InteractiveProvider is too tightly coupled to the ui module to be able to move it.

[igorkorsukov]

Only InteractiveProvider is too tightly coupled to the ui module to be able to move it.

Could you please remove the interactiveProvider from uiengine... Make interactiveProvider as a regular QML element and create it in InteractiveProvider.qml. This is also necessary for multi-window.

InteractiveProvider.qml

Item {
    id: root

    property var topParent: null
    property alias provider: _provider
    ...

    CppInteractiveProvider {
        id: _provider
    }

InteractiveProvider::InteractiveProvider()
    : QObject(), Injectable(muse::iocCtxForQmlObject(this))
{

[cbjeukendrup]

Working on this; the challenge is https://github.com/MuseScore/MuseScore/blob/ae198102bc182ab62ddfdf7ab131442f40329582/src/framework/ui/uimodule.cpp#L96.

[igorkorsukov]

I got it... then I think so

• CppInteractiveProvider - regular service, in internal (not part of the Qml module), but inherited from QObject
• Add an accessor to the Qml module of interactive

InteractiveModule::::registerExports()
{
ioc()->registerExport<IInteractiveProvider>(moduleName(), new InteractiveProvider());
}


class InteractiveProviderAccessor : public QObject 
{
         QML_ELEMENT
         Q_PROPERTY(InteractiveProvider * provider READ provider CONSTANT)
         
         Inject<IInteractiveProvider> interactiveProvider;
}

InteractiveProvider *  InteractiveProviderAccessor::provider()
{
     return qobject_cast<InteractiveProvider>(interactiveProvider().get());
}

Item {
    id: root

    property var topParent: null
    property alias provider: accessor.provider
    ...

    InteractiveProviderAccessor {
        id: accessor
    }

[cbjeukendrup]

I've gone a step further: instead of exposing the InteractiveProvider object itself to QML, its methods and signals are provided via InteractiveProviderModel.
And then I decided there is no good reason to keep InteractiveProvider separate from Interactive, so I merged them.

Possible future steps:

• Eliminate InteractiveProvider.qml - it doesn't seem to do anything that cannot be done in C++
• Rename InteractiveProvider... but to what?