Re: new image-type: composite, or not

[Andreas Politz]

Stefan Monnier <address@hidden> writes:

> What does it look like?  E.g. can you highlight the text without
> obscuring it?

http://public.fh-trier.de/~politza/emacs/pdf-isearch.png

Because of anti-aliasing, the background is not merely a single color,
such that my (single-color) mask is not perfect.  `convert' seems to do
some fuzzy comparing of colors by default.

>
>> Alas, all this made me realize, that maybe a simpler approach would
>> suffice.  Something like a single function
>> (mark-image foreground background &rest edges-list)
>
> I'm not sure exactly how that would work, can you give some details?
>
This kind of function was what I was looking for.  I have a list of
rectangles ((x0 y0 x1 y1)...) and want to ,,fontify'' the image at these
places.  

I don't know.  I just thought, that maybe this kind of low-level
tinkering with images, masks and slices is not really needed and maybe
it does not really fit nicely in the current image-framework.  If that
is true, then some more high-level function could simplify an
implementation or make it cleaner.  Using libmagick instead of X11 is
something else to consider.

>> which does not have the side-effect of reloading the image.
>
> Why does the composite type need to reload the image?
>

No it doesn't. I just stated an imported feature, this supposed
mark-image function would need to have.

> Not sure what other candidates there can be, neither for mark-image nor
> for a composite image.
>

Well, customizing tree-widgets images...

-AP