I want the syntax to reflect what Lily is doing inside. If you can figure out a way to unify both types of properties internally, I will unify the syntax.
Ideally, the user shouldn't need to know anything about the structure of the implementation. If we need the separation, we also have to be able to explain it in a way that's obvious to a person who has never done any programming.
Also, one problem from the users side, even when you have realized the difference between translator properties and backend properties, is that it's not always obvious if a certain feature belongs to the translator or to the backend, when you start searching for a property. I notice that the direct overlap between the two cathegories has decreased since 2.0.0 (where e.g. the translator property tupletInvisible directly translated into two backen properties), but the border line is still a bit fuzzy.
/Mats
_______________________________________________ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
