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

List:       kmail-devel
Subject:    Re: RFC: Detecting omitted attachments
From:       Karl-Heinz Zimmer <khz () kde ! org>
Date:       2002-03-01 8:05:16
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 28 February 2002 23:21, Waldo Bastian wrote:
> On Thursday 28 February 2002 01:19 pm, Volker Augustin wrote:
> > Maybe it's better to search for combinations. "attach" + "file". That
> > still can give false positives. But in that case, false positive is
> > better that a missing attachment.
>
> I think it should be somehow possible to offer functionality like this in
> the form of a plugin of some sort.
>
> For that to work, plugins should be able to register themselves and be
> called before a mail is send. I am sure there are more actions where it
> would be nice to have hooks for plugins.

Maybe a good way how to do that could be by extending the new Plug-in
interface we designed for the Ägypten project?

We are not fully done with that work and therefor it isn't in the HEAD
branch yet but in a separate AEGYTPEN_BRANCH branch of the kdenetwork.
The web page is here:

    http://www.gnupg.org/aegypten

There we use a new interface for adding Plug-ins to KMail: you are free
to register a Plug-in by specifying an arbitrary name for it and telling
the configuration dialog where the Plug-in binary is to be found...

At the moment our interface only supports Cryptography Plug-ins but there
is nothing that prevents the concept from being enhanced to support other
kinds of Plug-ins as well: using a methode called

  bool hasFeature( Feature flag )

the Plug-ins could inform KMail about the things they are providing...

We defined a (C style) API for designing such Plug-ins and our own
crypto Plug-in for the Aegypten project actually _is_ written in plain C
since we are using it for mutt as well but of course we have a little
warpper module (called CryptPlugWrapper.h / .cpp) to allow convenient
access to the Plug-in via C++.

In theory (especially if your Plug-in in intended for usage from inside
KDE program only) you could just write a C++ Plug-in and make sure it
can be loaded by the wrapper class.
The wrapper uses the following, simple functions to access the respective
Plug-in library:

            dlopen(..);
            dlerror();
            dlsym(..);

So all you need to know is your Plug-ins binary name and the names of the
respective functions.

Of course before adding new functions to the Plug-in interface we should
be informed so we could make sure these functions are added to the _global_
specification to prevent us and you from having different APIs for the
same thing...

The AEGYPTEN_BRANCH (and the Plug-in interface) will be merged into the HEAD
branch very soon after CeBIT 2002 so we expect it to be part of KDE 3.1.

Cheers,

  Karl-Heinz

- -- 
Karl-Heinz Zimmer, Senior Software Engineer, Klarälvdalens Datakonsult AB
<mailto:khz@klaralvdalens-datakonsult.se>            <mailto:khz@kde.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8fzZDCcaVnbvggDcRAnUMAJoCiYNeyS/iv2+aIv1BuGAgHsaBmgCgxu9z
uXtkw6nPXcEUhWvg5RQO8x0=
=LTqZ
-----END PGP SIGNATURE-----

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail
[prev in list] [next in list] [prev in thread] [next in thread]