2010/9/16 Tomáš Trnka <tomastr...@gmx.com> Dne Čt 16. září 2010 Luiz Romário Santana Rios napsal(a):
> 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? Well, I personally have two identities in Kopete - one for private purposes (chatting with friends) and one for work (corporate Jabber). The former one contains a nickname and some private information, while the latter needs to > be formal with only my real name, work position & e-mail and stuff like that. Almost every Kopete user I know has some kind of similar setup. You have two identities, each one with one account? Well, there could be a "merge" option for such cases, i.e., an option to make the contacts of two different identities appear on the same window. But why two identities with one account each and not an identity with two accounts? > > 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. Now that's some interesting functionality, indeed. However, I don't know whether it's worth the hassle... I don't think it's much hard. Just make a button/tab/whatever to show a account-configure-like dialog, create a guest account and connect it. But maybe I'm wrong, since I'm not yet familiarized on Kopete's internals. By the way, don't you think that making the guest's contacts appear in the same contactlist of the user would be too messy? Not to mention the remaning offline contacts forever on the contact list after the guest leaves. > > 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. How do two people end up using Kopete at the same time? A dual-monitor > dual- keyboard system? I didn't mean _exactly_ at the same time. But, for example, me and my brother are watching a movie and we both are connected on GTalk. Or I'm using the computer and my friend asks: "Lemme check my Live Messenger". Anyway, there are lots of situations where two users use a same computer in the same user; > > 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? Switching a X session takes a second, tops. It's certainly not a lot slower than switching a window. Starting a KDE session then starting Kopete takes some good amount of time. Beyond, a good amount of memory. And if you really need to run several Kopete instances for different users within one KDE session, nothing is easier than su user2 -c kopete (or > KDEsu, or making a desktop/menu icon to run Kopete as that user). That user would have to be created before. And, well, creating an identity is certainly easier. > > > > > > 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. oK, true, but it's just a matter of creating a simple wrapper > script/desktop file. The idea is only to separate identites and its accounts, not the whole configuration. > Well, take this mail into consideration. If you still don't feel > convinced, > maybe I could do some other stuff (or a fork :p). Of course, this all is just my opinion and that doesn't matter much (and > I'm not the maintainer). Let's see what other people think, too. 2T _______________________________________________ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel 2010/9/16 <cyberb...@gmx.de> > Hi, > > please let me also share my view: sometimes it is really desirable to have > two > people be connected with kopete temporarily in one desktop session, and > this > is what I would expect from multiple "identities" to solve. > > > 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? > > I (and most other users I think) will only have one kopete identity, and > this > identity concept is more confusing than helpfull. The default behavior with one identity will be automatically asking its password and connecting all of its accounts. That is, the identity concept would only apper when necessary and if wanted. Otherwise, it'll be straightforward. In other words: if the user does not need more than one identity, they'll be greeted with a contact list as usual. > I would prefer a solution > with running multiple kopete-sessions as different users in one desktop- > session (this does not work in the moment I believe? perhaps some > kde-services > have to be started additionally for the other user?). I wouldn't be sad, if > the concept of multiple identities would be removed from kopete. > That's basically what i purpose, only that, instead of different users, I want to use different identities. > > Any other solution should not make the configuration of kopete even more > complicated as it is, sane defaults may help here but may not solve all > configuration problems. > I don't think it will be complicated, since my idea does not alter the concept of identities, just gives it a new use. > > Volker > _______________________________________________ > 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
