Action queue concept about data-pen HOT 7 OPEN

+1 from me. We should do this now, while it is still early.

I'm just slowly coming back to work, and will want to finish the refactorings that were left incomplete before my vacation, but can do this after that (if you don't beat me to it).

from data-pen.

Welcome back! I'm hoping to get to this this afternoon, but we'll see. Let's just update here if one of us can start working on it.

from data-pen.

Alright, starting to work on this.

from data-pen.

Not a ton of progress on this. @jiemakel, if you want to take a shot at it, feel free. If I don't hear from you, I may take another stab at it tomorrow.

from data-pen.

So, I just put the Redux-style state/action-based approach in place. Right now it is all in the fibraService, but that will be broken out. At the moment there is no retention of the queue of actions, no reversal of actions, and no immutability on the state, but we're in position to add it. Slowly, we should move all the local state out of the construct view and into this centralized state.

from data-pen.

Can you break this out into a set of tasks with estimates? I'm thinking that the demo for Pelagios is too agressive a deadline for all of this, but maybe part of it?

from data-pen.

Unfortunately I haven't really thought through it enough to break it out, but I'll start to do that. Agreed that the full-featured capabilities are too aggressive for Pelagios, however we are now in a spot where we can do this incrementally. I'll continue to add to and improve this as we work on the other (actual) functionality.

from data-pen.