[Kde-imaging] Re: kdeextragear-libs-1/kipi-plugins

[Jesper K. Pedersen]

On Wednesday 16 June 2004 10:11, Gilles Caulier wrote:
| Le mercredi 16 Juin 2004 09:42, Jesper K. Pedersen a écrit :
| > On Wednesday 16 June 2004 09:23, Gilles Caulier wrote:
| > | Le mercredi 16 Juin 2004 09:16, Jesper K. Pedersen a écrit :
| > | > On Tuesday 15 June 2004 15:13, Gilles Caulier wrote:
| > | > | CVS commit by cgilles:
| > | > |
| > | > | Fix 'kipi' instead 'digikam':
| > | > | - In comments.
| > | > | - In dialog text and title.
| > | > | - In temporaly folders creation.
| > | > | - In ressource loading path (specific icons, script, etc.)
| > | > | - Handbook page call (PENDING : the kipi handbook must be created -
| > | > | based on Digikam plugins sections handbook).
| > | > |
| > | > | IMPORTANT : There is a very important _PENDING_ task to do : the
| > | > | kipirc file must have a config line for the images files filter
| > | > | using in the plugins. Digikam rc file have this line from the
| > | > | Albums files filter config.
| > | > |
| > | > | For example, from the CDArchiving plugins, the pending
| > | > | implementation is
| > | > |
| > | > |
| > | > |   // PENDING (Gilles) : Using kipirc file!
| > | > |   // Read File Filter settings in digikamrc file.
| > | > |
| > | > |     m_config = new KConfig("digikamrc");
| > | > |     m_config->setGroup("Album Settings");
| > | > |     QString Temp = m_config->readEntry("File Filter", "*.jpg *.jpeg
| > | > | *.tif *.tiff *.gif *.png *.bmp"); m_imagesFileFilter = Temp.lower()
| > | > | + " " + Temp.upper();
| > | >
| > | > Can't you just use the functions from KImageIO for this?
| > |
| > | Digikam use a basic images filter for images MIME types support. This
| > | is the reason for that.
| >
| > I'm afraid you lost me here.
| > Can you put me in the right context. Are we talking about file formats
| > that the plugin is capable of reading? I mean what does it help that .xyz
| > file appears in a file open dialog or similar of the backend doesn't know
| > how to read these?
|
| In the past, DigikamPlugins have used the digikamrc config file. Digikam
| have a image files filter for to limit the Albums images rendering on main
| GUI.
|
| In according with that, the Digikamplugins use this configuration for all
| image operations.
|
| For example, the imagesgallery use this config for resizing only the images
| from the Albums in according with this image files filter.
|
| > | Perhaps, libkipi can provide a mime type selection widget for the
| > | images like plugins selection widget. The hosts will can use that in
| > | the setup dialog...
| >
| > If we are talking about which types the host is capable of reading,
| > wouldn't it be better to ask the host application through the interface?
|
| I think the host and the plugins must be use the same images type MIME
| config. It's more explicit for the users.
So in Digikam the user can configure which format to consider, in other apps 
it is simple the list of formats supported by KDE.

To me it makes perfectly sense to have a
virtual QStrignList Interface::fileExtensions() {
  // by default return the supported formats by KDE.
}

Or am I missing something crucial here?