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
Right now, both are intermingled in TickerItem which really should be a common interface between both. What I propose is to create a RenderItem and LogicItem for the Item and extend off those base classes. This may change, but the overall goal is to be able to separate what should be logical or render operations.
For example, setting the style of a DOM Element, to me, counts as a render since it updates on the screen. A position that's tracked separately will then be used to update the style of the DOM element. This is a logical operation. The reason why we're being more explicit about this is because right now, updating position also clashes with trying to discern the logic of things.
We're basically trying to solve this problem.
The text was updated successfully, but these errors were encountered:
Right now, both are intermingled in
TickerItem
which really should be a common interface between both. What I propose is to create aRenderItem
andLogicItem
for theItem
and extend off those base classes. This may change, but the overall goal is to be able to separate what should be logical or render operations.For example, setting the style of a DOM Element, to me, counts as a render since it updates on the screen. A position that's tracked separately will then be used to update the style of the DOM element. This is a logical operation. The reason why we're being more explicit about this is because right now, updating position also clashes with trying to discern the logic of things.
We're basically trying to solve this problem.
The text was updated successfully, but these errors were encountered: