Le dimanche 14 décembre 2008, George Goldberg a écrit : > On Sun, Dec 14, 2008 at 1:04 PM, Olivier Goffart <[email protected]> wrote: > > Le jeudi 27 novembre 2008, Eva Brucherseifer a écrit : > >> Hello Matt, > >> > >> as discussed on IRC, we had a student investigating how to use kopete > >> protocol plugins within the Telepathy infrastructure. > >> Here is the promised list of issues Roman came up with. I hope it is > >> useful for you. > > > > Hi, i'll do some comments: > > I think this email is better suited for kopete-devel, so i'll cross-post. > > The original email and his attachement can be found here: > > http://mail.kde.org/pipermail/decibel/2008-November/000167.html > > > > http://mail.kde.org/pipermail/decibel/attachments/20081127/317585ad/attac > >hment-0001.pdf > > > >> 1. GUI-Calls at the libkopete-protocol-implementations > > > > Well, we discussed that a lot. The idea was to have a strong separation > > between the ui ans the logic. In a ideal world, neither libkopete, > > neither plugins/protocols would do any ui call. > > In a real world this is just not possible because there is many protocol > > or plugin specific ui that cannot be abstracted. > > > > And even in libkopete, it make few sens to remove _all_ ui call just for > > the so called purity of the design. > > > > I think that the level of separation we have now in libkopete regarding > > the ui/logic separation is good enough. > > The point is that Telepathy connection managers are separate processes > to the UI's, so the protocol implementation simply cannot directly > affect the UI.
Sure, and i think it's one of the reason the telepathy design is bad. There is always stuff that cannot be completely abstracted because the way it works with different protocol is way to different. Thoses stuff need different UI. Take the account config as an example. While some stuff are quite similar, there are some options that better should stay different (the way you can register new account, revoking your account, resources, nickname .... Some feature are very secific to a protocol and have no reason to be shared (I think about jabber services, or gateway). Or you will end up writing protocol specific ui in libkopete, which is a worse design. > >> 2. Parameters to connect to an account > > > > I don't see anything wrong with the current design. > > What is "wrong" is that it does not work in the way telepathy does. In > telepathy there is an AccountManager process which stores all the > account details, and when a connection is opened, it calls the > Connection Manager with the desired account details to be connected > to. Mhh, still i don't see anything wrong in kopete's way. Telepathy doesn't do the same, but you can easily convert from one to another.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Decibel mailing list [email protected] https://mail.kde.org/mailman/listinfo/decibel
