title: Using Durandal how can you use multiple viewmodel files with a single view in order to break up a large file?
body: <p>I have an application that utilizes a Google Map in one of its views.  This is a SPA that uses Durandal's view/viewmodel file structure using convention.  The problem I am trying to solve is that the functional modes that share the map view (google map) are quite diverse.  As examples the application needs to show the current locations of vehicles on the map, be able to show historical information (paths) for vehicles, and allow the creation, editing, and deletion of Geofences.  Each mode of using the map requires that some UX controls be hidden and others be made visible. </p>
  
  <p>I believe that when all the viewmodel logic code is in place for the above, the viewmodel will grow quite large and therefore hard to maintain and code.  I am trying to avoid having a huge viewmodel file with logic for all of these UX controls.  </p>
  
  <p>Conceptually I would like to have multiple viewmodel files working seamlessly with a single view file so I don't have to repeat the google map in multiple views.  Also, I would like to maintain the easy/automatic binding using Knockout if possible.  What are some solutions using Durandal to break up a large viewmodel file while maintaining a single view file?  Is this possible or even desirable?  </p>