musescore / musescore/MuseScore

Need a window to view console.log() output from plugins

Open
#34,266 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

community dev plugins
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Your idea

We need a window or file we can easily see console.log( ) output from plugins (some plugins do NOTHING but write to console.log(), i.e. they're analytical only.

I'm fine if it's only available when launched in debug mode, e.g. via DevTools tab or Diagnostics menu.

Problem to be solved

Some plugins are designed simply to analyse the current score at display info about it via console.log (e.g. "Score Duration", not sure where I got it from). And as a developer while working on a plugin, having some sort of debug output visible is pretty much essential.

Prior art

Was available in MS 3.x

Additional context

I've been told under Linux you can see the output in the terminal the executable was launched from. But it's definitely not possible in Window, even checking the debug output via a debugger nothing shows.

Checklist
  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the missing console.log() output on Windows and inspect the existing plugin logging and debug-output handling. Define a debug-mode window, DevTools view, or Diagnostics entry point that displays plugin output, then verify that analytical and development plugins can be observed without relying on a terminal.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop, devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.