-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/07/2011 10:51 AM, jb wrote:
> On 09/06/2011 11:21 PM, Till Theato wrote:
>>> So after a good coffee, here is my proposal:
>>>
>>> 1 - Move the upgrade code from trackview to documentvalidator
>>> (which is a more logical place for updates to th
On 09/06/2011 11:21 PM, Till Theato wrote:
>> So after a good coffee, here is my proposal:
>>
>> 1 - Move the upgrade code from trackview to documentvalidator
>> (which is a more logical place for updates to the document)
>>
>> 2 - Put the upgrade code in a different xml file, called like the
>> kd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/06/2011 12:49 PM, jb wrote:
> On 09/06/2011 09:53 AM, jb wrote:
>> On 09/05/2011 04:48 PM, Till Theato wrote:
> In my version, we simple put one xml copy for each version
> of the filter, and Kdenlive will only load the correct
> vers
On 09/06/2011 09:53 AM, jb wrote:
> On 09/05/2011 04:48 PM, Till Theato wrote:
In my version, we simple put one xml copy for each version of
the filter, and Kdenlive will only load the correct version.
>>> The attached patch is what i came up with. As I already said I
>>> will drop the ad
On 09/05/2011 04:48 PM, Till Theato wrote:
>>> In my version, we simple put one xml copy for each version of
>>> the filter, and Kdenlive will only load the correct version.
>> The attached patch is what i came up with. As I already said I
>> will drop the adopt function (and therefore the changes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/04/2011 12:26 AM, Till Theato wrote:
> On 09/03/2011 01:06 AM, jb wrote:
>> On Saturday 03 September 2011 00:44:46 Till Theato wrote:
>
1) Change the effect XML depending on the filter version
I did some test and managed to have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/03/2011 01:06 AM, jb wrote:
> On Saturday 03 September 2011 00:44:46 Till Theato wrote:
>
>>> 1) Change the effect XML depending on the filter version
>>>
>>> I did some test and managed to have a working implementation
>>> that will bring diff
On Fri, Sep 2, 2011 at 3:05 PM, jb wrote:
> 1) Change the effect XML depending on the filter version
>
> I did some test and managed to have a working implementation that will bring
> different parameters depending on the filter version, see my last commit:
> http://kdenlive.svn.sourceforge.net/vi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/03/2011 01:45 AM, Dan Dennedy wrote:
> On Fri, Sep 2, 2011 at 4:06 PM, jb wrote:
>> On Saturday 03 September 2011 00:44:46 Till Theato wrote:
>>> For the update thing to work a MLT release would be required,
>>> too. @Dan?
>>
>> Oh, you mean be
On Friday 02 September 2011 16:51:57 Dan Dennedy wrote:
> On Fri, Sep 2, 2011 at 4:06 PM, jb 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 exampl
On Friday 02 September 2011 16:45:22 Dan Dennedy wrote:
> On Fri, Sep 2, 2011 at 4:06 PM, jb wrote:
> > On Saturday 03 September 2011 00:44:46 Till Theato wrote:
> >> For the update thing to work a MLT release would be required, too.
> >> @Dan?
> >
> > Oh, you mean because the frei0r version is n
On Fri, Sep 2, 2011 at 4:06 PM, jb 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 Kde
On Fri, Sep 2, 2011 at 4:06 PM, jb wrote:
> On Saturday 03 September 2011 00:44:46 Till Theato wrote:
>> For the update thing to work a MLT release would be required, too. @Dan?
>
> Oh, you mean because the frei0r version is new in MLT... right I didn't think
> about it...
of course
>> > Once bo
On Saturday 03 September 2011 00:33:27 Alberto Villa wrote:
> On Saturday 03 September 2011 00:05:23 jb wrote:
> > Hi all.
>
> hello there!
>
> only one thing: i will have exams until sep 23. either we wait until sep 24
> for the git migration (unless i'm lucky enough to find half an hour to do
On Saturday 03 September 2011 00:44:46 Till Theato wrote:
> > 1) Change the effect XML depending on the filter version
> >
> > I did some test and managed to have a working implementation that
> > will bring different parameters depending on the filter version,
> > see my last commit:
> > http://
On Saturday 03 September 2011 00:44:46 Till Theato wrote:
> Does everybody already have KDE git access?
> @Dan, you might want to apply for an account too. (via identity.kde.org)
i do. i'll ask for your git access and see what you need (i knew how it
worked back in svn days)
--
Alberto Villa, Fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/03/2011 12:05 AM, jb wrote:
> Hi all.
>
>
> We are already very late for the 0.8.2 Kdenlive release, so I would
> like to prepare it in the beginning of next week.
>
> Most remaining issues have been fixed if I am right, we only need
> the upg
On Saturday 03 September 2011 00:05:23 jb wrote:
> Hi all.
hello there!
> We are already very late for the 0.8.2 Kdenlive release, so I would like
to
> prepare it in the beginning of next week.
great!
>
> Most remaining issues have been fixed if I am right
i'm sorry if i didn't help with this
Hi all.
We are already very late for the 0.8.2 Kdenlive release, so I would like to
prepare it in the beginning of next week.
Most remaining issues have been fixed if I am right, we only need the upgrade
mechanism for the frei0r plugins that did not follow the specs (0 - 1 range
for double pa
19 matches
Mail list logo