by Hooray » Fri Apr 10, 2020 10:09 am
There are several quick fixes that could be used at this point, either back-porting the work previously committed by James and GIjs, or exposing the projection handling to Nasal space via cppbind, so that a Nasal function can be used instead. Originally, Tom didn't like the latter though, because he wanted to avoid unnecessary Nasal overhead at runtime. Another idea we toyed with in response to TorstenD commenting on the issue, was using the property rule system for projections - because those are automatically XML-configurable, and everything runs at C++ speed anyway.
Technically, that would entail adding new projections in the form of property rules and then adding a Canvas projection to use a configurable property rule for each projection.
But if that's done, we'd have native speed/performance, and XML-level configuration options in XML space, i.e. if/when the need arises for a new projection, it can be implemented in the form of property rules.
Preferences / opinions ?