tag:robotlegs.tenderapp.com,2009-10-18:/discussions/problems/280-mdi-best-practicesRobotlegs: Discussion 2018-10-18T16:35:24Ztag:robotlegs.tenderapp.com,2009-10-18:Comment/61644302011-03-22T15:29:40Z2011-03-22T15:29:40ZMDI best practices<div><p>Just checking - MDI as in Multiple Document Interface?</p>
<p>Is this an air app - will there be genuinely separate windows?
Or are your views pseudo-windows?</p>
<p>Other than the few workarounds required with truely separate
windows (search around the forum for lots of good threads around
that) I can't think that it's any different to how I would do
normal Robotlegs.</p>
<p>The only extra option would be to treat each Document Window as
a newly spawned Module, with its own context. That might simplify
things a fair bit inside each individual module, with the trade-off
of the extra load of doing a modular app.</p>
<p>I have a multi-screen app which our clients use for editing
complex data. I treat each editing screen as a separate module -
and it works nicely.</p>
<p>Hope that helps,</p>
<p>Stray</p></div>Straytag:robotlegs.tenderapp.com,2009-10-18:Comment/61644302011-03-22T16:02:54Z2011-03-22T16:02:56ZMDI best practices<div><p>"MDI as in Multiple Document Interface?"</p>
<p>yes, that MDI.</p>
<p>"Or are your views pseudo-windows?"</p>
<p>Yes, pseudo windows in a flex app.</p>
<p>"The only extra option would be to treat each Document Window as
a newly spawned Module, with its own context. That might simplify
things a fair bit inside each individual module, with the trade-off
of the extra load of doing a modular app."</p>
<p>Ah, yea, i kept forgetting that i can have multiple
contexts.<br>
That's a good idea. Thanks man.</p></div>Anggie Bratadinata