tag:robotlegs.tenderapp.com,2009-10-18:/discussions/questions/8354-settings-and-game-state-manager-best-practiceRobotlegs: Discussion 2014-09-01T12:32:03Ztag:robotlegs.tenderapp.com,2009-10-18:Comment/336036702014-07-01T03:11:08Z2014-07-01T13:04:32ZSettings and Game State Manager - best practice<div><p>I have not worked with movile devices before, but I think that
if you need<br>
to access some external resource, eg. to get the current language,
you<br>
shoud do it through a Service with a Command, and store the value
in a<br>
Model. Then, access the model from the mediator, never from the
view<br>
because views are not injected (by default). Best practices say
that<br>
mediators should not know about models and services because of
the<br>
coupling, but they also say that you can access them from
mediators<br>
through their interfaces without serious coupling risks.</p>
<p>You can also have two or more global application states, one for
each part<br>
(language, volume, etc.). Also, if aspect ratio or any other
setting is a static variable aviable in the SDK, then you already
have a "Singleton"<br>
which can be used also in views without injection or events.</p>
<p>El Lun, 30 de Junio de 2014, 5:30 pm, anshumang001
escribió:</p></div>greenLED