@evs-chris what is interpolator plugin?https://ractive.js.org/plugins/#interpolators
Have we somewhere any description of this feature?
Dumb question. Do components get instanciated? Or they are reused? If I have +1000 copies of the same component, should I move some logic to helper functions?
Should I preparse the template?
I think yes, I always use preparsed templates (ready to use AST).
Component is js constructor. So, each component in markup become an instance of this constructor like this:
new MyComponent()
I don't think so, that it's good idea to use +1000 copies (instances) of component in Ractive. I think components in Ractive not the same thing as in React, for example. You can use partials to make these things cheaper.
I'm not sure where the interpolator plugins thing came from or what it's supposed to be. Afaik there no such construct.
and yes, using thousands of component instances can be quite expensive, whereas partials are only slightly more expensive than regular template
Maybe interpolator plugins supposed to be a way to doing such things like:
{{#await /}} but by 3rd party devs?
I don't think so, because in ractive terms only a
{{...}} is an interpolator, and {{#...}} is a block
I'm thinking maybe it was meant for filters/helpers, which ractive doesn't have
though helpers are in proposed changes related to computed props
Yup. There is such a thing as interpolators in Ractive, but they were previously undocumented and no plugins actually exist of that nature. I'll check it out and write documentation about it.
Fun fact: there's only one unit test written for it. :tada:
ohhhhhhh
those interpolators!
I've actually written one before
I also confuse them with easings btw :D
takes a css color of some sort and tweens to another case color of some sort
so easing takes a time point and adjusts it from linear to whatever, and the interpolator takes that time code and converts it into an intermediate value based on the start and end values
:thumbsup:
I see interpolators take a
from and to, while easings take an x to return a y. Does that mean interpolators use easings for each value from from to to?
indeed they do, but not directly
:thumbsup:
I believe both return functions that take a single decimal between 0 and 1 (well, maybe just outside of that for bouncy easings) as their only input and return a corresponding value
Ahh, got it the other way around. Easing gets called first, then interpolator. Each tick, easing gets called to translate a step (0-1) into progress (a bouncy 0-1). Then given that progress, interpolator gets called to translate progress to a value (translates progress in terms of
from and to).
Interesting...
I'm thinking maybe it was meant for filters/helpers, which ractive doesn't have
though helpers are in proposed changes related to computed props
Hm, what difference between helpers/filters and:
data: { foo: () => {} }
?
I always believe that it actually is helpers/filters in Ractive style
I'll check it out and write documentation about it.
It'll be very nice, thx!
:+1:
helpers are the same thing effectively, but with no nesting, so no need to prefix
and also more easily installed in Ractive.defaults
some people really hate functions in their data, apparently
Interpolator and updated
ractive.animate docs will be up in a few. :tada:
👌
:+1: