On Friday 21 July 2006 03:53, Roman Jarosz wrote: > 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. >
You are insane if you want to use friend classes. > 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. > insane. :) > 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 also not what I envisoned. :) I think we need to sit down and discuss this if you're going to continue the work. I have everything up in my head and it's not always easy for me to get everything out on paper in a way that's coherent. I have the exact design in mind that I want to use, and if I can better communicate that on IRC, I think you guys will like it. I think it rocks, so it has to be good, right? ;) When is good for y'all? -- Matt _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
