>>> 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 don't mind, I just want to make sure I follow the policy. I certainly don't want my own module. > I prefer modules be defined by > dependencies, license, and/or copyright terms rather than by function. Makes sense to me. Those are the use cases by which someone might want to disable a module. > 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. I hadn't thought about proliferation and loading time, but it makes sense. I'd be happy to move the avsync, dynamictext and count services into core. I would much rather have my contributions more integrated into MLT rather than keep my name in the copyright field. One thing you could consider would be to create a single module for all compatible contributions. The layout could look like this: * core - Includes required modules - MLT isn't much use without these - These modules should not have dependencies outside of core - Copyright attributed to Ushodaya Enterprises Limited * contrib - Includes useful contributed modules - These modules should not have dependencies outside of core or contrib (some exceptions possible for dependencies that are highly likely to be met) - The license of files in this module must be compatible with core so that contrib can always be included in any build/release - Copyright may be attributed to the author(s) * anything else - Not in contrib because the license is not compatible with core, or it has a dependency that may not be available - Can be optionally excluded at compile time If we went this route, I think the following modules could go into contrib: avsync, kdenlive, oldfilm, plus, rtaudio, vmfx, xml I agree with removing dv since avformat covers DV. I agree with removing kino. To move vmfx into core, you would have to change the copyright attribution. Maybe that's not a problem. I would like to see the kdenlive directory disappear as well. Anyway, I'll move avsync, dynamictext and count into core unless I hear otherwise. But let me know if you would like any help with any other reorganization - I'd be happy to help. ~Brian ------------------------------------------------------------------------------ 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
