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

List:       koffice-devel
Subject:    Re: Plugin versioning
From:       Boudewijn Rempt <boud () valdyas ! org>
Date:       2005-04-19 10:21:39
Message-ID: 200504191221.49560.boud () valdyas ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Tuesday 19 April 2005 12:07, David Faure wrote:
> On Tuesday 19 April 2005 10:11, Boudewijn Rempt wrote:
> > On Tuesday 12 April 2005 11:25, David Faure wrote:
> > > Ah, you're talking about KParts plugins, those which only provide a .rc
> > > file (and an optional .desktop file following the plugininfo format)
> > > and which inherit KParts::Plugin?
> > >
> > > I'm afraid those don't have versioning support.
> > > I can add that to KParts::Plugin::loadPlugins for the future though.
> > > What do you think? Meanwhile you'd better overwrite the installed .rc
> > > files with empty ones when removing a plugin...
> >
> > I may be useful; but I can also do what Kate, Digikam and other apps have
> > done, and load the plugins myself. One day I will have to anyway, so a
> > scripting plugin can know what filters and tools are available and that
> > kind of thing.
> >
> > But I guess I won't get done before the release now :-).
>
> Not before the beta, of course (it's ready now, except for binary
> packages), but for the final release you can still add some versioning
> support, to avoid problems later on.

What steps should I take? Add a .desktop file to every plugin with a version 
field?

-- 
Boudewijn Rempt 
http://www.valdyas.org/fading/index.cgi

[Attachment #5 (application/pgp-signature)]

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


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