These are chat archives for jdubray/sam
blockquote A parent/child SAM implementation is relatively trivial, the parent needs to instantiate the child as it renders the corresponding view, once the child is ready to return control to the parent, it presents a proposal to the parent's model.
I have been looking for an example for this after searching this forum on all the discussions about components and parent child implementations after trying to reason about who would take on what responsibility .. e.g: still not clear if it is best practice for a child component to have its own model, state, view , action stack or not.. etc..
would it be much to create an example that just uses plain JS
I have been thinking about how a SAM implementation would look for the equivalent of the components tutorial in cycleJS with passed in props and how the output is merged into the main app stream. http://cycle.js.org/components.html
Can a quick example of this nature be put together fairly easily?
well that is where the strategizing comes in that i have been having a hard time with.... to make or compoent or not; how much responsibility of the component; how to communicate with them and how to make the parent app implement it etc..
i took it on myself to try and create SAM implementation of the same tutorial that i used to learn cycleJS when i first discovered it and I find myself failing misreably