Allow downloading individual export template TPZ files for each platform

[ViktorEvil]

Describe the project you are working on:
HeartBeast 1-bit course

Describe the problem or limitation you are having in your project:
Have to download export templates that I do not need / want

Describe the feature / enhancement and how it helps to overcome the problem or limitation:
could we have the option to select individual export templates instead of the entire package. As Godot gets more advanced this Export template package is getting larger. Individual templates would reduce bandwidth on the server.

Describe how your proposal will work, with code, pseudocode, mockups, and/or diagrams:
Display a list of all export templates available then put a tick by the needed templates

If this enhancement will not be used often, can it be worked around with a few lines of script?:
I envision it would be used a lot

Is there a reason why this should be core and not an add-on in the asset library?:
I do not think that anybody using Godot requires all export templates available

[Calinou]

Related to #35.

I'm willing to make the required UI changes, but this requires the export template packaging to be modified so each TPZ file contains only one platform. However, I have no control over it.

Old Godot versions will have to keep the old packaging scheme, but Godot 4.0 onwards should use the new per-platform packaging scheme.

---

If you stumbled upon this proposal and are experiencing slow downloads on TuxFamily, use this mirror.

[Calinou]

@me2beats Please don't bump issues without contributing significant new information. Use the 👍 reaction button on the first post instead.

[0x53A]

I'd like to add that while on a developer PC, you only download the templates a single time; when using a CI like github actions, they are downloaded every single time.

For myself I've reuploaded a version of the templates with only the ones I actually need, which for now includes windows and web (both release only), which comes down to 114 MB uncompressed, or 64 MB zipped, compared to the original templates which are 1.6 GB uncompressed or 1020 MB tpz compressed.

[AmanRajAryan]

What's the status, no progress at all?

[Calinou]

What's the status, no progress at all?

godotengine/godot-build-scripts#107 modifies the infrastructure part, but we still need the editor side to be modified.

I have a prototype for the editor UI in a branch, which I've just rebased:

However, what the UI will look like exactly depends on how many .tpz files we plan to split the export templates into. We can do either per-platform splits like this proposal originally mentions, or use a more granular approach and also split each architecture into its own .tpz file.

The difficult part of the UI is handling export templates that are already installed, but only for a subset of all available platforms/architectures. The UI prototype currently doesn't handle this, so you can't add more platforms to a platform that is already partially already installed. I guess the checkboxes should reflect the state of the currently selected platform, so you can tick unchecked checkboxes to install more platforms, or untick checked checkboxes to remove them. The operation would be done in one go once you click the Download and Install button (which could be renamed Update Selected Version in this situation).

[arkology]

I have a prototype for the editor UI

Talking about UI side, listing platforms as Tree (with something like "Select All" as root) is more standard way to represent such things.