Indeed I understand that SANE isn't a Gimp plugin. If
you saw my other post with an (somewhat rough)
alternative model that puts SANE as a mediator between
data sources and data sinks you would see that I make
allowance for other data destinations. Surely you have
an interface that writes a Gimp format file? I don't
actually know whether you write a physical file for Gimp
or pass the data as memory structures but it isn't
particularly relavent for this exersize. Once you have
one Gimp interface there is no reason why you (or
someone else with a vested interest) cant write a second.
Gimp has this nice layers model which can be used for
generic image data. Whereas the Alpha layer has a
specific meaning which is distinct from dust removal
operations.
Cheers,
Steve Gunnell
Oliver Rauch wrote:
> Hi Steve,
>
> I have no problem to shift the 4th channel data as an auxillary channel to the
> gimp.
> But SANE is not ONLY a gimp plugin and I am programming a frontend
> that normally saves the images to a file and I want to know how to
> save new formats.
>
> Nick seems to be a really big Gimp fan and gimp is a nice tool, but
> SANE/xscanimage/xsane are not only scanning-tools for the Gimp.
>
> I also have no problem to remove the RGBA routine if nobody likes it.
> It is a way to save the data in a known format.
>
> Other possiblities are to define a raw format that is passed through the
> frontend without any changes or the frontend say "unsupported".
>
> Bye
> Oliver
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com