Here's what I have so far: a model, a view and a delegate.
Em 14 de setembro de 2010 18:56, Luiz Romário Santana Rios <
luizroma...@gmail.com> escreveu:
>
>
> Em 14 de setembro de 2010 15:51, Lamarque Vieira Souza <lamar...@gmail.com
> > escreveu:
>
> Em Sunday 12 September 2010, Luiz Romário Santana Rios escreveu:
>> > Em 12 de setembro de 2010 16:10, Lamarque Vieira Souza
>> >
>> > <lamar...@gmail.com>escreveu:
>> > > Hi Luiz,
>> >
>> > Hi.
>> >
>> > > I think you remember me from Akademy-br.
>> >
>> > I do.
>> >
>> > > What exactly do you call a
>> > > "Kopete instance"? Is it a separated process? Do you want to run more
>> > > than one
>> > > Kopete process? At least for now I think that is not possible, Kopete
>> is
>> > > coded
>> > > to run only one instance per user as far as I know.
>> >
>> > I'm aware of that, but it doesn't need necessarely to be a separate
>> > instance; there would be a contactlist per identity instead of only one
>> > contactlist holding all the identities on a computer, but the process
>> could
>> > be the same. However, when a user re-opened Kopete - by typing "kopete"
>> on
>> > Alt+F2 or through the menu, it would show an identitylist, each one
>> showing
>> > its label, picture and accounts, showing also the connected ones, their
>> > text being bold. I think having a Kopete process per account would be
>> > better, but that's up to the mantainer.
>>
>> I do not like the idea to have to choose the identity everytime I
>> launch
>> Kopete. You should use the last used identity instead, if the user wants
>> to
>> change to a different identity he/she should do it through the menu or
>> another
>> mechanism. One process per account is overkill, it would make handling
>> metacontats more complex.
>>
> 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.
> And it wouldn't be a process per account, but per identity. Thus, handling
> metacontacts wouldn't be a problem, as I can't see when allowing different
> identities to share a metacontact is desirable.
>
>
>>
>> > > 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.
>
>
>>
>> > > I am not familiar with this part of Kopete's
>> > > internals. Two months ago I talked to Daniel (from KDE-MG) about this
>> > > problem
>> > > and we are not sure if it is possible to make one kopete process to
>> have
>> > > one
>> > > password for each identity. Does anyone here know if that is possible?
>> >
>> > Maybe, via KWallet. One could assing a wallet per user, if they wanted
>> to.
>> > Or the user could have a master password for their identity, but that's
>> > basically Kwallet's concept.
>>
>> We would need different wallets per identities here, that would
>> make
>> using Kopete a little troublesome because most people use only one wallet.
>> The
>> default identity should use that one wallet used by the other KDE programs
>> to
>> simplify the use. Only when using other identities the user will be asked
>> the
>> password to unlock that identity's wallet. I am just not sure if kwallet
>> allows one process to open several wallets with different passwords.
>>
> I agree, although I think setting a wallet per identity could be left as an
> option. But what about a master password per identity? Currently, if you
> don't store a password for a given account, it's password will be asked
> every login. That is, if an identity has a lot of accounts without
> passwords, the user will have to type one password per account. In that
> case, a master password for each identity would make it act as a
> "sub-wallet" only for IM accounts.
> Suggestions?
>
>
>>
>> I like your idea and I think other people will make use of it.
>> Unfortunately I am very busy and probably will be for the a long time, I
>> cannot help you with the implemenation.
>
> I see. No problem, though, you already helped me a lot by giving such
> feedback.
>
>
>> Does anybody here want to help with
>> this implementation?
>>
> I would appreciate that.
>
>
>>
>> > > Em Sunday 12 September 2010, Luiz Romário Santana Rios escreveu:
>> > > > Resending without attachment.
>> > > >
>> > > > Hello for the first time.
>> > > >
>> > > > I had some ideas for Kopete which I'm willing to implement. Here's
>> an
>> > >
>> > > image
>> > >
>> > > > to help you understading:
>> > > > http://img844.imageshack.us/img844/2646/ideiaskopete.png
>> > > >
>> > > > 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.
>> > > >
>> > > > What do you think? If you think it's fine, then I'll need some help
>> on
>> > > > Kopete internals.
>> > > >
>> > > > Best regards.
>> > >
>> > > --
>> > > Lamarque V. Souza
>> > > http://www.geographicguide.com/brazil.htm
>> > > Linux User #57137 - http://counter.li.org/
>> > > http://www.kde-mg.org
>> >
>> > Best regards.
>>
>>
>> --
>> Lamarque V. Souza
>> http://www.geographicguide.com/brazil.htm
>> Linux User #57137 - http://counter.li.org/
>> http://www.kde-mg.org
>>
>
> Best regards.
>
> --
> Luiz Romário Santana Rios
>
--
Luiz Romário Santana Rios
Index: kopete/CMakeLists.txt
===================================================================
--- kopete/CMakeLists.txt (revision 1175396)
+++ kopete/CMakeLists.txt (working copy)
@@ -2,6 +2,7 @@
add_subdirectory( addaccountwizard )
add_subdirectory( statusmenu )
add_subdirectory( identity )
+add_subdirectory( identitylist )
add_subdirectory( contactlist )
add_subdirectory( config )
add_subdirectory( chatwindow )
@@ -15,6 +16,8 @@
${CMAKE_CURRENT_BINARY_DIR}/statusmenu/
${CMAKE_CURRENT_SOURCE_DIR}/identity
${CMAKE_CURRENT_BINARY_DIR}/identity
+${CMAKE_CURRENT_SOURCE_DIR}/identitylist
+${CMAKE_CURRENT_BINARY_DIR}/identitylist
${CMAKE_CURRENT_SOURCE_DIR}/contactlist/
${CMAKE_CURRENT_BINARY_DIR}/contactlist/
${CMAKE_CURRENT_SOURCE_DIR}/config/plugins/
@@ -25,6 +28,7 @@
${KOPETE_BINARY_DIR}/libkopete
${CMAKE_CURRENT_BINARY_DIR}/addaccountwizard
${CMAKE_CURRENT_BINARY_DIR}/identity
+${CMAKE_CURRENT_BINARY_DIR}/identitylist
${CMAKE_CURRENT_BINARY_DIR}/contactlist
)
@@ -65,7 +69,8 @@
kopeteaddaccountwizard
kopetestatusmenu
kopetecontactlist
- kopeteidentity)
+ kopeteidentity
+ kopeteidentitylist)
install(TARGETS kopete_bin ${INSTALL_TARGETS_DEFAULT_ARGS} )
Index: kopete/kopeteapplication.cpp
===================================================================
--- kopete/kopeteapplication.cpp (revision 1175396)
+++ kopete/kopeteapplication.cpp (working copy)
@@ -51,6 +51,8 @@
#include "kopeteviewmanager.h"
#include "kopeteidentitymanager.h"
#include "kopetedbusinterface.h"
+#include <identitylistview.h>
+#include <identitylistmodel.h>
KopeteApplication::KopeteApplication()
: KUniqueApplication( true, true )
@@ -64,6 +66,11 @@
m_mainWindow = new KopeteWindow( 0 );
Kopete::PluginManager::self();
+
+ Kopete::IdentityListView *idlv = new Kopete::IdentityListView;
+ Kopete::IdentityListModel *idlm = new Kopete::IdentityListModel;
+ idlv->setModel(idlm);
+ idlv->show();
Kopete::UI::Global::setMainWidget( m_mainWindow );
_______________________________________________
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel
