11–20 of 21 posts
I would think just rendering something charcoal on the computer of the designer should be enough, rather than repeating it on the machines of thousands of visitors?
Slightly related question: Does the carbon footprint increase with all this client side rendering? I would think just rendering something charcoal on the computer of the designer should be enough, rather than repeating it on the machines of thousands of visitors?
In any event I don't like it because it kills my battery.
Earlier quoted context omitted.
But how would you then download the edited image? Either browsers support taking screenshots via an API (no browser extension) or you would need to render it on the server side again. Maybe I am missing something?
If it was done inside a canvas it would be possible to save it. The effects would not be as simple to create though.
I'm pretty sure the applied css effects should carry over to the canvas.
Recently, I've been looking more into WebGL and what's possible with GLSL shader scripts for image warping (for VR) and image processing/effects. see shadertoy.com etc.
Slightly related question: Does the carbon footprint increase with all this client side rendering? I would think just rendering something charcoal on the computer of the designer should be enough, rather than repeating it on the machines of thousands of visitors?
However, if you want to use a pencil effect on an image that you don't have control over (eg a user's image before they upload it, or something from an API-driven service like Unsplash) then the technique still has a lot of value.
Earlier quoted context omitted.
But how would you then download the edited image? Either browsers support taking screenshots via an API (no browser extension) or you would need to render it on the server side again. Maybe I am missing something?
If it was done inside a canvas it would be possible to save it. The effects would not be as simple to create though.
Earlier quoted context omitted.
Client side image editor is the first thing I thought of.
But how would you then download the edited image? Either browsers support taking screenshots via an API (no browser extension) or you would need to render it on the server side again. Maybe I am missing something?
Earlier quoted context omitted.
Client side image editor is the first thing I thought of.
But how would you then download the edited image? Either browsers support taking screenshots via an API (no browser extension) or you would need to render it on the server side again. Maybe I am missing something?
[1] https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API/...
Slightly related question: Does the carbon footprint increase with all this client side rendering? I would think just rendering something charcoal on the computer of the designer should be enough, rather than repeating it on the machines of thousands of visitors?