> Passing postscript code to other backends indeed is a good idea ;-)
So you agree that a hook mechanism discriminating between backends is a good
idea. That's why I proposed it.
---
** [issues:#5162] Some hooks useful for video production**
**Status:** Started
**Created:** Tue Jul 25, 2017
I don't think that there will be an agreement with David, so uploading to
Rietveld is probably pointless.
---
** [issues:#5162] Some hooks useful for video production**
**Status:** Started
**Created:** Tue Jul 25, 2017 05:48 PM UTC by Knut Petersen
**Last Updated:** Wed Jul 26, 2017 11:51 AM
Passing postscript code to other backends indeed is a good idea ;-)
Yes. Every single person who wants to override code that cannot be overriden
from within a score source might ask for a patch - but once implemented
everybody can use that hook. Nobody will ask again.
---
** [issues:#5162] S
> Other people might want to try doing animated SVG and I don't see the point
> in having them start over.
These would be happy to have the possibility to use overloaded-rgb? and
probably would need an extended svg dump-page. So they probably would ask for a
predicate use-svg-dump-page-replacem
> You state that this approach would lead to
>> useful extensibility.
> I tend to believe that it is nothing but over-engineering.
Well, it will save you or the next person this kind of discussion next time
they want to implement something along that line. For example, you are only
interest
> I believe that KISS is still one of the most important principles.
Hidden functionality violating existing data checks and passing unrelated data
through fields intended and document for something else working only for a
single application and a single backend and requiring new surgery for eve
