2010/9/16 Tomáš Trnka <tomastr...@gmx.com> > Hello, > > although it's true that my last commit to Kopete was two years ago, I'm > still > following the development closely (and probably will re-join soon), so let > me > share my view of the proposed changes. > > > > > > > But it basically separates one identity for Kopete instance, > since > > > > > > it makes no sense to have more than one indentity an a same > Kopete > > > > > > instance in my opinion. Beyond, it gives the user the option to > > > > > > login quickly into an account. > > First and foremost, as far as I can see it, the whole point of Kopete is to > integrate all your IM needs in one place (something like what Kontact does > for > mails&stuff). That way the user can talk to Jack from the HR department and > to > her teenage son the same way, without needing to think "Ah, so Jack is my > colleague, that means I'll have to use the corporate Jabber to contact him, > and that's this window here". Using Kopete, as it is now, all she needs to > do > is click the tray icon, write "Jack" into the search bar and click the > metacontact. All the technicalities (like which account to use to contact > him) > are handled automatically. (And the IM management duties get even easier if > you use the KAddressbook integration.) > I know, handling all of your accounts at once is the whole point of KDE. But what are identities for, if not for letting many different users use the same account? I mean, if one user needs only one Identity, what's their use anyway?
> > And what does "login quickly into an account" mean exactly? As far as I > know > KWallet already lets you do exactly that. > Logging in without registering an account, as a guest, let's say. > > > I think I didn't express it well. You won't have to choose the identity > > everytime you run Kopete, you will have this option, since every identity > > will have its own icon in the systray. And, yes, logging in the last used > > identity would be the _default_ behavior, but not the only one, because > > there would be some cases in which this is not desirable (multiple users > on > > a same computer is the most obvious example). Other mecanisms could be > > available as well. > > That gets us back from the all-integrated multiprotocol multi-identity > client > we have now to seven different icons in the systray and users having to > carefully pick which one to use, each and every time. > I think you're getting my idea wrong. I'm not willing to separate different accounts, but rather, different identities. And that's useful if two people are using Kopete at the same time, IMO. > > And as far as multiple users go, there's no need to reinvent the wheel > here. > Every modern OS (including Linux) allows you to have many users on the same > machine, with full separation (including IM ;-)). > 1 - Many people use the same computer at the same time. It's not very cool to switch to another session when a message arrives and, then, switching back to the previous session. And what about three users at the same time? 2 - Whole new Linux, X and KDE sessions just for Kopete? > > > > > > Having more than one identify for one instance has its use, so > > > > > has using different passwords for each identify (if configured to > > > > > do so). I think that is what you want, right? > > > > > > > > Kind of. Not only that, but, as I already said, a separate > contactlist > > > > and conversation window(s). > > > > > > > Separated contact history too, although I think separated history would > > > be automatic by using separated contactlist, I am just not sure of > that. > > > > Yes, it would be included. The idea is: separate each identity > environment, > > so they can't interfere each other unless both users want to. > > Then just go ahead and run two kopete processes with different config dirs > :-) > I think that that's not very straightforward. > > Long story short: I feel the proposed changes drastically alter the > principles > of Kopete. Therefore I don't think this can be easily integrated without > breaking current functionality and making lots of users very unhappy. > Making > it configurable is IMHO not reasonably possible without bringing in much > code > bloat and UI clutter (that the rest of KDE is trying very hard to get rid > of). > Well, take this mail into consideration. If you still don't feel convinced, maybe I could do some other stuff (or a fork :p). > Best regards > > 2T > > _______________________________________________ > kopete-devel mailing list > kopete-devel@kde.org > https://mail.kde.org/mailman/listinfo/kopete-devel > > Best regards. -- Luiz Romário Santana Rios
_______________________________________________ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
