• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ChordPro & ABC Text Display Settings
#1
"Text Display Settings" has two entries named "Chord Size". They should be named in a way that shows clearly which one changes the chord size for the lyrics & chords sections and which one changes the chords of chord grid sections. It is required to keep different settings for these two parts.
Separate settings should be possible for more ChordPro elements: chords, grid chords, lyrics, chorus, comment, comment italic, subtitle ... Not only size but also colour, bold, italic, font ... I requested that since the very beginning of ChordPro support in MobileSheets. That would probably require a redesign of the "Text Display Settings" dialog and changes in the database.
A different font should at least be possible for chords. My favorite font for chords is MuseJazzText as in MuseScore. It is public domain and available here: https://github.com/musescore/MuseScore/t...s/musejazz
The same chord font should be used for ABC sections, chord grids and lyrics & chords

Attachments:
BengerzBrauneBrieh_F_3.9.1.jpg shows the output of MobileSheets 3.9.1 on my Android phone
BengerzBrauneBrieh_F_ChordPro_6.050_029.pdf shows the output of the ChordPro reference implementation V 6.050_029
BengerzBrauneBrieh_SHe_ABC.pro is the ChordPro source
CPCHe_20_MuseJazzText.json.txt and CPCHe__General.json.txt are the config files that I used in ChordPro to create the PDF, just in case somebody wants to reproduce it.

By now MobileSheets 3.9.0 and 3.9.1 are still missing in the Microsoft Store.


Attached Files Thumbnail(s)
   

.pdf   BengerzBrauneBrieh_F_ChordPro_6.050_029.pdf (Size: 160.78 KB / Downloads: 4)
.pro   BengerzBrauneBrieh_SHe_ABC.pro (Size: 1.89 KB / Downloads: 5)
.txt   CPCHe_20_MuseJazzText.json.txt (Size: 1.34 KB / Downloads: 4)
.txt   CPCHe__General.json.txt (Size: 4.8 KB / Downloads: 5)
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 22H2 - Huawei Media Pad T5, Android 8.0 - Boox Tab Ultra C, Android 11
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de


Reply
#2
With how many settings you are talking about, I think I would prefer to place it all on a fullscreen UI that is completely separate from the existing dialog, and I imagine most users would configure defaults for it that wouldn't need to be overriden per song. So I would create a new database table for these new advanced settings that wouldn't be populated per song by default unless the user checks a box to override the defaults. That way I'm not storing tons of data in the database that is rarely if ever used.

When it comes to custom fonts, it's a little bit of a can of worms if I let users provide their own fonts, as then I have to store that font as part of the library so it's included in backups, exports, etc, otherwise it won't load properly on other devices. Or I could take an entirely new approach to it and have a different part of the settings where users can import fonts, and this would only be stored on the current device, and users would have to install those fonts on their other devices in order to view the chord pro file with those fonts. This doesn't work well at all with my current way of handling fonts, but I'd have to adjust things to account for it. If I just add support for that font you provided, that's not as big of a deal, although it still requires quite a few changes.

When it comes to ABC sections, I'll revisit that when/if I can integrate abc2svg, and then see what is required to feed it custom fonts, because I imagine things are going to get weird with the embedded javascript engine when it comes to accessing local files. 

As far as the Microsoft Store, version 3.9.0 was available since like Wednesday I think. I'm not sure why you are unable to update, because the Microsoft Store certainly shows that it is available.

Mike
Reply
#3
Maybe the Microsoft Store is providing updates later in Germany. So I still have to use 3.9.0 on Win 10.

My goal is being as compatible as possible with Sciurius' reference implementation, meaning that a single source file produces a very similar appearance no matter if it is displayed in MobileSheets directly or if I create a PDF in Sciurius' ChordPra and use that.
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 22H2 - Huawei Media Pad T5, Android 8.0 - Boox Tab Ultra C, Android 11
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de


Reply
#4
Imho it's not necessary that users are able to install their own fonts. Just the possibility to chose different fonts for chords and the rest of the score and a handwritten looking font for chords would be great. It would be perfectly fine if MobileSheets included such a font in its installation, that's how it is also the case in MuseScore which also doesn't install its fonts in the OS's font directory but integrates them somewhere in the installation files. The font files on github are provided additionally in case somebody wants to use them for other purposes like ChordPro or (hopefully soon) MobileSheets. I proposed MuseScore Jazz because it is open source, well known from its usage in MuseScore, it is loking nice and comes with "real" sharps and flats.
Default settings for all songs with the possibility to overwrite them for the one or the other song would be great. The settings for page scaling and display mode and the new fixed page settings are implemented like that in a great way. I myself would use the same fonts for all my songs, overwrite colours every now and then and set individual font sizes for every song.
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 22H2 - Huawei Media Pad T5, Android 8.0 - Boox Tab Ultra C, Android 11
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de


Reply
#5
Thanks - I appreciate that feedback. Packaging the font is much easier.

Mike
Reply




Users browsing this thread:
2 Guest(s)


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2024 MyBB Group.