lestahl / cortex Goto Github PK

There is some uncertainty, which fonts are installed on the compo hardware and whether or not the fonts installed on the dev machines are the same. To avoid this problem, we need code that

• knows, which fonts the demo would like to have (with fallback options)
• crawls C:\Windows\Fonts on the compo machine to check whether they are present

There are several languages that need linting in the project: CMake, JSON, C/C++, GLSL, Python

• identify a linting strategy that is available in CMake,
• agree on linting rules for all the languages above
• implement linting step into CMakeLists.txt
• update existing source to match linting rules

I would like to show the NFO file inside the selector, or add a "Display NFO" button. Preferably the NFO should be displayed using a simple shader.
I'd rather not compile the NFO file into the executable; If it gets deleted (as compo rules always claim), there should be code that prevents the executable from crashing.
The option should be switchable at compile time.
Information about the character encoding can be found here.

At the moment, releasing includes some effort:

• create screenshot
• create downscaled version of screenshot for pouet (information on requirements available in here
• build compressed release executable
• pack screenshot, nfo file and compressed release executable into single zip file named demo.name-group.name.zip
  Add a CMake target to CMakeLists.txt that does all this automatically.

There are multiple packers available; upx, squishy, kkrunchy and crinkler.

• Include command line switches for creating an executable for each of the options above inside CMakeLists.txt
• Update CMakeLists.txt to create the executable with the selected tool: upx (windows and linux), squishy (windows), kkrunchy (windows) and crinkler (windows)

There are multiple options for compiling the executable under windows: Visual C++ Toolkit and CLang and linux: CLang and g++.

• automatically select the correct command line options for the platform and compiler combinations
• update the code for selecting crinkler as linker so the correct compile command and linker executable is used when the crinkler option is on

There are two groups of optimiziations that I can think of:

• lexer-based
• parser-based

Goal of this issue is to brainstorm ideas, which optimizations can be made to GLSL source. The idea is to separate result-preserving optimizations and approximating optimizations.