tag:robotlegs.tenderapp.com,2009-10-18:/discussions/questions/120-is-robotlegs-overkill-for-what-im-doingRobotlegs: Discussion 2013-04-28T10:29:13Ztag:robotlegs.tenderapp.com,2009-10-18:Comment/14106572010-04-09T15:06:48Z2010-04-09T15:06:48ZIs Robotlegs overkill for what I'm doing?<div><p>It does help to define what "areas" are self-contained
components. This part might make sense to that - so it controls its
own parts. So, think about the API that this component would
need:</p>
<p>addLayer<br>
removeLayer</p>
<p>and some event/signal when you rearrange layers.</p>
<p>everything else can be handled by the component itself...</p>
<p>This makes sense regardless of the framework/work flow.
Partition the work into self-contained chunks. Think about the
public API and events that chunk needs to talk to and respond to
the rest of the app.</p>
<p>good luck!<br>
jos</p></div>Jos Yuletag:robotlegs.tenderapp.com,2009-10-18:Comment/14106572010-04-09T15:28:17Z2010-04-09T15:28:17ZIs Robotlegs overkill for what I'm doing?<div><p>the DragAreaUpdated signal could trigger a command and/or be
received by the LayerMediators to updated them directly. It isn't
strictly necessary to hold this value in a model and might be
clearer if the mediators within this component structure just speak
directly.</p></div>Joel Hooks