Re: [CinePaint-dev] VICAR file r/w - status

[Robin R. <ro...@mo...>]

Daren,

> It was just over one year ago i volunteered to add VICAR format 
> read/write capability to Cinepaint.  

Glad to hear from you. I was thinking about VICAR. My friend who 
designed the Mars Pathfinder flight software was here last week for my 
birthday.

 > I hacked
> XV to read VICAR; that's the closest to a handy tool we have for now.  
> There are a lot of things XV is no good at.     Those of us doing daily 
> production work (e.g. cover image for December National Geographic) use 
> GIMP and like it.   Of course it's only 8 bit/channel.   So, there still 
> exists demand for Cinepaint with VICAR  

Are you using xv VICAR now? Do you convert files using xv or do you have 
a GIMP plug-in for VICAR?

> Now, exactly where to start?   add VICAR to  Glasgow 0.1 since it's the 
> fresh new thing?  

If you have a GIMP plug-in it would be trivial to port to CinePaint Film 
Gimp. Although not binary compatible, many GIMP plug-ins can be built 
for CinePaint without change. You could use the legacy Film Gimp API 
supported by Kai-Uwe. Or if you want to work with me you could try the 
new Glasgow img_img plug-in API. I'd have to walk you through that. 
Either way, 95% of the code would remain the same. Not a big deal to do 
both. If you can reuse your VICAR code from xv it should go pretty quick.

Don't use the Glasgow GUI plug-in API. That's a temporary hack pending 
integration with the img_img API. The img_img program is command-line 
tool and therefore easier to test and debug than with a GUI. The design 
goals for the img_img API are to make it easier and faster than the Film 
Gimp API.

What would you like to do?

Robin
--
CinePaint.org