Moving KFIleMetadata into KDE SC (documentation and ExtractionResult)
me at vhanda.in
Wed Jan 22 17:47:37 GMT 2014
On Wednesday 22 January 2014 13:09:58 David Edmundson wrote:
> Add COPYING file
> ExtractorPluginManager::fetchExtractors seems odd to me.
> If it can't find any plugins it searches for all plugins that start
> the same prefix.
> I assume it's designed so I can have a plugin with the mimetype audio/
> that will still match the file mimetype audio/mp3
> But this means that if I add a special new plugin with the mimetype
> audio/mp3 the original plugin will stop running? Given you're trying
> to build a list of all valid plugins, is that meant to happen?
I've added the relevant documentation.
> Having setInputUrl / setInputMimetype public in a way which can be set
> by the plugins seems wrong; personally I'd put the two in the
> We should document the list of names of properties that can be extracted.
> Some things are in lowerCamelCase i.e "wordCount" "author" except for
> the eviv plugin which is in the form:
> and the odf extractor which is in the form
> to me it seems fairly random.
Fixed. Added a proper property and type system.
More information about the kde-core-devel