Re: GSoC History plugin (Was: Re: Kopete - GSoC 2015)

Pali Rohár <[email protected]>
Newsgroups gmane.comp.kde.devel.kopete
Message-ID <201506141625.06103@pali>
On Sunday 14 June 2015 16:13:39 Joshua Joseph wrote:
> On Sun, Jun 14, 2015 at 5:08 PM, Pali Rohár <[email protected]>
> wrote:
> > Quick look at database schema:
> > 
> > Columns:
> > entry_id (int, primary key)
> > timestamp (text)
> > protocol (text) - (the protocol in use)
> > direction (text) - (either incoming or outgoing)
> > local_id (text) - (the account being used locally)
> > remote_id (text) - (the remote account)
> > message (text) - the content of the message
> > 
> > This is not sufficient for multi user chat messages!
> > 
> > I know at least two different types of multi user chat types used:
> > 
> > 1) chat rooms - every message from sender is sent to chat room and
> > every received message is either from remote contact to chat room
> > or from chat root to local contact or from remote contact to local
> > contact
> > 
> > 2) multi user chat - every message is sent from sender (local
> > contact) to every received in multi user chat -- there is no chat
> > room, just list of receivers
> 
> We were discussing of having a groups table, where every group
> conversation is stored with a group_id.
> 

Then please update draft API. Do not forget to include also room name 
(somewhere) and also that room name do not have to be present.

> > Plus some protocols provide additional information about sender and
> > receiver. E.g. in jabber we have "resource" which is part of every
> > contact (local or remote).
> > 
> > Some messages could have priority or type (e.g. IRC messages /me,
> > ...). This is not handed here.
> > 
> > And what is "message"? Plain text? Html message? or something else?
> 
> I'll add a message_type column.
> 

Look at Kopete::Message class. It supports more then type. Plus think 
about messages like incoming file transfer or user joined chat 
conversation... I do not know if these messages should be logged or not.

> > On Sunday 14 June 2015 15:57:51 Joshua Joseph wrote:
> > > Hi all,
> > > 
> > > I have been working on a draft API for the history plugin:
> > > 
> > > Here is the draft so far:
> > > https://github.com/josh-wambua/kopete/commits/devel
> > > 
> > > Comments are welcome. :)
> > > 
> > > On Sat, Jun 13, 2015 at 8:14 PM, Pali Rohár
> > > <[email protected]>
> > > 
> > > wrote:
> > > > Hello :-)
> > > > 
> > > > What is state of your kopete projects? Can you show me what
> > > > have you done since start of GSoC? Do you have any parts which
> > > > are ready for merging into kopete master (or other branch)?
> > > > 
> > > > --
> > > > Pali Rohár
> > > > [email protected]
> > > > 
> > > > _______________________________________________
> > > > kopete-devel mailing list
> > > > [email protected]
> > > > https://mail.kde.org/mailman/listinfo/kopete-devel
> > 
> > --
> > Pali Rohár
> > [email protected]
> > 
> > _______________________________________________
> > kopete-devel mailing list
> > [email protected]
> > https://mail.kde.org/mailman/listinfo/kopete-devel


-- 
Pali Rohár
[email protected]

_______________________________________________
kopete-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kopete-devel
signature.asc (application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEABECAAYFAlV9jsIACgkQi/DJPQPkQ1LI3wCdFGE6s0XN+olGZUO7cwXnodtu
wfEAn2F6wYorxCTDfOacagZ4baDiOoVT
=w1F7
-----END PGP SIGNATURE-----
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.