tag:robotlegs.tenderapp.com,2009-10-18:/discussions/questions/597-robotlegs-and-ui-interaction-some-questionsRobotlegs: Discussion 2018-10-18T16:35:29Ztag:robotlegs.tenderapp.com,2009-10-18:Comment/82583812011-06-29T17:25:14Z2011-06-29T17:25:14ZRobotLegs and UI interaction, some questions.<div><p>In general I let the views handle all navigation logic (unless
if there's a good reason not to) so normally I don't have a model
containing the selected tab index, but obviously that's a matter of
preference.<br>
About the signal names: I prefer to have signal names w/o the
originating UI element descriptors:<br>
NextTabRequested, ReplayRequested,
VideoEndOverlayRemovalRequested<br>
In the last one I do include a UI element descriptor since it
describes what should be removed, not where it's dispatched from
(even if it would be dispatched from VideoEndOverlay)<br>
If you do this, you'll be refactoring less, when you decide to
change UI elements, since you don't have to rename your
signals.</p></div>creynderstag:robotlegs.tenderapp.com,2009-10-18:Comment/82583812011-06-29T18:09:43Z2011-06-29T18:09:43ZRobotLegs and UI interaction, some questions.<div><p>I agree with you about the way to handle the selected tab index,
but in this case the TabBar and the "< >" buttons are two
separate views. Of course I could have put both in a unified
view…<br>
I like your "Requested" signal name suggestion!</p>
<p>If anyone wants to share his best practices, I'm interested!</p></div>Quentintag:robotlegs.tenderapp.com,2009-10-18:Comment/82583812011-07-01T10:09:38Z2011-07-01T10:09:38ZRobotLegs and UI interaction, some questions.<div><p>I have an app that is almost identical to this. Requested
signals are exactly how I do it too. Then you're coupling to the
user gesture and not to the implementation - which, in my mind, is
ideal!</p></div>Straytag:robotlegs.tenderapp.com,2009-10-18:Comment/82583812011-07-01T10:45:54Z2011-07-01T10:45:54ZRobotLegs and UI interaction, some questions.<div><p>Great, cool!<br>
Renamed my signals and felt prettier.</p>
<p>Thanks.</p></div>Quentin