Which mvp directory organisation do you prefer, why?
The illustration I give here are general may not bear close resemblance to the brand of mvp of your preference - but I think you would comprehend what I am attempting to illustrate.
 
I see most examples and programmers organise their directories this way

- event (bus or controller)
- presenter
  - space1presenter
  - space2presenter
  - space3presenter
- view
  - space1view
  - space2view
  - space3view
- misc
  - space1misc 
  - space2misc
  - space3misc


However, I prefer to organise it this way:

- event (bus or controller)
- space1
  - space1presenter
  - space1view
  - space1misc 
- space2
  - space2presenter
  - space2view
  - space2misc 
- space3
  - space3presenter
  - space3view
  - space3misc 

The reason is that I hate looking all over back and forth for all the files of the same space. I also find it easy to introduce a new place/space within the mvp state-machine by simply swapping in a single directory tree. And I can debug that individual space/place by itself independent of the other spaces by simulating/testing various stimulus and exercising it with an alternate state-machine, just by copying that directory into another project/module. In that way, my alternate state-machine will not contaminate or be contaminated by the other spaces/places. 

I know that people say that, well, what if you wish to represent the presentation with another view? Like

- event (bus or controller)
- presenter
  - space1presenter
  - space2presenter
  - space3presenter

browser

- view
  - space1view
  - space2view
  - space3view
- misc
  - space1misc 
  - space2misc
  - space3misc

mobile

- view
  - space1view
  - space2view
  - space3view
- misc
  - space1misc 
  - space2misc
  - space3misc


Then, this is what I'd rather prefer: 

- space1
  - space1mobileview
  - space1mobilemisc 
- space2
  - space2mobileview
  - space2mobilemisc 
- space3
  - space3mobileview
  - space3mobilemisc 

In fact, some times the event controller is totally different on the mobile device than it is on the browser. Or on the touch screen.

So, why bother making life difficult by splitting/dividing up the classes of a space across the whole project and frequently I get lost navigating someone else's code, as we often have to divide our programming tasks and integrate into each other's mvp?      

I think to some people, mvp directory organisaation sounds trivial and non-issue, but it gets pretty frustrating when working with a large project, in spite of ctrl-shift-T.

Tell me why - so many programmers prefer splitting/splatting the code of each space across the whole project? What is the advantage under what circumstances ? 
Which mvp directory organisation do you prefer, why?
===

The illustration I give here are general may not bear close resemblance to the brand of mvp of your preference - but I think you would comprehend what I am attempting to illustrate.
 
I see most examples and programmers organise their directories this way

- event (bus or controller)
- presenter
  - space1presenter
  - space2presenter
  - space3presenter
- view
  - space1view
  - space2view
  - space3view
- misc
  - space1misc 
  - space2misc
  - space3misc


However, I prefer to organise it this way:

- event (bus or controller)
- space1
  - space1presenter
  - space1view
  - space1misc 
- space2
  - space2presenter
  - space2view
  - space2misc 
- space3
  - space3presenter
  - space3view
  - space3misc 

The reason is that I hate looking all over back and forth for all the files of the same space. I also find it easy to introduce a new place/space within the mvp state-machine by simply swapping in a single directory tree. And I can debug that individual space/place by itself independent of the other spaces by simulating/testing various stimulus and exercising it with an alternate state-machine, just by copying that directory into another project/module. In that way, my alternate state-machine will not contaminate or be contaminated by the other spaces/places. 

I know that people say that, well, what if you wish to represent the presentation with another view? Like

- event (bus or controller)
- presenter
  - space1presenter
  - space2presenter
  - space3presenter

browser

- view
  - space1view
  - space2view
  - space3view
- misc
  - space1misc 
  - space2misc
  - space3misc

mobile

- view
  - space1view
  - space2view
  - space3view
- misc
  - space1misc 
  - space2misc
  - space3misc


Then, this is what I'd rather prefer: 

- space1
  - space1mobileview
  - space1mobilemisc 
- space2
  - space2mobileview
  - space2mobilemisc 
- space3
  - space3mobileview
  - space3mobilemisc 

In fact, some times the event controller is totally different on the mobile device than it is on the browser. Or on the touch screen.

So, why bother making life difficult by splitting/dividing up the classes of a space across the whole project and frequently I get lost navigating someone else's code, as we often have to divide our programming tasks and integrate into each other's mvp?      

I think to some people, mvp directory organisaation sounds trivial and non-issue, but it gets pretty frustrating when working with a large project, in spite of ctrl-shift-T.

Tell me why - so many programmers prefer splitting/splatting the code of each space across the whole project? What is the advantage under what circumstances ? 