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

List:       kopete-devel
Subject:    Re: [Kopete-devel] Contact list abstraction
From:       Olivier Goffart <ogoffart () tiscalinet ! be>
Date:       2003-03-30 18:12:31
[Download RAW message or body]

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

Martijn Klingens wrote:

> On Sunday 30 March 2003 18:47, Jason Keirstead wrote:
>> IMO the whole contact list interface should be abstracted. There
>> is no reason Kopete should know or care if the underlying contact
>> list format is XML, KConfig, a SQL database, or gotten via some RPC
>> calls to another server.
> 
> And reinventing Kiosk for all settings along the road? You still bypass
> the whole issue.
> 
> The issue is not about whether to use XML or KConfig. That's the result.
> Not the issue.
> 
> The issue is that we first need to separate the config from the contact
> list, as currently contactlist.xml holds both.
> 
> So whatever approach you pick, there must be a THOROUGH abstraction
> between config and non-config. And config should have *FULL* Kiosk
> support.
> 
> If you think you can achieve in an abstract API without the mapping that I
> don't even want to think about implementing, go for it. But don't expect
> me to write a KConfig plugin since if you manage to do that everything
> that _has_ to be in KConfig is already there and I don't really need a
> KConfig for the rest (I just think it's by _FAR_ the easiest and most
> sensible choice).

I am realy against to use plugin for save the contactlist, or others
settings.
It should be done in libkopete, like now  (i mean where, not how)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+h0EWz58lY8jWrL0RAvgfAKCASUOk3A4ZrIDd1zk5C1KSFdvzSQCePPh/
/GMgG1T0xi9cSdZAEoxLIvo=
=Gfih
-----END PGP SIGNATURE-----
_______________________________________________
Kopete-devel mailing list
Kopete-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/kopete-devel
[prev in list] [next in list] [prev in thread] [next in thread]