User-474980206 posted
I knew this. I'm curious if Blazor WASM can do the job with .net libraries instead of javascript.
I know there are many libraries in javascript for this task. Also, there are many graphic editor UI components.
it depends. a graphic / image editing program has two components, a UI and graphics engine. in browser based application you need a local graphics library, because passing images from client to server is too slow.
one approach is two graphic libraries, on the client one where you edit a low res image, and a server one, that edits the high res version. the client sent all graphic command to the server an it keeps its version in sync. with clients support more memory,
this is not so common.
in browser graphic application, a canvas is used to display the image. the UI elements like object selection, lasso's, etc are drawn on the canvas. Typically the tools are outside the canvas, but can be drawn in the canvas. Th UI converts mouse, and
keyboard commands in graphic commands, which update the canvas.
it is perfectly possible to write a WASM graphics application, the issue with writing one in Blazor is performance. Currently C# WASM performance is generally much slower than native javascript. For a WASM graphics application you should use C/C++,
Rust or Swift to write the graphics engine. Currently there is no thread or GC support in WASM. this means you should use a heap language for performance.
As a WASM graphic application can not access the dom or the canvas, the UI is typically written in javascript. Blazor has a generic javascript interface that allows send events to the WASM and rending html back, so the UI could be written in Blazor with
minimum javascript required.
As your questions are rather naive, I suspect you should just pick a working graphics library (with UI).
