There are lot of component system trying to solve encapsulation of UI logic for reusability, but they don’t seem to solve the inter component communication issue. How do/should components/template-instance talk to each other to perform unit actions. Eg. If I have a edit post dialog component that …

You can use a reactive var or reactive dict based approach. If what you’ll be tracking is very template/component specific, you can keep it scoped to the component’s creation. Or, as you have already decided, you can create a central “place” to hold state. Don’t think of it like a dispatcher, but t…

@serkandurusoy Lets take my example above and apply a state management solution per your comment. Lets assume that we have two components postDetail(shows the full details of a post) and postTile (shows just a tile version of a post). Each of these component/template need the functionality to allow …

For the specific case of dialogs, I make them children of the issuing template.

@Steve That solve the problem but you end up with dialogs everywhere. I think its much better to use a single instance for performance and ease of code management.

To accomplish that we need to add another state. …See where this is going. Why do you need multiple states? You can use a reactive dictionary instead of a reactive variable. That would be to keep a common context. Then, your states could beobject literals that contain: name of the state track…

@serkandurusoy Would be great if you can elaborate on your last post with code sample. It wasn’t clear to me as to your description of using reactive dictionary. Can you provide a sudo code sample on the editPostDialog scenario.

Sure. Here’s a semi-pseudo take on what I had in mind: Initialize broker Broker = new ReactiveDict; Initiate action /* click a button etc */ Broker.set('editPost', { requestedBy: 'buttonComponent', requests: 'postContent', requestTo: 'buttonComponentReturnTracker' }); Tracker.autorun(function(){…

@serkandurusoy got it. Its still a dispatcher pattern but the dispatcher holds that state instead of a passing it through. I think this will work. We wont have the ability to stop and start reactivity on the state but …we can live with that. Its seems weird to use Session and a reactive dictionary f…

Yep, that’s right. It is not very clean, but I suspect it would work for basic scenarios. About dict, yes it is essentially session with a custom name. I like it because it works like a context where var is all over the place. Reactivity can be stopped, though. Tracker’s handle does provide a non-…

@emmanuelbuah you might want to check out the following thread for a similar discussion. [image] Patterns and practices for passing data between templates help I recently read this article by @sashko about data flow from the database to the UI – it was fantast…

Inter component/template communication (architecture)

help

serkandurusoy April 14, 2015, 12:15pm 11

@emmanuelbuah you might want to check out the following thread for a similar discussion.