This is a suggestion for using Marionette's modul system to wrap our different modules. In this case I took the MapView as an example. Some parts of the original MapView were reorganized with the goal to clearly separate between a private and a public interface of the MapView module. E.g. the view itself should have no knowledge of the surrounding Application/Communicator, this is all handled by the controller.
Also, router.js was deleted and replaced with a distinct router for the MapView module. Each module (VGV, RBV, ...) should have its own router.
MapViewController.js currently contains the Module initialization, Controller, Router and RouterController in a single file. This is just for easier review and should be changed if the pull request is accepted.
This is a suggestion for using Marionette's modul system to wrap our different modules. In this case I took the MapView as an example. Some parts of the original MapView were reorganized with the goal to clearly separate between a private and a public interface of the MapView module. E.g. the view itself should have no knowledge of the surrounding Application/Communicator, this is all handled by the controller.
Also, router.js was deleted and replaced with a distinct router for the MapView module. Each module (VGV, RBV, ...) should have its own router.
MapViewController.js currently contains the Module initialization, Controller, Router and RouterController in a single file. This is just for easier review and should be changed if the pull request is accepted.
Give it a look and tell me what you think!