The framework models a contact as a list of property types, with no, one or more items of a type for each contact. There are three types of services for a property (e.g. email address):
* action service (e.g. send email)
* data action service (e.g. send file per email, like from drag'n'drop)
* status service (e.g. number of unread emails in assigned folder)
The tarball includes a lot of services for the most common properties:
* birthday: copy date; has birthday
* im address: chat with; send message; send file; online status
* email address: send email; copy address; send files/urls;
open assigned folders in KMail; unread emails in assigned KMail folder
* homepage: open; copy url;
* blog feed url: copy
* phone number: make call; send fax; send SMS; copy number;
* postal address: open in Google Maps; copy address
* note: copy note
Examples for programs using the framework are a contact cards server and a kicker applet, which are available as seperate packages:
http://www.kde-apps.org/content/show.php?content=34479
http://www.kde-apps.org/content/show.php?content=50766
Includes (partial) translations for:
ar, be, bg, br, cs, da, de, el, es, ga, gl, it, ja, nl, pa, pl, pt, pt_BR, sk, sv
Thanks to the translators! No unsermake needed.
Please see also http://frinring.wordpress.com/2006/07/05/framework-for-contacts-and-services-slowly-getting-shapes/
Developers, you are welcome to try to create own services! Have a look at the folder "contacts/properties/example"
If you want to build directly from KDE's repository:
svn co svn://anonsvn.kde.org/home/kde/trunk/playground/pim/ -N
cd pim
svn up contacts
svn up contactsapplet
svn up contactcards
svn co svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kde-common/admin
make -f Makefile.cvs
./configure
make
su -c "make install"
PS: Packagers are welcome
Ratings & Comments
12 Comments
Hello! I tried to install this framework from KDE's repository. But I get an error: msd@bcn:~/contactsmenu/pim/pim$ make -f Makefile.cvs This Makefile is only for the CVS repository This will be deleted before making the distribution ./admin/cvs.sh: 651: --version: not found *** AUTOCONF NOT FOUND!. *** KDE requires autoconf 2.53 or newer make[1]: *** [cvs] Error 1 make: *** [all] Error 2 msd@bcn:~/contactsmenu/pim/pim$ autoconf -V autoconf (GNU Autoconf) 2.60 Can anybody help? Thanks, Max
Does http://wiki.kde.org/tiki-index.php?page=ErrorMessages#_autoconf_not_found help?
Yes, that's it! Thanks a lot!
after your clarification i realized i have to add this as a "miniprogramm" to my taskbar. this is correct? unfortunately i am not able to *move* this programm in my kicker. could you fix this? you usually have this context menu if you click the icon to move it left/right. hmm.. difficult to explain, but i guess you know what i mean? additionally, the icon is too huge, if using "normal size".
1. Correct. 2. Support for moving applets is given by Kicker, nothing an applet developer can do about. To move things around, undo the fixing of the kicker bars and click the small handler bar next to the applet, like one has to do for all applets (don't mix the treatment with that of builtin buttons, they behave differently :/ ) 3. Icon is too huge? Iconsizes should be calculated by the size of the kicker bar. Could you send me a small screenshot, to show what you mean? kossebau (at kde org.
i am not sure how i could use this, really? it compiled and installed fine, though.. i have no idea what to edit for *your*type, etc.. (those "your" variables i would have to edit. hmm.. maybe as usual i am too dumb?
Not too dump :) It's just a little bit complicated, as I want to promote the framework, which is not usable by itself, only for developers. So plain users should just add the applet to Kicker and have fun. The config file is only needed for people adding their own properties and services, which includes coding :) Hm. Perhaps I should promote the applet separately. Added a hopefully useful comment to the description for now.
thanks for clarifieing this. and happy x-mas, btw ;)
you display this after running "unsermake install", shouldnt it be displayed after "unsermake"? anyway, compiled fine on amd64, thx! *************** Important ************************* This module contains unreleased software. The software may compile and work, but it may just as well neither compile nor work. ****************************************************
no idea, why it only is shown after "unsermake install". I think that should be better shown directly after "configure". But I am not in the buildsystem business, just using the KDE scripts and svn2dist.
I haven't been able to test this, but it really seems useful to me. Have you considered joing the kde-pim or plasma teams?
He is :) http://frinring.wordpress.com/2006/12/17/dumped-contacts-framework-as-010/