Platform: Web #591

New issue

Open

opened 2025-12-17 03:14:39 +00:00 by SakulFlee · 0 comments

SakulFlee commented

2025-12-17 03:14:39 +00:00

(Migrated from github.com)

Web and #573 & #590 share a lot of similar problems, but in different ways.
We might be able to take solutions from one target over to the other.

1. Proper build tools

There are a lot of different build tools for compiling Rust to WASM.
Unfortunately, all of them require some amount of setup first.

Similar to what we need to do in #573, we should create some kind of universal script (e.g. Makefile, Just, etc.) to generate or ready these project files. We should also think about how we even distribute this ... just a simple website with nothing but the engine? Maybe some kind of legend and info aside it? etc.

2. CI / CD

Similar to 1., we don't have any proper CI / CD setup for Web.
We'd need a way of easily replicating given configurations of Android versions X source code revisions.
Ideally, we'd build some form of distributable website package.

(Optional, not sure if needed ... probably useless for now until we have bigger examples: Push to something like GitHub-Pages!)

3. Asset management

Assets are done much differently on web platforms!
Commonly, the website (e.g. HTML & CSS files) as well as the WebAssembly (WASM) files don't include the assets. These have to be fetched from the server via a REST (or similar) request to basically download these and potentially cache them locally in the browser cache.

This also applies for writing files like save games!
There needs to be a solution for saving files locally.

Web and #573 & #590 share a lot of similar problems, but in different ways. We might be able to take solutions from one target over to the other. ### 1. Proper build tools There are a lot of different build tools for compiling Rust to WASM. Unfortunately, all of them require some amount of setup first. Similar to what we need to do in #573, we should create some kind of universal script (e.g. Makefile, Just, etc.) to generate or ready these project files. We should also think about how we even distribute this ... just a simple website with nothing but the engine? Maybe some kind of legend and info aside it? etc. ### 2. CI / CD Similar to 1., we don't have any proper CI / CD setup for Web. We'd need a way of easily replicating given configurations of Android versions X source code revisions. Ideally, we'd build some form of distributable website package. (Optional, not sure if needed ... probably useless _for now_ until we have bigger examples: Push to something like GitHub-Pages!) ### 3. Asset management Assets are done much differently on web platforms! Commonly, the website (e.g. HTML & CSS files) as well as the WebAssembly (WASM) files don't include the assets. These have to be fetched from the server via a REST (or similar) request to basically download these and potentially cache them locally in the browser cache. This also applies for writing files like save games! There needs to be a solution for saving files locally.

SakulFlee added the

Type: Tracker

Platform: Web

labels

2026-01-07 01:32:46 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

SakulFlee/Orbital#591

No description provided.

Rows
Columns