On Friday 27 October 2006 02:31, Michaël Larouche said: > I had a small discussion with Robert McQueen about my questions and nothing > to worry about :)
> > - Respect of KDE settings (Proxy, Phonon, Address Book, etc...) > > > > They are some bug report about some protocol plugin that doesn't respect > > the KDE proxy settings. How do we ensure those settings are respected > > using Telepathy. > > > > Also for the voice and video, we will need to tell the connection manager > > to use those devices and settings from Phonon configuration. > > For proxy, we just need to use "http-proxy-server" parameter. For the rest > I'll discuss that with Telepathy folks in time. But nothing is impossible. Thanks for clearing that up, Michael > About audio/video: > > <Robot101> and don't worry about audio devices > <Robot101> connection managers don't use them > <DarkShock> that's the job of the streaming engine ? > <Robot101> well, we're going to make it into a library if possible > <DarkShock> ok > <Robot101> so you can just take gstreamer src/sink and hook it up, then > point the library at the channel We'll need to get the gstreamer blinkers off them soon. > > - Specific interface for type of protocols, to not loose specific > > functionality of each protocol (disco search in Jabber) > > > > This is about regression of features. The main point of Kopete is to > > integrate many protocols into a consistent interface but without loosing > > the native features of protocols. This is one reason I started using > > Kopete(or any similar program) because I wanted multiple native support > > for each protocol, which is not the case in Jabber Transport. I was tired > > to switch to a native MSN client just to transfer file. I'm thinking > > about Service discovery in Jabber. Robert McQueen talked about maybe > > doing interface for specific protocols in Telepathy specification. > > This is a low priority for Telepathy guys and they want to make > it(Telepathy) work without exposing protocol specific interface in the main > interface. > To quote Robert: > "<Robot101> the idea is to make most stuff work without exposing > protocol-specific madness like that" > > > - What about the UI in protocol plugin ? > > > > What we shall do about the UI in protocol plugin ? We can't use them > > anymore since the implementation is separated by D-BUS. > > Somehow the UI in the current protocol will migrate to the main > application. Time will tell :) That's something we can work on. A Gnome-style limited configurability philosophy is fine for their frontends but we will want to do more. Maybe it's worth looking at the jabber protocol Gof mentioned for this, so CMs can export their UI in a standard way that most IM clients already know how to represent. Will _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
