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

List:       kmail-devel
Subject:    Re: S/MIME
From:       Ingo =?iso-8859-15?q?Kl=F6cker?= <kloecker () kde ! org>
Date:       2003-08-27 20:28:41
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Wednesday 27 August 2003 20:17, George Staikos wrote:
> On Wednesday 27 August 2003 12:04, Stefan Rompf wrote:
> > Am Montag, 25. August 2003 22:06 schrieb George Staikos:
> > >    Well the biggest problem right now is that the "plugin"
> > > architecture is only designed to support one plugin: the gpg
> > > based one.  This needs to be fixed so that it is KDE standardized
> > > and freedesktop XDG compliant. the XDG spec (I think that's the
> > > right spec) defines the location for plugins to be installed, for
> > > instance.
> >
> > Also, the crypto plugin API is very much tied to Aegypten. This
> > makes it possible to use the Aegypten plugins outside KDE too, but
> > limits the KDE features the KSSL plugin can use, for the simple
> > reason that the API does not always pass all information needed.
> >
> > I already thought about a direct integration of S/MIME into KMail,
> > but I'm far to unfamiliar with the code right now. And the weather
> > was too good this summer ;-)
>
>    The plugin system is a better idea IMHO.  It should be made
> abstract though, so that Agypten isn't the only possible plugin.

But the plugin system should be limited to crypto plugins I guess. I was 
thinking about writing KDE-style wrapper plugins for the two Aegypten 
plugins. Then other crypto plugins could be directly written as KDE 
plugins and KMail would automatically find all plugins via the KTrader 
mechanism. (That's how it should have been in the first place.)

> > >    If the plugin system can actually be turned into a *plugin*
> > > system and not a hardcoded library path to ~, then I propose we
> > > finish up the KSSL S/MIME plugin and commit it to kdepim or
> > > kdeaddons.
> >
> > Do we want to meet the KDE3.2 schedule for this? From my point of
> > view, the KSSL plugin is stable, but using it is still a bit raw:
>
>   We don't have to release the plugin, but we should definitely fix
> the plugin architecture so that we can release the plugin later.

I agree.

Regards,
Ingo

[Attachment #5 (application/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]