[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: KMail drag and drop
From:       Sébastien_Laoût "\[temporar\]" <les83plus () free ! fr>
Date:       2004-08-26 13:30:39
Message-ID: 1093525735.3192.138.camel () localhost ! localdomain
[Download RAW message or body]

Re,

> kdepim/libkdepim/maillistdrag.* contains a description of the latest 
> classes used for drag and drop of mails.

Ho... libkdepim! It's what I missed.

> Each mail in a draglist has 
> a serialNumber which is a unique number that identifies a message. 

Cool. It's already there!

> Using DCOP KMail can be instructed to show a mail by using showMail 
> as defined in kmail/kmailIface.h.

> k_dcop_signals:
> k_dcop_hidden:

!! Wasn't knowing the existence of that (but never studied deeply DCOP).

> But all of these interfaces are private kdepim interfaces, they are 
> subject to change without notification and are intended for internal 
> kdepim usage only.

Ho. Bad news.
Do you forsee to make it public?
Would be very usefull (at least in my case, but for user scripting too,
I think...).

> [seb@localhost seb]$ dcop kmail KMailIface showMail 1 "mId"
> no such function
> [seb@localhost seb]$ dcop kmail KMailIface showMail
> no such function

OK... Hum I will learn DCOP (and how to use hidden methods, if possible)
and go back after that :-)

And what is the need for a QString messageId when a Q_UINT32
serialNumber is here? Seem the same for me.

I could try to begin to code with that MailSummary and showMail (if I'm
allowed to call it)...
But it could be good to have official KMail support.

And what about the "message/rfc-822" appending and/or mbox?

Cheers,

Sébastien Laoût.


_______________________________________________
KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel
[prev in list] [next in list] [prev in thread] [next in thread]