W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Re: Reading image bytes to a PNG in a typed array

From: Florian Bösch <pyalot@gmail.com>
Date: Mon, 14 Jan 2013 14:03:26 +0100
Message-ID: <CAOK8ODj9sf2rD1wNxnzemMhD=pnzFNGvCDsgN+MWmJjmXW_TRw@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: Webapps WG <public-webapps@w3.org>
The usecase is that I write a productivity application using WebGL which
has a need to bundle images residing in computed textures into one archive
(tar, zip etc.).

- The images belong together (such as normal, height, tangent, specular
color, specular power, albedo etc.)
- The archive has to land in a typed array so it can efficiently be put
into a blob url, put into an XHR for upload to cloud storage, etc.
- Which means the images encoded have to land in a typed array
- Which means the described process is currently the "best" on offer by
browsers.
- Which should be rectified.


On Mon, Jan 14, 2013 at 1:46 PM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Mon, Jan 14, 2013 at 1:20 PM, Florian Bösch <pyalot@gmail.com> wrote:
> > Having a texture in WebGL and wanting to encode it into a typed array as
> > PNG, I have found that the only way to do it is the following convoluted
> > method.
>
> Could you list the use cases?
>
> http://wiki.whatwg.org/wiki/FAQ#Is_there_a_process_for_adding_new_features_to_a_specification.3F
> is relevant in particular.
>
>
> --
> http://annevankesteren.nl/
>
Received on Monday, 14 January 2013 13:03:54 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:57 GMT