title: Correct folder structure for extjs MVC
body: <p>I would like to know the most correct best practice in laying out a folder structure for a MVC application in Extjs (specifically 4.x).</p>
  
  <p>There are many examples scattered around, but there seems to be no general consensus.</p>
  
  <p>In general I have seen a lot of examples that are structured like this :</p>
  
  <p><a href="http://www.slideshare.net/senchainc/structuring-your-sencha-touch-application" rel="nofollow">http://www.slideshare.net/senchainc/structuring-your-sencha-touch-application</a></p>
  
  <p><a href="https://i.stack.imgur.com/dGt2o.png" rel="nofollow"><img src="https://i.stack.imgur.com/dGt2o.png" alt="enter image description here"></a></p>
  
  <p>This approach somewhat horrifies me, as having the same file name for a view, controller, model, store etc.. (instead of AccountMode, AccountController, AccountView) can only lead to confusion. I am currently in a project that uses this methodology and it really stinks. My productivity has gone down because it is not easy for me to navigate through the code if everything has the same name. I spend 5 minutes staring at an 'Account' file, only to realise that I was staring at the wrong 'Account' file.</p>
  
  <p>Secondly, having done MVC for over 10 years, I have always held my View and Controller close together. If the View and Controller have a 1 to 1 relationship then they would always live together in the same folder. This is a more OO approach as there is less inter-package (ie folder ) dependency. Folders should have strong inter-dependencies between classes inside them, but weak inter-dependencies to classes in other folders. </p>
  
  <p>Is there a best practice out there for extjs folder structures using MVC?</p>