On Mon, Oct 08, 2007 at 03:49:10PM +0200, Will Stephenson wrote: > On Sunday 07 October 2007, Olivier Goffart said: > > Le samedi 6 octobre 2007, Matt Rogers a ?crit?: > > > On Friday 05 October 2007 05:15:22 pm Olivier Goffart wrote: > > > > Le mardi 2 octobre 2007, Charles Connell a ?crit?: > > > > > > I think address is bad. I'm sure I think this because of the way I think > > > of addresses. I'm open to it though. :) > > > > Do you have another suggestion. > > We need a short name for the class. > > Another idea is to call the class ProtocolContact or AbstractContact > > You know 'abstract' is reserved for indicating an abstract data type, don't > you? > > ImAddress? >
This works, although I wonder if the Contact/ProtocolContact split isn't a bit better... > > so s/\bContact/AbstractContact/g > > > > And call the subcontact as "addresses" or "protocol identifier" > > > > > NO! *pounds fists hard on desk* Kopete is NOT just a sort of GUI for the > > > addressbook. That is so completely and totally bogus. Kopete is an > > > INSTANT MESSENGER that allows its users to store details about their > > > messenger contacts in their address book. > > Is this comedy outrage or for real? It's for real. To imply that Kopete has no other purpose but to be a GUI for the addressbook is completely wrong, IMHO. This is the meaning that is implied when I see comments like "Kopete is just a sort of GUI for the addressbook, after all", at least from my POV. > > > What is an addressbook? > > http://en.wiktionary.org/wiki/address_book > > It is a list of contact associated with their contact information (such as > > instant messaging address) > > > > What is the kopete contactlist? This is an interface to an addressbook. > > > > What is the point of having two storage point for contact lists in kde > > (kabc, and kopete) > > > > The Kopete ContactList window should be a particular interface to the > > addressbook, showing especially intant messaging information. > > > > > The use of Kopete does not require an addressbook, nor should it. > > > > I think it should. > > This has been discussed for very long time, and the idea was that we should > > repace the contactlist.xml almost entirely with the addressbook. (Akonady) > > I'm with Gof on this (surprise surprise). And if Gof, the leading proponent > of "Kopete as classic standalone IM client" in recent times, now says this, > I'm interested to know why you feel we should stop with an 'INSTANT > MESSENGER'. > > Will > To somehow minimize the fact that Kopete is an instant messenger is wrong, IMHO, and this is what I object to. Do I care if we store the contact list in akonadi? No. In fact, it's a good idea. I still want the ability to use a contactlist.xml file though. It's the whole reason I wanted to abstract out the contact list loading. Why? Mostly because, as a developer, I want to be able to not worry about fucking up my possibly important data if I make my program crash or whatever while I'm hacking on it. So whether we separate the data in akonadi or allow developers to use a contactlist.xml file, I don't care as long as I can have separation when I want it. This is the part where the use of Kopete should not require an addressbook. After all, the storage mechanism shouldn't matter anyways. So, blanket statements like "Kopete is just a sort of GUI for the addressbook" will continue to piss me off, because, in my mind, that's not what Kopete is. KABC is a GUI for the addressbook. Kopete is an instant messenger that has kick ass integration with your KDE address book. Does that mean that I think we should minimize the amount of integration we do? No. Does that mean that we should keep people from using Kopete as a sort of GUI for the addressbook? No, because that's how some people will end up using it anyways, and I'm fine with that, as long as I don't have to use it that way. What it does mean is that I don't think we should put so much focus on the addressbook stuff as to make it the whole reason people should use Kopete. People should use Kopete because it has kick ass protocol support, oh, and as an added bonus, it rocks even more because it integrates so well with your KDE address book too. Although, my viewpoint on this should come as no surprise since I've been preaching for better protocol support for quite awhile now. Hopefully this clarifies things for everybody. -- Matt _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
