RE: [Inkscape-devel] Re: importing bitmaps as patterns
FWIW, I also fall into the "clean SVG" camp. Not just for "cleanness", but also because SVG renderers won't necessarily perform as well (visual glitches and slowness) with pattern fills as with bare images.
Just tried Batik 1.4. It indeed has bad glitshes on redraw/scrolling, but these glitches are _the same_ on a filled rect vs. an <image>. So I don't know why one should be better than another. In fact, from my programmer's experience, both <image> and pattern fills must support the same set of operations (affine transforms, opacity) and therefore are likely to be rendered by mostly the same code.
As for "slowness", this is premature optimization IMHO. We should strive to save the work time of the user first, and rendering time second. Those who need highly optimized rendering will probably be knowledgeable enough to use <image>s if that indeed gives any advantage.
- there should be a command to "wrap" the selected objects into a patterned rect (determined by their collective bounding box)
Yes, I thought about it too, and it's very easy to implement (once we clear the pattern bugs, that is). It will be usable not only for converting an <image> to a filled rect but for creating non-bitmap patterns too. I think "Make a tile" is a good name for such a command.
- there should be a corrseponding command to "unwrap" the objects in an SPShape's fill pattern as they appear in the SPShape; I think it's better to make copies of each rather than destroy the pattern. I'm not sure whether this operation ought to remove the SPShape or alter its fill.
Yes, this would be nice to have too, although more difficult to implement (most of the difficulty is in finding out how many copies of the pattern you need; once you know that you need to do either boolean intersection or masking of each object in the pattern copies with the former container shape).
_________________________________________________________________ Add photos to your messages with MSN Premium. Get 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI...
On Wed, 2004-05-26 at 20:30, bulia byak wrote:
In fact, from my programmer's experience, both <image> and pattern fills must support the same set of operations (affine transforms, opacity) and therefore are likely to be rendered by mostly the same code.
Patterns are tiled. It's hard (when the enclosing rect is transformed) to not have fringing due to opposite sides of the tile peeking through due to roundoff errors.
It's a fairly common bug in renderers that do tiled patterns/bitmaps.
- there should be a command to "wrap" the selected objects into a patterned rect (determined by their collective bounding box)
Yes, I thought about it too, and it's very easy to implement (once we clear the pattern bugs, that is). It will be usable not only for converting an <image> to a filled rect but for creating non-bitmap patterns too. I think "Make a tile" is a good name for such a command.
Sounds about right.
- there should be a corrseponding command to "unwrap" the objects in an SPShape's fill pattern as they appear in the SPShape; I think it's better to make copies of each rather than destroy the pattern. I'm not sure whether this operation ought to remove the SPShape or alter its fill.
Yes, this would be nice to have too, although more difficult to implement (most of the difficulty is in finding out how many copies of the pattern you need; once you know that you need to do either boolean intersection or masking of each object in the pattern copies with the former container shape).
Perhaps; an initial implementation that just copied one tile's worth and didn't bother with clipping would still be useful, however.
(I would hope it would be able to detect the image-in-rect situation and short circuit in that fashion anyway)
-mental
win32 autobuild 29 May.
While playing around with importing bitmaps as patterns I found that I could get Inkscape to crash consistantly as follows.
1. Open Inkscape. 2. Import bmp or jpeg file. 3. extend image with any control handle to edge of screen. 4. Inkscape crashes.
the crash occurs whether transforms are optimised or preserved.
vellum
participants (3)
-
bulia byak -
MenTaLguY -
vellum