Currently on save the user will be directed to a URL with a pregenerated image created by a local utility and uploaded to github. This might cause issues with github repo storage limits, could upload to a paid storage solution but...
Luckily the package rfd now supports save_file for wasm: PolyMeilex/rfd#134
This could be used to generate the image on save and allow the user to save it locally.
Looked into it briefly, not sure how this can be used with image::save_buffer because it seems the dialog only triggers with a call to write and doesn't return a path which image::save_buffer expects as one of its arguments.
Currently on save the user will be directed to a URL with a pregenerated image created by a local utility and uploaded to github. This might cause issues with github repo storage limits, could upload to a paid storage solution but...
Luckily the package rfd now supports
save_filefor wasm: PolyMeilex/rfd#134This could be used to generate the image on save and allow the user to save it locally.
Looked into it briefly, not sure how this can be used with
image::save_bufferbecause it seems the dialog only triggers with a call towriteand doesn't return a path whichimage::save_bufferexpects as one of its arguments.