Code: Select all
include/classes/access-control/
database/
html-formatters/
phrasebook/
storeable-objects/Now I'm having an explosion of little classes that implement a given pattern, so I've been adding directories for "contexts","requests","controllers","handlers", etc. These are likely to have a large number of classes, 20+ each, easily.
In addition there's a clustering effect. Almost every handler has its own request. Contexts are almost similarly customized, though there is a litle more sharing, etc.
I'm a little tempted to re-orient the tree around functional areas, Each functional sub-directory would have its own controller with its associated contexts/requests/handlers. The few universally applicable/base-class can live in a "shared" or similar named directory. Any thoughts?