screenplay VS gitlab

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

Since the relevant code appears to be in the "ee" directory <https://gitlab.com/gitlab-org/gitlab/-/blob/v16.11.0-ee/ee/l...> and is not present in the foss repo, I'm guessing the answer is no, at least for now. They do have a history of "releasing" features from EE back to CE but my suspicion is not for LLM stuff

(Side note: Issues are usually hash-prefixed like #1234 both on GitLab and GitHub. However, commit messages must not begin with a hash, they would be considered a comment and ignored. Therefore, GitHub has introduced the alternative prefix GH- and I've contributed a similar prefix GL- to GitLab a while ago.)

and its "oh, you want multi-arch, do you?" friend. While prosecuting this <https://gitlab.com/gitlab-org/gitlab/-/issues/339567> I learned that https://hub.docker.com/layers/multiarch/qemu-user-static/7.2... actually mutates the binfmt_misc in buildx's context in order to exec the static copy of qemu in it https://github.com/multiarch/qemu-user-static/blob/v7.2.0-1/...

and, that the buildx plugin itself has some qemu magick in it, which got addressed in a minor version bump but I couldn't track down the relevant GitHub issue this second (I've flushed it from my mind, only recalling that there were a lot of actors in that tire fire)

This is actually a follow-up refactor, the fix is here: https://gitlab.com/gitlab-org/gitlab/-/commit/abe79e4ec43798...