Make multiple export templates tpz files#107
Make multiple export templates tpz files#107pafuent wants to merge 1 commit intogodotengine:mainfrom
Conversation
|
I'm not sure if we should have more granularity than just "one TPZ per platform". Having separate TPZ for debug/release and for each architecture will make the editor UI to manage which templates to download more complex. If you only download debug/release or only some architectures, you'll also see error messages in the Export dialog until you change some settings. Additionally, having a lot of files to download makes the UX for manual downloaders more tedious. PS: For those interested in downloading all platforms at once, there is a benefit to having multiple downloads being performed in parallel, especially on fast FTTH connections. However, since we support 6 platforms (and therefore at least 6 TPZ files), we already have plenty of concurrency possible this way. Not to mention web browsers generally can't download more than 6 files at the same time anyway (it's a hardcoded limitation). |
|
I thought that the granularity will be useful for CI environments. |
Partially implements godotengine/godot-proposals#647 Besides the original all-in-one export templates tpz file, `build-release.sh` generates several export templates tpz files to allow smaller downloads.
pafuent
force-pushed
the
make_multiple_export_templates_tpz_files
branch
from
6acb484 to
9be1988
Compare
2 participants
Partially implements godotengine/godot-proposals#647
Besides the original all-in-one export templates tpz file,
build-release.shgenerates several export templates tpz files to allow smaller downloads.I arbitrarily decided on which new export templates tpz files create and it's contents. Please fell free to suggest more or less files.
Here is the contents of each new file (used files from Godot 4.4 to test my changes):
Classical
Mono