Nic,
The per-page model makes it clear what belongs to a particular page (model and view, but also XForms model, actions, and possibly other per-page dependencies), and also has the benefit of keeping the number of files in a particular directory small. Organizing your files per functionality, you end up with a small number of directories, but a large number of files in each directory. For this reason, I personally favor the per-page organization.
As you point out, this is really a question of personal preference. I don't see any problem choosing a different layout.
-Erik
Nicholas Hemley wrote:
Hello,
I was just wondering why the actual underlying folder structure for the Bizdoc example has adopted a per-page structure rather than a MVC-oriented structure i.e. keeping all models in one folder, keeping all views in another folder (rather than mixing all source files together according to application 'pages')
I guess this is a question of personal preference, but are there any gotchas for me to be aware of for why one has been chosen over another? My own personal preference would be to keep all models separate from views since I come from a Java package background, which seems sensible to group source according to function and not according to application 'pages'.
Any other opinions/pointers?
Cheerio, Nic.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
orbeon-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/orbeon-user
