Any tips/thoughts on separation of view from controller/model (MVC concept) with composer. That is composer seems a little view centrix as you move from page to page. How about:
-
keep all View items in the composer scene files
-
in the scene “create” create/instantiate a “controller” for that scene/page (might be a lot of logic/state tracking etc in a game)
-
for UI events pass to controller via dispatching events
-
for controller outcomes that imply UI update pass to controller via dispatching events
Comments? Overkill re using events? Goal I guess is trying to make the code files more readable/less large, so splitting out logic from UI I thought (via MVC) might be one good way.