I'm doing hopefully my last revamp of a fairly sizable project, and need
pointers on the best way of organizing includes, header
templates/procedures, and that sort of thing. Here are some details
-The heart of the matter is fairly basic ecommerce, but the products have
Vast Quantities of options/configs, so I've created a custom admin
interface
-I use smarty templates
-I've successfully made objects/methods for just about everything
Specific questions:
1. I have a class "productFetcher" -- this retrieves dB info and contains a
method showUpdateForm(). That method assigns info to smarty and calls
smarty->display($tpl). Should this just return the data and let the
operative script call smarty->display()?
2. I have an adminHeader.php which is included by all pages in the interface.
It starts the session, includes a css, and draws a set of menus for the
admin functions. Authorization is currently checked by each page, after
this header has been included. Maybe it should be checked inside this
header?
Everything works, so I don't necessarily need answers to these questions.
Just looking for resources on architecture, so that I don't go too far
down this road if there's something ugly in the design.
Thanks.
