Demo page is down

[john-sardinha-pbx]

Please ensure you have given all the following requested information in your report.

Issue details

https://libgdx.badlogicgames.com/demos/ is down (503)

Reproduction steps/code

Go to https://libgdx.badlogicgames.com/demos/

> $ ping https://libgdx.badlogicgames.com/demos
ping: cannot resolve https://libgdx.badlogicgames.com/demos: Unknown host
> $ ping https://libgdx.badlogicgames.com                                                                                                                                            X
PING https://libgdx.badlogicgames.com (95.216.8.184): 56 data bytes
64 bytes from 95.216.8.184: icmp_seq=0 ttl=53 time=46.012 ms
64 bytes from 95.216.8.184: icmp_seq=1 ttl=53 time=45.540 ms

Version of libGDX and/or relevant dependencies

Please provide the version(s) affected.

Stacktrace

//Please provide the stacktrace if applicable 

Please select the affected platforms

• [ ] Android
• [ ] iOS
• [ ] HTML/GWT
• [ ] Windows
• [ ] Linux
• [ ] macOS

[tommyettinger]

I'm not sure where the demos are hosted now, if anywhere, but https://libgdx.com/wiki/start/demos-and-tutorials needs to be updated when hosting is figured out. @crykn , do you know if the old demos are still up anywhere (as built GWT apps)? Or what it would take to host them on libgdx.com , if we can build them again?

[Frosty-J]

Don't think they're hosted anywhere, except for the one I built. Duplicate of libgdx/libgdx.github.io#221.

[crykn]

@Frosty-J is right, at the moment they don't seem to be hosted anywhere. If badlogicgames.com doesn't come online again, we should definitely think about transferring them to libgdx.com. The easiest way of achieving this would probably be to build them automatically via GitHub Actions and then deploy the GWT builds to GitHub Pages (similarily to what we do in the https://github.com/libgdx/libgdx-wiki-examples repo). The desktop and Android downloads could be provided via the releases tab of the corresponding repos.

Regardless of that, going forward we should probably think about what we want to do with the demo projects. We might want to archive a few of those/maybe even replace them, considering they are all quite old, have a bunch of open issues/PRs and it's a hassle keeping them up to date.

[SonicGDX]

I will look into attempting to create PRs to update some of these so that they build at least. It looks like @obigu updated lots of them in 2021 but perhaps they are broken again?

However I'm not sure if I should update lwjgl to version 3 or leave it as is (or perhaps keep both?) for some of the older projects. Lwjgl3 is the main now, but 2 is still supported, right? Edit: I'll just make changing to lwjgl3 a separate PR

[tommyettinger]

I'd think they should target GWT if at all possible; the downloadable targets are much less likely for newcomers to try. If you include a desktop build, LWJGL3 is preferable because M1 and later macs don't work (normally) with LWJGL2.

[Frosty-J]

Some changes may be desirable for GWT. For example, that backend doesn't support setting a frame rate cap, so demos that don't use delta times will run at the wrong speed for users who have non-60Hz displays.

[SonicGDX]

Manually changing one of the gradle projects now (although it may honestly just be easier to create a new project with the game name and drop the code files in), but I was curious about how it pulls the latest version numbers from the website as opposed to them being pinned like in newly generated projects. https://github.com/libgdx/libgdx-demo-superjumper/blob/master/build.gradle It means the project is updated to the latest libgdx version automatically, but could this lead to breakage if e.g. the android api version changes?

[tommyettinger]

I'd think if the projects are currently fetching the latest libGDX, they're broken as-is. They should IMO be pinned, and updated when the project is brought up-to-date for a new release.

[crykn]

Closing this in favour of #221.