From 16d4306763cd48d57abb2e247040a082600973f1 Mon Sep 17 00:00:00 2001 From: Shautvast Date: Wed, 10 Apr 2024 17:41:51 +0200 Subject: [PATCH] readme and page updated --- README.md | 16 +++++++++++++--- index.html | 6 ++++-- src/img/browserwarning.png | Bin 0 -> 10124 bytes src/js/index.js | 3 +++ 4 files changed, 20 insertions(+), 5 deletions(-) create mode 100644 src/img/browserwarning.png diff --git a/README.md b/README.md index 83dd99e..3f59e42 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,17 @@ -**Spiegel** image filter project (Work In Progress) +**Spiegel** image filter project -- rust -- wasm +- rust/webassembly for image processing +- vanilla javascript for the user interface +- no server (just static pages) + +Live demo at https://shautvast.github.io/spiegel-demo/ + +* Sorry for the poor performance, especially on larger images. +* It uses the median image filter from image.rs. That in itself can be pretty slow. +(Although the implementation uses a _sliding window histogram_, which I think is pretty nifty). +* And on top of that, I created this custom flood fill algorithm, +that instead of filling it with with a single color, looks up a sample from the +Spiegel book (that has a corresponding color) and takes the pixels from that. sample output ![sample](https://github.com/shautvast/spiegel-web/blob/main/unsplash.png) diff --git a/index.html b/index.html index 2035ab8..d1ba718 100644 --- a/index.html +++ b/index.html @@ -19,7 +19,7 @@
@@ -37,7 +37,9 @@

(Painting can take long, be patient

-

all image processing is done in your browser)

+

all image processing is done in your browser).

+
And ignore all the warnings! It will be all right.
+