Skip to content

Conversation

@tychedelia
Copy link
Member

Partially addresses #26.

Adds a new processing_wasm crate that operates similar toprocessing_ffi, i.e. wrap in a WASM/JS compat function.

We're helped by running in a single thread on desktop already, but on web we can't ever block the main thread, so we need a few additional non-blocking flavors of some methods that currently block on desktop.

We're generating JS bindings here because it's helpful to test. Most implementers will likely just bind directly to the WASM module.

Adds a justfile to help coordinate some of this. If you're not familiar, just is a common task running in the Rust ecosystem that's like a simplified make.

@tychedelia tychedelia requested a review from catilac December 6, 2025 00:19
if let Some(mesh) = ctx.batch.current_mesh.take() {
// we defensively apply a small z-offset based on draw_index to preserve painter's algorithm
let z_offset = ctx.batch.draw_index as f32 * 0.001;
let z_offset = -(ctx.batch.draw_index as f32 * 0.001);
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Somehow evidently I screwed this up again relative to ProcessingProjection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant