W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2012

Re: [whatwg] <picture> / <img srcset> not needed

From: Kevin Marks <kevinmarks@gmail.com>
Date: Thu, 17 May 2012 09:59:11 -0700
Message-ID: <CAD6ztsqNkYNSTxtGpzXrqhJEpGDfe3jEwYqc0KC8dEgEPyOu6w@mail.gmail.com>
To: Glenn Maynard <glenn@zewt.org>
Cc: whatwg@whatwg.org, "Tab Atkins Jr." <jackalmage@gmail.com>, Aldrik Dunbar <aldrik@gmail.com>
Jpeg 2000 has wavelet coding and progressive loading so you can stop at the
desired resolution (if you decode on the read thread). Presumably it will
be patent free by 2020...
On May 16, 2012 3:57 PM, "Glenn Maynard" <glenn@zewt.org> wrote:

> On Wed, May 16, 2012 at 5:44 PM, Aldrik Dunbar <aldrik@gmail.com> wrote:
>
> > Of course if someone comes up with a progressively loaded image format
> > this could be handled much more elegantly.
> >
>
> Both PNG and JPEG have had this forever.  (PNG's approach is crude, but
> JPEG's is reasonable.)  However, there's no way to control it client-side;
> without somehow knowing how many bytes to load for a certain amount of
> detail, all you can do is load the whole thing (or make multiple requests,
> which is obviously worse).   I've thought about this in the past, but it's
> a hard thing to make practical use of.
>
> --
> Glenn Maynard
>
Received on Thursday, 17 May 2012 16:59:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:08 GMT