[haiku-commits] Re: haiku: hrev46554 - src/add-ons/translators/psd
- From: Marcus Jacob <rossi@xxxxxxxxxxxxxxx>
- To: "haiku-commits@xxxxxxxxxxxxx" <haiku-commits@xxxxxxxxxxxxx>
- Date: Mon, 23 Dec 2013 11:16:54 +0100
> On 18.12.2013, at 10:16, Stephan Aßmus <superstippi@xxxxxx> wrote:
>
> Hi,
>
> just to let you know your work on the PSD Translator is greatly appreciated!
> Its also pretty cool that it supports so many colorspaces and compression.
>
> It would be cool if the Translator supported an extended API via BMessages. I
> haven't really looked at how this works, but I know the JPEG Translator
> supports retrieving embedded thumbnails via such messages. What I am aiming
> at is retrieving individual layers in WonderBrush for example. But I know it
> can make the translator much more complex. It's been a long time since I
> looked at the PSD format, but if memory serves, there is a "final composed
> image" in the file, and one can ignore pretty much everything else if one
> wants to just display the image. If support for layers is needed, one needs
> to look at much more in the file to do it right. Just sharing my thoughts, I
> don't know what you plans are... :-)
>
> Best regards,
> -Stephan
Sorry for my potentially superfluous question, but is there a standard set of
messages translators will accept to retrieve such data?
Just asking because I use the OpenRaster
(http://www.freedesktop.org/wiki/Specifications/OpenRaster/) format for
StreetPainter and if there is such a standard set of messages, I could
potentially refactor my IO code into a translator. Its currently specific to my
project, as I was lacking advanced capabilities like layer support in the
translator API.
On another thought did anybody think about a standard add-on API for image
filters etc.? Something like provided by the Media Kit for AV stuff?
Cheers,
Rossi
Other related posts:
