You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some functions that you use in rules will take keyword arguments that need to be pre-filled by the user before using the function in a rule. They're a kind of partial function, similar to what you'd use in functools.partial.
A user of ELiDE should be able to fill those arguments in graphically, just by filling out a form.
The text was updated successfully, but these errors were encountered:
I've stopped liking the idea of making new rules that are just partials wrapping stored functions; it complicates the data model more than just making the rules dependent on some stat of the entity they're about. However, it's currently too difficult to tell which stats are relevant to any given rule, and you have to back out of the rule configurator screen to go set those, which isn't very usable.
So there should be graphical forms on rules in the configurator that just change the relevant stat on the entity. Building those will require either static analysis on the rule's parse tree, or the rule's author manually specifying a relevant stat, perhaps using a new decorator.
Some functions that you use in rules will take keyword arguments that need to be pre-filled by the user before using the function in a rule. They're a kind of partial function, similar to what you'd use in
functools.partial
.A user of ELiDE should be able to fill those arguments in graphically, just by filling out a form.
The text was updated successfully, but these errors were encountered: