Bumping thread. API changed again:) Current version supports all i need to
and can be extended without breaking BC (which is important when API will
be stabilized).
UML diagram:
https://raw.githubusercontent.com/ABBAPOH/imagedocument/master/uml/Class%20Diagram.png
Typical usage: http://pastebin.co
Another experiment. I've added separate classes for CubeTexture and
VolumeTexture
https://github.com/ABBAPOH/imagedocument/blob/textures/src/lib/cubetexture.h
https://github.com/ABBAPOH/imagedocument/blob/textures/src/lib/volumetexture.h
The idea for Cube texture is an ablitity to create from/conv
For now, i moved mipmaps into ImageResource
+ the Document is just an array of resources now (with 1 element for jpeg,
png, ico, icns; multiple for gif)
+ in the simplest case (jpeg, png) Document has 1 Resource with 1 image in
it.
+ in the case of icns/ico Resource is a 1d array of mipmaps
- in th
2015-05-21 10:16 GMT+04:00 Rutledge Shawn :
>
> So I’d add both frame and frameCount to Image, which would be enough in
> this example, and then you don’t need the ImageDocument for such a simple
> use case.
>
Doesn't this mean Image becomes a light-weight variant of ImageDocument?
How will image
On 19 May 2015, at 21:00, Konstantin Ritt wrote:
> IIUC, this already covered by the idea: since we can not (currently?) support
> animated "pages", we treat both a multi-page tiff and an animated gif as a
> document with N "frames”.
I thought so.
>
> What you described sounds more like mip
Иван Комиссаров schreef op 19-5-2015 om 19:43:
Let me describe current API and the ideas behind it.
The core class is the ImageDocument - this is the replacement of the
QImageReader/QImageWriter. Reader and writer has similar API and
implemented in the same way, so i’ve decided to merge them i
2015-05-19 22:12 GMT+04:00 Rutledge Shawn :
> I think the new API should have multi-page support. It would be useful
> for pdf, djvu, multi-page tiff, and for looking at individual frames of
> animated gif, png, etc., to the extent that we write plugins for those.
>
IIUC, this already covered by
Thanks for reply.
Yes, frames should actually be renamed to something more generic (array
element? page? resourceCount? - i couldn’t find the right name yet). Actually,
DDS doesn’t support animation, but it supports texture arrays which should be
implemented using "frames".
I didn’t think abou
I think the new API should have multi-page support. It would be useful for
pdf, djvu, multi-page tiff, and for looking at individual frames of animated
gif, png, etc., to the extent that we write plugins for those.
I wrote a QQuickImageProvider for PDF (using poppler), but requestImage takes
o
Hello everybody!
Recently i’ve started a project of a new imageformats API. The reasoning is
that there are a lot of limitations in the current API: no way to save file
containing an array of images, bad error handling, no support for the EXIF.
Implementing those features requires ABI breakage
10 matches
Mail list logo
