tag:robotlegs.tenderapp.com,2009-10-18:/discussions/questions/527-views-mediators-modelsRobotlegs: Discussion 2018-10-18T16:35:26Ztag:robotlegs.tenderapp.com,2009-10-18:Comment/70368822011-05-06T14:17:21Z2011-05-06T14:17:22ZViews, Mediators & Models<div><p>And if I'm wrong,<br>
The media.Player is a standalone component, maybe it's not a View
part...<br>
Maybe the media.Player should be create and manage by the
PlayerModel ?</p></div>Armetiztag:robotlegs.tenderapp.com,2009-10-18:Comment/70368822011-05-11T08:36:48Z2011-05-11T08:36:48ZViews, Mediators & Models<div><p>Hi there,</p>
<p>sorry for the delay - was hoping someone more video-based would
reply!</p>
<p>I think my approach would be to use a PlayerModelProxy to wrap
the info about the state of the player. Your Robotlegs Commands
would access this, and it would dispatch events and so on, and it
would have access to the API of the videoPlayer's state model.</p>
<p>But... I'm not sure what your existing component exposes.
Perhaps your component itself should be dispatching the events?</p>
<p>Sorry not to be more helpful - I'm not really clear enough about
how / what you're doing.</p>
<p>Stray</p></div>Straytag:robotlegs.tenderapp.com,2009-10-18:Comment/70368822011-05-11T09:57:05Z2011-05-11T09:57:06ZViews, Mediators & Models<div><p>Thanks for your anwser.</p>
<p>The media.Player dispatch many events to advice is activity.<br>
Now, this is PlayerModel that manage media.Player instance
directly. PlayerModel is like a Proxy.</p>
<p>I have to work more with RL, the more I work the more I
understand.</p></div>Armetiz