edit-add -> list-add
You have no idea how hard it was to reduce the number of
"add" icons from two to one. I nearly died in the process :-S
The difficult part, of course, was to find the answer
to the everlasting question "What does each icon mean?"
And these are my findings:
* If you add anything to a list (or something else that is
some kind of collection of items), you use list-add.
* If you remove something from that list (or collection)
without destroying the removed object itself (because
it's only a reference to something outside),
you use list-remove.
* If you delete something from that list (or collection)
and the item that you deleted had its home in the list
and is therefore destroyed on removing,
then you use edit-delete.
Phew. Who wants to open up a TechBase article on using icons?
svn path=/trunk/KDE/kdebase/workspace/libs/plasma/; revision=753984
libplasma
Commit Rules:
* If your patch is not an obvious or trivial bug fix, have it peer reviewed
by another Plasma developer
* All code MUST follow the kdelibs coding style, as found at:
http://techbase.kde.org/Policies/Kdelibs_Coding_Style
* All new public API MUST have apidox written before committing
Unit tests are next to godliness. (Though as you can see, right now libplasma
is hellbound.)
This directory contains the classes making up libplasma, which provides the
core framework used by Plasma and its components. This includes applet and
extension definitions and loading, common GUI elements, etc.
Domain specific sets of functionality, e.g. for network awareness or sensors,
are not found here but in one of the Plasma Engines.
Please refer to the Plasma website (http://plasma.kde.org) and Plasma wiki
(http://techbase.kde.org/Projects/Plasma) for API documentation and design
documents regarding this library.
9f2e3e276e