screenplay VS bfg-repo-cleaner

Download test mp4 https://gitlab.com/kelteseth/ScreenPlay/-/blob/master/Content/wallpaper_video_nebula/mantissa.xyz_loop_072.mp4

They also have a gitlab where you might be able to find a command utility, although looks like it’s written in c++. https://gitlab.com/kelteseth/ScreenPlay

ScreenPlay: A live wallpaper project; oddly enough it's made by the mod of this sub

Shameless self promo :D https://gitlab.com/kelteseth/ScreenPlay

- Godot is the most easiest way to deploy an app. Simply click export. In qt there is windeployqt for windows and macdeployqt that works fine. There are external projects like linuxdeployqt that has other problems like it forces you to compile on ancient Ubuntu versions for maximum compability. I had to write an python script that compiles my app on all (desktop) platforms https://gitlab.com/kelteseth/ScreenPlay/-/blob/master/Tools/build.py

Self containing Qt6 project, just clone the branch and open the CMakeLists.txt file of the ScreenPlayShader subfolder, so you do not have to install all external dependencies of ScreenPlay itself: https://gitlab.com/kelteseth/ScreenPlay/-/tree/testing/shader/ScreenPlayShader

My Qt/C++ cross-platform FOSS Wallpaper Engine project[1] currently uses 47gb of storage. This is because I compile for every platform and store the artifacts for 4 weeks. Not sure what I will do in the future, because having older builds around to try out without recompiling is always nice.

[1] https://gitlab.com/kelteseth/ScreenPlay

So this is a weird one. Code: https://gitlab.com/kelteseth/ScreenPlay/-/tree/master/ScreenPlayWeather is a simple http request that then parses the requests and fills a QQMLListProperty via a helper template class here https://gitlab.com/kelteseth/ScreenPlay/-/blob/master/ScreenPlayUtil/inc/public/ScreenPlayUtil/ListPropertyHelper.h. It does only work If I add anything before or after the assignment (rp.model = weather.days) in qml:

Here is how I fixed it: https://gitlab.com/kelteseth/ScreenPlay/-/commit/97d65c2ab61c8d47f588186b648e30de0e0ba0bf

So, this is a PSA that you can't simply delete the file and commit that. You must either use a tool like BFG Repo Cleaner which can scrub files out of your commit history or you could simply delete your repository and recreate it (easier, but you lose your commit history).

It shouldn't take a lot of time to modify. There is even a tool just for this scenario https://rtyley.github.io/bfg-repo-cleaner/

You need to git out the BFG: https://rtyley.github.io/bfg-repo-cleaner/

This method requires changes to be committed as usual in the regular project repository, and then committed again in the -docs repository. This is inelegant, but it provides clear distinction between private and public content. You cannot publish your regular repository without using git-filter-branch or some Git history rewriting software like BFG Repo-Cleaner. This would rewrite every commit in the history of the repo, removing all changes to the paths you don't wish to publish. This would change all the commit hashes and possibly other metadata – in short, it wouldn't be the same repository.

GFG Repo-Cleaner

You could use a repo filtering tool (e.g. BFG Repo-Cleaner) to clean up unintended information leak from your Git repository -- which retains the history timeline, but I believe it would rehash all the commits and render everything unsigned, which is probably not the desired outcome.