Thank you Dan for your reply.
I completely agree with you - a crop
filter should be the first in the chain (and it is, even in my
implementation), and the MLT framework should not be changed only
because it would be handy for me.
Meanwhile, I searched another way to
go ahead: i wrote the
melt and the xml module require using the loader producer. The loader
producer is very special and chooses which real producer to use based on
the resource string - configured in loader.dict - as well as adding what
we call normalization (aka conform) filters - configured in loader.ini.
Extremely
