kfilemetainfo using strigi

Jos van den Oever jvdoever at gmail.com
Fri Jan 12 10:20:55 GMT 2007

2007/1/12, Sebastian TrĂ¼g <trueg at k3b.org>:
> How about providing a compatibility wrapper strigi plugin that is able to load
> KFilePlugins? This way all the old plugins could be reused until they have
> been ported. Is that possible or do we get a problem with the streaming
> issue?

This is a possibility, yes. This will only mean that files that are
not readable through QFile will not work. This is the case now too, so
there's no problem there.
The hard bit is in how to change the API of KFileMetaInfo. Some things
in there have to change:
 - Interface must pass a QIODevice and not a QFile (easy change)
 - We have to reconsider the role of the mimetype. In Strigi mimetype
has no meaning. Each analyzer looks at the content of the file and
determines from that what it can get out. In KFileMetaInfo, the
combination mimetype + KFilePlugin instance determines the fields that
could be available for a file. In Strigi you dont need the mimetype
for that, but you do need to know if an analyzer can handle a specific


More information about the kde-core-devel mailing list