RAW export (command line)
Bug #172207 reported by
Amphi-users
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Inkscape |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
RAW export via command line with configurable byte order (eg ARGB, BGRA
etc) would be pretty handy for extension writing. The benefits are speed
(no silly intermediate png en/decoding) and an image/png lib for Python (or
just ImageMagick) won't be required.
AFAICT interlacing options (none, line, plane and partition) aren't
needed.
Possible uses are ICO (multi page) and ICNS for example.
Revision history for this message
| Amphi-users (amphi-users) wrote | #1 |
| Changed in inkscape: | |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
| tags: | added: cli |
To post a comment you must log in.
Originator: YES
Another interesting field of application is benchmarking. (A "null" export
might be interesting as well.)
Currently the export speed varies greatly with the proportions of the
image.
32x32768 took 16.5930 s
32768x32 took 1.2970 s
4096x256 took 3.8440 s
256x4096 took 8.5790 s
2048x512 took 3.6090 s
512x2048 took 4.0940 s
(In all cases the number of pixels is equal to 1024x1024.)
It would be interesting to know if the png export or blur code is
responsible for this behavior.