This is not the only plugin affected, see #15609: many plugins don't load in trunk.
Not sure wether this is a general issue with the plugin framework or an issue with the indivudual plugins.
The requirement to enable the plugins was done in the trunk quite some time ago and I suspect this is one of the underlying changes in 2.0 that will frustrate people. I wonder why it is necessary?
Using the latest trunk version on OS X, I couldn't find out how to install the plugin. I tried copying console.js to various folders, as suggested in the handbook
. The plugin didn't appear to the list in Preferences, and nothing changed in the Plugins menu. Perhaps I'm doing something wrong? I'd appreciate step-by-step instructions.
I have started an attempt to update this plugin to work with 2.x, but I'm lacking basic information about the QML format which is blocking progress. For example the original code defines a ScriptConsoleMainWindow prototype, but I have no idea how to do this in QML. Advice appreciated.
This plugin was basically the predecessor of the 2.x (and 3.x) Plugin Creator.
Many of the things it refers to are simply not existent in a QML environment or no longer required.
None afaik.
It basically used the input given and eval'd it as the body of an onRun loop in the current Plugin Creator. What it left out was the wrapping plugin instantiation and windowing code and it offered the inclusion of the MuseScore namespace (just as a default plugin does now).
So feature-wise it would currently be identical to open the Plugin Creator, start a new plugin and put whatever you'd want eval'd into the onRun function. The press the run button.
The only additional thing for your REPL is the 'P' part, which isn't handled by default, so you must include console.log() statements at the return value point of onRun to mimic the old plugin behavior.
Comments
This is not the only plugin affected, see #15609: many plugins don't load in trunk.
Not sure wether this is a general issue with the plugin framework or an issue with the indivudual plugins.
Sorry, EBKAC... needed to enable the plugin in preferences...
EBKAC?
The requirement to enable the plugins was done in the trunk quite some time ago and I suspect this is one of the underlying changes in 2.0 that will frustrate people. I wonder why it is necessary?
Error Between Keyboard And Chair ;-)
Esp. as this is not the first time I personally stumble across this...
So I've now added this to the handbook
Using the latest trunk version on OS X, I couldn't find out how to install the plugin. I tried copying
console.jsto various folders, as suggested in the handbook . The plugin didn't appear to the list in Preferences, and nothing changed in the Plugins menu. Perhaps I'm doing something wrong? I'd appreciate step-by-step instructions.The plugin is not compatible with the current trunk. It needs to be rewriten. In trunk you can use the plugin creator instead.
Automatically closed -- issue fixed for 2 weeks with no activity.
I have started an attempt to update this plugin to work with 2.x, but I'm lacking basic information about the QML format which is blocking progress. For example the original code defines a ScriptConsoleMainWindow prototype, but I have no idea how to do this in QML. Advice appreciated.
This plugin was basically the predecessor of the 2.x (and 3.x) Plugin Creator.
Many of the things it refers to are simply not existent in a QML environment or no longer required.
OK thanks, so which are the features of this plugin which got lost in the switch to the Plugin Creator? I was hoping for a REPL loop at least.
None afaik.
It basically used the input given and eval'd it as the body of an onRun loop in the current Plugin Creator. What it left out was the wrapping plugin instantiation and windowing code and it offered the inclusion of the MuseScore namespace (just as a default plugin does now).
So feature-wise it would currently be identical to open the Plugin Creator, start a new plugin and put whatever you'd want eval'd into the onRun function. The press the run button.
The only additional thing for your REPL is the 'P' part, which isn't handled by default, so you must include console.log() statements at the return value point of onRun to mimic the old plugin behavior.