tag:robotlegs.tenderapp.com,2009-10-18:/discussions/questions/2309-best-practice-for-multi-tab-applicationsRobotlegs: Discussion 2013-05-20T13:54:49Ztag:robotlegs.tenderapp.com,2009-10-18:Comment/268097912013-05-14T16:05:58Z2013-05-14T16:05:58ZBest Practice for multi-tab applications?<div><p>Hello Xlke,</p>
<p>Sorry for the delay - many members of the team are away at the
moment.</p>
<p>The solution here is to use multiple contexts. Have a look at
some modular examples/articles. Each context lives in its own
isolated scope, and a shared event dispatcher is used to
communicate between the "Shell" context and the "Module"
contexts.</p>
<p>This is much easier to do in RL2, but it looks like you're using
RL1. In that case, search the knowledgebase for information on
multiple/modular contexts.</p></div>Shaun Smithtag:robotlegs.tenderapp.com,2009-10-18:Comment/268097912013-05-19T00:23:20Z2013-05-19T00:23:22ZBest Practice for multi-tab applications?<div><p>Hey, thanks for the response. That sounds perfect- I didn't like
the idea of trying to pass the model instance or id around in an
event to differentiate. Thanks!</p></div>xIketag:robotlegs.tenderapp.com,2009-10-18:Comment/268097912013-05-20T13:39:39Z2013-05-20T13:39:39ZBest Practice for multi-tab applications?<div><p>Closing this for now, if you have any more questions, let us
know!</p></div>creynders