iune / melbourne Goto Github PK

Currently, entrants who have already voted are not displayed any differently than those who are yet to vote. There should be an option to allow for the differentiation of the two categories.

• Possibly, entrants who have already voted could be distinguished by writing their name in italics
• Alternatively, we could have a little circle next to the entrant name indicating their voting status (which could also show if a participant is disqualified).

Note: this issue was manually transferred from GitLab.

Currently entry placings are not shown on screen in the scoreboards — viewers must manually determine the place for an entry themselves. There should be an option to display the entry placings next to the entries.

• Possibly, this could be done in grey color (possibly bolded) like the country and same size as points or vote.

Note: this issue was manually transferred from GitLab.

Currently, entries are split across two columns, regardless of how many entries there are. In smaller contests, it may be better to have a single column display of entries. Similarly, in larger contests, it may be better to have a three column display of entries.

• Add the option to set the number of columns to arrange the entries. (If the user selects more columns than there are entries, use the highest possible value for the number of columns.)

Note: this issue was manually transferred from GitLab.

Personally, I do not have a Mac so I cannot test nor verify the issue. Thus, I am just relaying it here.

Apparently, the .dmg releases of Melbourne for macOS do not work on newer Macs with ARM-based Apple silicon (for example, M1 or M2). The program name appears on the top left but just hangs.

Using Apple's Rosetta 2 translation did not help either. https://support.apple.com/en-us/HT211861

According to the link above, I guess the dmg releases would have to be of so called "universal" type in order to run both on Intel Macs and Apple silicon Macs. I am not sure how to package Melbourne that way.

Hi,

Michael, creator of fbs here. fbs is licensed under the GPLv3, which forces you to also put your project under the GPL. In other words, you can't use the MIT license. Kindly change it please.

Thanks!
Michael

Currently, it appears that the scoreboard generator is unable to set font weights to bold on macOS (specifically 10.14 Mojave). Programmatically, the appropriate font weight is set but the font shown in the scoreboard images remains at the regular weight.

This appears to be related to other upstream issues with QPainter/QImage as setting font weights to bold in the GUI works properly.

• https://codereview.qt-project.org/c/qt/qtbase/+/242476
• https://bugreports.qt.io/browse/QTBUG-69955
• https://forum.qt.io/topic/98943/qpainter-drawtext-bold
• https://forum.qt.io/topic/98943/qpainter-drawtext-bold/6

Currently, the application window size is set with hard-coded values depending on the operating system. This is not idea, as many factors have a role in how much size the window needs to fit its contents, such as DPI scaling, operating system, screen resolution, etc.

• Instead, the application should set its window size dynamically, depending on the size needed to fit its contents which cannot be predicted before hand.
• In addition, instead of preventing users from being able to resize the window, we should simply set the minimum size that the window can take (so that all the contents will always fit properly on screen), and allow users to make the window as large as they desire.

• Fix the algorithm used to determine the accent_text color as it does not properly determine when to use black and when to use white text colors.
• Add a menu to the application
  • Add shortcuts for selecting the input file (Ctrl+O) and selecting the output directory (Ctrl+Shift+O) to allow users to quickly choose these values
  • Add an About menu
• Refactor the existing "backend" code base
  • The Contest class should no longer have a name field since we are using the title field in the ScoreboardDetails class instead.
  • The generate_btn should check for invalid flags
• Build the application using fbs freeze and test the basic functionality of the program
  • Test on macOS
  • Test on Windows
  • Test using an Excel spreadsheet from a non-US locale (preferably generated on Windows)
• Build the application installers using fbs installer and test that the installation completed properly'
  • Test on macOS
  • Test on Windows
• Update the documentation for using the program
  • Create a sample Excel spreadsheet for users to use
  • Create Wiki pages for installing, using, and extending the functionality of the program
• Update flag icon set
  • Get a set of rectangular flags for the world
  • Update set of ISC flags

Currently, users cannot select the main color used in the scoreboards — it is hardcoded to be #2F292B. In previous versions of the program, this was a configurable option similar to the accent color and we should make this available for customization again.

Show the next country/participant to vote in the scoreboard.

• Add the option "Display Next Voter" to the GUI
• In the scoreboard, add a banner at the bottom (with the same size and color as the voter banner at the top of the scoreboard) with right-aligned text: "Next Voter: XXX"

Note: this issue was manually transferred from GitLab.

On Windows, it appears that the size of text rendered using QPainter is affected by the operating system's overall DPI Scaling factor (ex: 1.5 vs. 2.0).

For example, in the two images below, we can see that the scoreboard rendered when the UI Scaling factor is 2.0 has larger text than when the DPI Scaling factor is 1.5.

1.5 Scaling: This is the look of the scoreboards that we wish to achieve.

2.0 Scaling: Here, we can see that the text is drawn larger, making the scoreboard look less appealing.

A CI/CD solution, such as Travis CI, should be used to build and create executables for Windows and macOS.

Noticed this tonight making OSC scoreboards

Really tiny issue but some of them are jpg's instead of png's and it would be cool if they were consistent since I just auto generated the flag names