On Wed, Dec 4, 2013 at 9:34 AM, Brian Matherly <pez4br...@yahoo.com> wrote:
>
>
>>On Tue, Dec 3, 2013 at 9:11 PM, Brian Matherly <pez4br...@yahoo.com> wrote:
>>> Dan,
>>>
>>> I just committed my first implementation of a text producer based on QT:
>>> https://github.com/mltframework/mlt/commit/70b5a1fe2a2aef2ec513c07a15434195d561ca38
>>> Comments are welcome.
>>>
>>> I copied the producer_pango properties/arguments as well as I could. There
>>> are two exceptions:
>>> 1) Obviously, I can't implement the pango markup property. So the markup
>>> property is excluded from qtext.
>>
>> True, but most Qt text facilities support some subset of HTML for rich
>> text. I think there may be some automagic in there as well, and it
>> might be working already.
>
>
> Ok. I'll look into it. If it does work, I may just leave it because there is 
> no sense in trying to strip out markup if it is provided.
>
>
>>> 2) I see an undocumented feature in producer_pango to load text into
>>> keyframes from a .mpl file. I didn't carry that over because I don't know
>>> the use case. But it could be easily ported if necessary.
>>
>> That is legacy because now there is animated properties that can
>> replace it, and it resembles a subtitle file while not being a
>> standard or properly integrated.
>
>
> Ok. I'll happily ignore it.
>
>
>>> My plan is to next modify producer_count and filter_dynamictext to use qtext
>>> first and revert to pango if qtext is not found. if I do that, should I move
>>> those two files out of the GTK folder? If so, to where?
>>
>> I suggest core.
>>
>
> Will do. Must I change the copyright designation then?
> http://www.mltframework.org/bin/view/MLT/CopyrightPolicy

If you do not want to do that, then I suggest renaming avsync as
"pez4brian" and putting in there. I prefer modules be defined by
dependencies, license, and/or copyright terms rather than by function.
I do not want a proliferation of modules when it is not really
required. More modules do slow down every MLT app because the modules
dir is scanned upon init without any cache, and a cache can be tricky
to ensure its consistency. I have been thinking to merge plus and vmfx
into core and removing dv and kino. It should be noted that the kernel
block I/O cache does help significantly timely launches after the
first launch. Also, the increasing popularity of SSD and hybrid drive
helps.

-- 
+-DRD-+

------------------------------------------------------------------------------
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
Mlt-devel mailing list
Mlt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlt-devel

Reply via email to