I wanna discus what would be best for Kopete contact list Model-Storage interface. With Michael Larouche we agreed we'll be using "friend classes" to not bloat the public API of MetaContact/Group. Now with friend classes we have two possibilities.
First: add friend keyword to MetaContact/Group for every interface. Like XmlMetaContactStorage,OtherMetaContactStorage ... so we will have access to d-pointer and protected and private members. In this case to save/restore MetaContact we'll access these members directly. Second: We make generic class MetaContactStorage, that will have functions for saving/restoring and will have access to d-pointer and protected and private members. By functions for saving/restoring I mean setPicture/picture, setID/id etc.. And than XmlMetaContactStorage will only use functions of MetaContactStorage to save/restore MetaContact. In this case we don't need to add friend keyword for every xxxMetaContactStorage to MetaContact and we only have limited access. Roman Jarosz _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
