Apps may want to provide fileitemactionplugins without using other KIO functionality. The FIAP stuff doesn't use any KIO functionality itself, so having it in a low tier frameworks such as KGuiAddons would help that use case.
KAbstractFileItemActionPlugin uses KFileItemListProperties which has ties to some other KIO classes, however, looking at the usage only a list of urls and their mime type is actually needed
We need to decide on what KIO is.
Some people think "if I don't need kioslaves, I shouldn't have to use KIO".
But another line of reasoning is "if you want to do any sort of file-management stuff with URLs, files, dirs, mimetypes, then KIO[Core] is what you want". KFileItem, KFileItemListPropreties, KFileItemActionPlugins... this all fits into this definition.
Where else would one put KFileItem and KFileItemListProperties?
KAbstractFileItemActionPlugin should certainly move from KIOWidgets to KIOCore, but I'm unsure about moving it further down the stack. KFileItemListProperties is very useful to determine properties of a list of file items...
KAbstractFileItemActionPlugin should certainly move from KIOWidgets to KIOCore,
Agreed, that is already covered in other tasks
but I'm unsure about moving it further down the stack. KFileItemListProperties is very useful to determine properties of a list of file items...
I agree, should we close this task as invalid?