What buttons? You mean the templates? Oh, yeah, those are in one part of the tree. Database layer in another (so that when you become famous and have to upgrade to Oracle, you don't have to rewrite your app from the ground up - just the interface layer). Oh, and that interface layer also allows for IPC, if necessary for synchronization.

Hmmm ... Logging in shouldn't be something special. If it is, that specialness should be in the Apache handler, not the place it lives.

As for modules - make modules for business objects, not developer processes. If you can't figure out what business object(s) are involved in a given feature, that means you don't understand what business purpose that feature serves, and, thus, it's a waste of time. (Worse, it'll introduce bugs into code that was fine before.)

Basically - think like a business person who can ask things to take care of business needs. Kinda like top-down decomposition, but in terms of business, not development. Then, build objects/modules to handle those business needs. Your features are now just chains of these business things working together. :-)

------
We are the carpenters and bricklayers of the Information Age.

Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

In reply to Re: Sensible Module organization for a fairly large web application by dragonchild
in thread Sensible Module organization for a fairly large web application by aristAugust

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.