MuseScore Plugins_Plugin Manager Listings - Every QML file listed even if it cannot be executed as a plugin.

workaround: name those secondary files .js

Since the Plugin manager relies on the .qml suffix to find plugins, I think the best solution is to move the non-plugins to a sub-directory (maybe call it addons?) and edit the plugins that used these so they will look in */addons for these files. I'm not familiar with the language, but there must be an easy way to look in a sub-directory for a file.

Fixed in branch master, commit ec7d9a85d7

fix #275268: don't list non-plugin QML files in Plugin Manager

How does it distinguish with this fix in? What is the protocol? How does one reference/include a "subroutine" file from a QML extension?

a subroutine is looking to see if there is a meta-information in the file.

I see, this, a MuseScore object? That's all I see of meta-information in operative plugins.

MuseScore {
version: "3.0"
description: "This plugin adjusts the timing of an appoggiatura."
menuPath: "Plugins.Appoggiatura"

Yes, MuseScore plugins are those QML files where root object is MuseScore. In any QML files you still can use other QML components, including those you defined manually in other .qml files, this patch changes nothing in that regard. The change is that Plugin Manager won't anymore display QML files other than those that can be loaded by MuseScore as plugins (that is, they must define MuseScore as a root object and contain no syntax or other errors preventing QML engine from loading the file).

Does one use include, import, or require to import non-plugin-root js files into plugins?

This was a problem with e.g. the QuarterTonePlayback plugin, which has 3 .qml files, but only one that is to be loaded into the Plugin Manager. Same for the TuningCents plugin, but see the initial report

> Does one use include, import, or require to import non-plugin root js files into plugins?

For QML files no imports are required, it is enough to put the files in the same directory and use the components defined there just by their names. Imports may be required for importing pure JavaScript (.js) files or if you decide to group .qml files into modules within separate directories (which shouldn't probably be necessary for most plugins).

The best reference on how to use this feature is probably Qt documentation itself:
https://doc.qt.io/qt-5/qtqml-documents-definetypes.html
https://doc.qt.io/qt-5/qtqml-javascript-resources.html

Great, just what I needed, thanks (although the management of shared code between different plugin versions is another ball of wax). By the way, all my new stuff, including use of the onRun fix, works perfectly in a Mac build from "master" a short while ago. I look forward to tonight's nightly.

you are aware that 'nightlies' are not really that anymore (and since quite long), but get created immediatly after a PR gets merged?
So the 'nightly' containing that change is available already...

That's also why they are called Development Builds nowadays.

@#$@#$@#? !? !!!!! 😀!

pardon?

Übersetzung: "What the ... ?" "huh?" "oh, wow." "Oh boy! Great!"

;-)

Hold the champagne. The onRun fix does not seem to be in the 0734 build. Perhaps I have to wait a while.

it should be. No build is pending

Edit, but the Mac build failed: https://travis-ci.org/musescore/MuseScore/jobs/565383197
It timed out...

"Other than that, Captain Smith, everything is fine ...." Well, that explains it.

Been building for 10 min. on that page; I assume will time out again. Who's in charge of fixing it?

Anatoly and/or Dmitri. I notified them via Telegram

It is running now
https://travis-ci.org/musescore/MuseScore/jobs/565383197

And finished

Automatically closed -- issue fixed for 2 weeks with no activity.

No fixed as far as the plugin manager is concerned.
This my file b.qml:

import QtQuick 2.0
import MuseScore 3.0

Rectangle {
onDeleted: {
console.log("hello world")
Qt.quit()
}
}

It still gets listed in the plugin manager:

And what if it's already in the list, is it removed in some way?
I think collectPluginMetaInformation() should also be called [here](https://github.com/songchaow/MuseScore/blob/plugin-manager/mscore/plugi…] and it should be removed from the list if needed.

Seems that bool collectPluginMetaInformation(PluginDescription* d) is OK with reading no (or empty) version and description?

No, if I create a qml file in one of the directories MuseScore checks for plugins, with the content of your example about, it does not get listed as an available plugin.
Not sure how you managed to get it there? Also using MuseScore 3.3.2?

Just tried on another computer and could not reproduce.
I will try again monday. But I suspect that I was under 3.

oops, wrong label