Re: Creating a new image loader

Ruben Lopez <r.lopez-u/[email protected]>
Newsgroups gmane.comp.kde.gwenview
Message-ID <[email protected]>
Hi,

Thanks for your reply. By following the KImageIO plugin design I finally 
have an I/O plugin for the Softimage PIC format working properly with 
most KDE tools (tested with Kview, Kuickshow, and Kcolourpaint).
But for some reason, it is not working with gwenview :( The weird thing 
is that gwenview manages to create thumbnails, but it does not show the 
image in full screen or in the left panel. In fact, the left panel says 
"No image selected".

The format that I am supporting (Softimage PIC), is the main image 
format for 3D Animation industry working with Softimage|XSI. Our company 
would like to start using gwenview in production, but I can't get it 
working with PIC images. Any help with this would be much appreciated.

Thanks in advance.

Lubos Lunak wrote:
> On Monday 21 of May 2007, Ruben Lopez wrote:
>   
>> Hi,
>>
>> I want to add my custom image format to gwenview. I have searched
>> documentation and found that I should add this to KDE, which means
>> adding it to Qt, this way:
>>
>> QImageIO::defineIOHandler( "format-name", "header-regexp", 0, read_func,
>> write_func );
>>
>> But how can I make gwenview know this new format, I mean, should I make
>> a .so library and put it somewhere where gwenview will look for?
>>
>> I can force loading of a .so library along with gwenview with an
>> LD_PRELOAD, but I would like to use a cleaner way ;)
>>     
>
>  Have a look at KImageIO 
> (http://websvn.kde.org/branches/KDE/3.5/kdelibs/kimgio/ , there's README).
>
>   

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.