[Kdenlive-devel] Release and future...
jb at kdenlive.org
Sat Sep 3 07:35:53 UTC 2011
On Friday 02 September 2011 16:51:57 Dan Dennedy wrote:
> On Fri, Sep 2, 2011 at 4:06 PM, jb <jb at kdenlive.org> wrote:
> > In my version, we simple put one xml copy for each version of the
> > filter, and Kdenlive will only load the correct version.
> What is the comparison logic for version selection? For example, what
> happens when a new version of a plugin is made but Kdenlive is not yet
> updated? Also, there can be version changes that do not require a
> change in Kdenlive (e.g. crash fix).
The different xml versions of the filter should be all put in one file, in
chronological order (older on the top, newest at the bottom).
When parsing the xml files, Kdenlive stores the effects in a list based on
their "id" tag. If two effects have the same id, the last parsed will replace
the first one (no duplicate id allowed).
So, now let's say you have an xml file like that:
<effect id="blah" version="0.2">
<effect id="blah" version="0.3">
Let's say we have the filter at version 0.2. Kdenlive will load the first
version in any case (it has no version tag). Then, it will load the second one
that will replace the first one. The third one will be discarded since it
doesn't match our version number.
If we have the filter at version 0.5, Kdenlive will load the last one (0.3).
This way, Kdenlive will always load the latest available version for your
I will document this in the xml readme file.
More information about the Kdenlive