Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Canvas Gauges

canvas-gauges.com

Post reply on HN
Print view View original

1–10 of 62 posts

Re: Canvas Gauges

#2

Post by watty »

Looks nice, I may use them.

I noticed in the docs you said they are great for desktop, mobile, or (emphasized) "IoT devices with limited resources". These run on the client side which means they won't typically run on IoT devices unless I'm missing something. What does it have to do with IoT?

Re: Canvas Gauges

#3

Post by Pigo »

watty wrote: post #2

Looks nice, I may use them. I noticed in the docs you said they are great for desktop, mobile, or (emphasized) "IoT devices with limited resources". These run on the client side which means they won't typically run on IoT devices unless I'm missing something. What does it have to do with IoT?

They might mean for use in something that's built on Electron or another cross platform desktop library built with js.

Re: Canvas Gauges

#5

Post by askmike »

watty wrote: post #2

Looks nice, I may use them. I noticed in the docs you said they are great for desktop, mobile, or (emphasized) "IoT devices with limited resources". These run on the client side which means they won't typically run on IoT devices unless I'm missing something. What does it have to do with IoT?

I guess the author is talking about the small codebase, which means every IoT device that has some kind of webinterface has to store and serve less data (library is 10kb gzipped, while a high level chart library like d3 is 77kb). At least in the case where you don't serve libraries from a CDN..

Re: Canvas Gauges

#7

Post by detaro »

watty wrote: post #2

Looks nice, I may use them. I noticed in the docs you said they are great for desktop, mobile, or (emphasized) "IoT devices with limited resources". These run on the client side which means they won't typically run on IoT devices unless I'm missing something. What does it have to do with IoT?

Maybe that client-rendering doesn't put load on the IoT device serving the page (vs. e.g. rendering an image on it and serving that)

Re: Canvas Gauges

#8

Post by ctoth »

These do not appear to be accessible at all. If you use this on your site, I will not be able to read whatever you're trying to tell me, other than by making me look at source. Please don't do that. I know accessibility is hard, and the developers of this were just trying to make something that looks nice and gets the job done. Every time an inaccessible reusable {component, library, toolkit\, framework} is released, the inaccessibility spreads like a cancer to every single downstream project. What this translates to is a web, that for me, is slowly going dark. This sucks, but I don't see any way to fix it other than trying to be some sort of front-line accessibility cop when I see new stuff on HN. But I'm not an expert in all forms of accessibility, and I am already stretched thin trying to build my own accessible apps.

I don't have a good answer here, just a plea to consider accessibility when designing stuff that's meant to be some variety of reusable widget.

Re: Canvas Gauges

#9

Post by Mikhus »

ctoth wrote: post #8

These do not appear to be accessible at all. If you use this on your site, I will not be able to read whatever you're trying to tell me, other than by making me look at source. Please don't do that. I know accessibility is hard, and the developers of this were just trying to make something that looks nice and gets the job done. Every time an inaccessible reusable {component, library, toolkit\, framework} is released,…

Thank you, it is simply one of the most useful comments I (as developer) have for the moment. I will look forward to get a clue how to provide accessibility features in the next releases. Shame on me but this was exactly that feature I completely missed off.

Re: Canvas Gauges

#10

Post by Mikhus »

askmike wrote: post #5
watty wrote: post #2

Looks nice, I may use them. I noticed in the docs you said they are great for desktop, mobile, or (emphasized) "IoT devices with limited resources". These run on the client side which means they won't typically run on IoT devices unless I'm missing something. What does it have to do with IoT?

I guess the author is talking about the small codebase, which means every IoT device that has some kind of webinterface has to store and serve less data (library is 10kb gzipped, while a high level chart library like d3 is 77kb). At least in the case where you don't serve libraries from a CDN..

Exactly, that was I meant :)
Post reply on HN