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
We currently specify a field name and a property setter function for fields we want to expose to the user.
It may be possible to abstract this slightly further and just use reflection to determine which fields are on a given Effect object (already can do this with something like Reflect.fields()). The hard part is determining the Type of the field so we can automagically associate the right PropSetterFunc with it.
Pros: Even less for the user to mess up
Cons: Would still need a way to let users provide their own setters if they want to do something with the values (.... this may not be true as the user can just do the transformation at apply() time.
The text was updated successfully, but these errors were encountered:
Can we somehow utilize macros or typedefs? As this is input through raw strings, it may be hard to do through raw use of the library. It might make more sense to have this repo have an editor that lets you build strings. Though we'd have to figure out a way to import effects from other projects... Perhaps have a place to drop code that this will auto-register for use in the editor?
We currently specify a field name and a property setter function for fields we want to expose to the user.
It may be possible to abstract this slightly further and just use reflection to determine which fields are on a given
Effect
object (already can do this with something likeReflect.fields()
). The hard part is determining the Type of the field so we can automagically associate the right PropSetterFunc with it.Pros: Even less for the user to mess up
Cons: Would still need a way to let users provide their own setters if they want to do something with the values (.... this may not be true as the user can just do the transformation at
apply()
time.The text was updated successfully, but these errors were encountered: