[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] Addressbook - link to advance contacts ?
From:       Guenter Schwann <schwann () icg ! tu-graz ! ac ! at>
Date:       2002-06-13 14:47:18
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 13 June 2002 16:04, Bryan Brunton wrote:
> << Who's saying that you should drop your work? We just point you to a
> technical solution to connect your application with KDE.>>
>
> Geez, Guenter, you must be reading a different list than I am.  Are you
> actually following the discussion?  Here is one example that occurred just
> on this thread:
>
> "Instead of starting thousands of new projects you could bring
> your manpower in kde-pim development."

Well - that was only one quote (I don't know of any more), and you told us to 
drop kde-pim...

> << That's what we told you all the time: _it does make sense to you to
> write a libkabc backend_>>
>
> That's what people said, but as I mentioned they never actually provided
> any technical reasons for doing so until that post.  Instead, people were
> busy relating how there used to be three KAddressBooks and that there
> should never be another one, etc.

Cornelius Schumacher wrote about the benefits of using libkabc several times, 
and you always replied, that you don't want to use it.

> << Supporting multiple different addressbook interfaces is a lot of work to
> maintain. We aren't willing to do it>>
>
> I don't remember asking anyone to support multiple different addressbook
> interfaces.  I do remember asking for the ability to allow the user to use
> a different addressbook if that is what he wants to do.

Users can use _any addressbook without any work for us_. But as soon as the 
addressbook should be used by KDE-applications (KMail as you want), there is 
sone maintainace work (just starting the addressbook doesn't help anyone).

> << But
> the benefit of libkabc is, that you can easily make a "plugin" (backend).
> So we still have the one interface for our apps.>>
>
> If I write the libkabc backend, I won't actually use it as a backend for my
> UI.  Libkabc is too limited.  I will simply use it so that KMail can
> talk to my database.

No one even suggested that your font- and backend should communicate via 
libkabc. Libkabc is just for the communication with the KDE-applications. And 
this is, what we wanted to make you clear is the best for all.
When you make a libkabc backend, then the KDE-applications can use your 
addressbook (nearly?) without change of _any line of code_ in KDE and 
Advance. So Andvance can use the full power of your addressbook, and KDE can 
use what it needs.

ciao
- -- 
Guenter Schwann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9CLB543e2O3Z+/CQRAmllAJ489I2t+5iLR/3rs8p+OEQDPyYcZACfau5n
/cADxhqC7KnBNnH91PXkAIw=
=Hckh
-----END PGP SIGNATURE-----

_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]