Scripting language for properties

[kirkedal]

This can even be extended to a small scripting language, that can
calculate grades and similar. We can even move the calculation of Total and
MaxPoints to have a predefined summation of the leaves.

[oleks]

I think I'd prefer a "specification language" to a mere "scripting language". It is fun to define dynamic properties, as you mentioned in #6, but it is even better if you can declare mandatory properties. I'm not exactly sure what you were thinking, but maybe we should go ahead and declare a separate remarks template format where properties can be specified/scripted? This would make this related to #13.

[oleks]

But I would warn against over-engineering this. I think remarks, without further/better design considerations, will only be fast if we keep it simple.

[kirkedal]

I have not made much considerations of this and it is not a priority. I would also not make it too advanced. Just thought that is would be useful over time i some form. Basing it on a template structure makes much sense as it will be much easier to update. It would the be obvious to have a `remarks update [dir]` that can update the individual files from the specifications in the template.

…

On 18 January 2017 at 19:02, Oleks ***@***.***> wrote: But I would warn against over-engineering this. I think remarks, without further/better design considerations, will only be fast if we keep it simple. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#15 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB15lry9azj5xVtH9l4lLuBOk_guuo2Gks5rTlOZgaJpZM4LnK_J> .