Developer and test environment on Linux

• Jun 3, 2025 - 08:48

Hello,

despite the likelihood that this question was asked numerous times (even though I haven't found any in the past year and I find https://musescore.org/en/node/337468 a bit light), may I ask:

  • what is the recommended development environment (IDE) for plugins on Linux?
  • which IDE will support some kind of reflection to understand the object models?
  • what are the recommended patterns for tests that can be run at least on parts?

My current setup using VSCode/PyCharm is not great, also having to copy files from my repo checkout to the Musescore plugin area is slowing down development speed. A symbolic link did not help either. Without data models, debugging and testing, development is very tedious.

Kind regards,
peter


Comments

In reply to by ILPEPITO

Thanks for the prompt response; however, I am not quite sure what is not an OS problem.

For the past decades I have been developing software in various languages and IDEs; what allows progress is a decent IDE, to write code, create and run tests, and to debug, all now a bit of help with copilot.

In reply to by ILPEPITO

Thanks again for your help; I have already had a browse around several plugins to get some inspiration.

However, my main questions are still unanswered: what IDE supports qml development (syntax and most importantly object model of imported libraries), how to write and run tests, and how to make MuseScore "point" to a git repo.

In reply to by yonah_ag

I tried a bit with JetBrain's PyCharm which I have been using for years and am familiar with, I might try JetBrain's WebStorm (dedicated JavaScript). I will probably give QtCreator a go which I was using for many years in a previous job. Syntax high lighting is one thing, what I am really after is something that understands the object model, by being able to import the MuseScore bindings.

In reply to by Peter Wurmsdobler

MS object model would be really handy, so would intellisense on Qt objects for the UI design. The error logging from MS4 plugins is a bit of a pain as it's buried in one of MS4's log files. There's no live console output so I've resorted to using a pop-up QT window and writing to it with some Javascript.

Do you still have an unanswered question? Please log in first to post your question.