[Kde-pim] kleopatra system tray
Kevin Krammer
krammer at kde.org
Sun Aug 4 13:30:05 BST 2013
On Sunday, 2013-08-04, Lindsay Mathieson wrote:
> On Sun, 4 Aug 2013 10:36:16 AM Kevin Krammer wrote:
> > It isn't in a library and even if it where it is in kdepim which does not
> > install any public API doe not give any guarantees API or ABI wise.
> > So I would also think that (1) is the better approach.
>
> Ah, i assumed that since it had its own entry on api.kde.org
> (http://api.kde.org/4.x-api/kdepim-apidocs/kleopatra/html/classSysTrayIcon.
> html) it was a shared component.
Ah, understandable confusion :)
As an open/free source project we basically don't differentiate between public
and private or, maybe better, exernal/published and internal API when it comes
to documentation.
In either case a class or component is ideally usable by a developer who has
not worked onf the component itself, only requring the documentation to be
good enough.
One way to find out whether there are more users of a class (for example for
an internal class in multiple apps within the same module) it so search for it
on lxr.kde.org, which holds a cross reference of all of KDE's code base.
A good rule of thumb is whether a class is in one of the library repositories,
e.g. kdelibs or kdepimlibs.
It could still be internal to a library, so the only reliable way to tell is
to check the respective CMakeLists.txt and look for whether the header is part
of an install() rule's FILES set.
In this case its location in kdepim already removed any compatibility
constraints as far as policies are concerned, however it could still be part
of a module internal library and effect more than one application of said
module. On closer look that does not seem to be the case either.
Cheers,
Kevin
--
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20130804/409be718/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
More information about the kde-pim
mailing list