Mozilla2:Image Encoding: Difference between revisions
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
Something like: | Something like: | ||
interface imgIEncoder : | interface imgIEncoder : nsIInputStream | ||
{ | { | ||
/* input image data | /* input image data | ||
| Line 10: | Line 10: | ||
* result height | * result height | ||
*/ | */ | ||
void init(in imgIContainer input, | |||
in unsigned long width, in unsigned long height); | |||
}; | }; | ||
=== Scaling === | === Scaling === | ||
| Line 22: | Line 20: | ||
A reader should get the bytes requested, if not greater than length of encoded image, and it's up to the encoder to buffer more if it encodes more bytes, reading from the buffer on next read. | A reader should get the bytes requested, if not greater than length of encoded image, and it's up to the encoder to buffer more if it encodes more bytes, reading from the buffer on next read. | ||
This expresses the idea that the encoder is something you read from. | This expresses the idea that the encoder is something you read from. | ||
Latest revision as of 06:17, 8 March 2005
Interface
We need to add a new interface. When you read from the stream should we encode just that much? Thoughts?
Something like:
interface imgIEncoder : nsIInputStream
{
/* input image data
* result width
* result height
*/
void init(in imgIContainer input,
in unsigned long width, in unsigned long height);
};
Scaling
Do we want to support different types of scaling? I'd prefer to just do nice Bicubic resampling. [1] [2]
Brendan's comments
A reader should get the bytes requested, if not greater than length of encoded image, and it's up to the encoder to buffer more if it encodes more bytes, reading from the buffer on next read.
This expresses the idea that the encoder is something you read from.
Use
You would create one by doing:
createInstance("@mozilla.org/image/encoder;2?type=image/png");