Open natevw opened 11 years ago
Started on this tonight.
https://github.com/Katharine/httpebble-watch/issues/4 is the notes on httpebble data sizes: current maximum 59 bytes, hypothetical 84 bytes per request.
Pasting https://raw.github.com/natevw/wristmap/e89045f660d6cb5d0c1e341c8caa4e8a01b554b4/server/ccitt.js into the JS console of various original toner images e.g. http://d.tile.stamen.com/toner/12/690/1452.png and http://d.tile.stamen.com/toner/0/0/0.png show compression reducing to 30% of original size, working out to 14–16 requests per screen (instead of 54 for current 3 rows/request).
(Next step is to decompress in the C code and actually use/test the compress code from the API.)
Right now it takes over 50 requests to get a single screen!