Re: GSoC History plugin

Joshua Joseph <[email protected]>
Newsgroups gmane.comp.kde.devel.kopete
Message-ID <CAKYNVbSRWp28Gn3JJZN4zOi1jLXP0gkTVa4J7F72o0y_EcJYcQ@mail.gmail.com>
On Tue, Jun 16, 2015 at 12:00 AM, Pali Rohár <[email protected]> wrote:

> .. I do not know if these messages should be
> > > logged or not.
> >
> > I think these messages (user joined, left) should be logged. They can
> > provide
> > context when someone is reviewing the history later.
> >
>
> https://github.com/josh-wambua/kopete/blob/proposal/proposal.md
>
> I looked at updated info in git and I'm still not happy with it...
>
> First storage structure does not allow to save any (relevant/useful)
> information about messages what Kopete::Message class supports
>
>
> http://api.kde.org/4.x-api/kdenetwork-apidocs/kopete/libkopete/html/classKopete_1_1Message.html
>
>
I updated the page to add some relevant message information.


> And second I still do not see how you want to handle multi user chats
> correctly. You are adding session to chat message, but
> Kopete::ChatSession is not useful here. It is destroyed if you close
> chat window, but some multi user chats are still active (e.g. in skype)
> even if you close chat window. Something similar will be in IRC plugin
> too (I believe).
>

I am in communication with Kaushik about that, so we can see how best to
handle multi user chats.


>
> Also I do not know where or how will be stored something like jabber
> resource name...
>
> As I told at the beginning of GSoC, rewriting history plugin is not easy
> and new plugin should have fixed all design problems of previous
> implementations. And first I want to see working storage format...
>
> --
> Pali Rohár
> [email protected]
>
> _______________________________________________
> kopete-devel mailing list
> [email protected]
> https://mail.kde.org/mailman/listinfo/kopete-devel
>
>


-- 
Thanks,
Joshua

_______________________________________________
kopete-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kopete-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.