> I don't expect that you will ever succeed in decoupling the idea of a
'KDE Application' from the 'KDE Workspace'.
Why not?
This is actually one of the easier ones IMHO since it reflects end users'
reality best, i.e. apps like Amarok, K3B, Kontact, etc. being used on
other workspaces than KDE's.
> not that it matters because all the distinctions you are trying to make
are pointless, even meaningless to the end-user.
Isn't it mainly interesting for the end-user?
I mean if the communication from the creators better fits into what the
end-users are already doing (using apps built with KDE Development
Frameworks on workspaces built on different frameworks).
It should additionally help those who are still uncertain about that or
uncertain about whether the creators will consider it a bug if it doesn't
work like that.