A useful feature addition to the GUI version/s, at some point, might be an embedded terminal window.

I'm mainly thinking about how to make the full functionality of ChordPro most accessible to users who've only ever used GUIs (primarily Windows/Mac users I guess). More of this sort of thing might emerge as I put myself in the naive user's shoes for writing a tutorial guide.

It's a feature I'll often use in Geany, and wonder if it might ease the transition from GUI to CLI for some users.

Rationale

CLI is essential for fully exploiting ChordPro functionality.
Embedded terminal provides immediate CLI access from within ChordPro (GUI) without separate terminal window, so it feels like using the same software, and staying in the same world.
Reduces the need for a whole terminal/CLI primer as part of user guidance.
Provides a known environment on which to focus user guidance (i.e. less need for OS-specific guidance on using terminal).
Potentially also convenient for more experienced users.

Queries

Could embedded terminal default to the path of the currently-open document? That would avoid need to use of cd or specify full path to song, by people more familiar with clicking through folders.
When run in embedded terminal, should ChordPro command automatically inherit/add options from GUI Preferences, e.g. selected configs, transposition library?
Could the resulting PDF somehow be displayed automatically, based on viewer set in Preferences?
The need might reduce if/when more ChordPro functionality becomes available via GUI, but I'm guessing that's unlikely in the near future.

A different or additional approach might be a Preferences setting in GUI, which provides a text box for additional ChordPro command options. When running with Preview command, those options would then be applied in addition to those specified with graphical Preferences.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.