We were provided with the php inventory program. Then we must say whether the design template will make the program better or if it just complicates the program.
The program is structured as follows.
The program is divided into php scripts built into html. Either there is (A) one whole php page dedicated to one option, or (B) the logic of the parameters is inside another script page, which serves for other variants of a similar action. (This excludes simple buttons such as "Reset" and "Back to Home".)
(A) For example, as soon as you open a website, a navigation menu with options appears. When you click on the option, say that the Client has a “View” link. After clicking, you go to another page, which includes other links that correspond to more parameters, such as “Change” and “Delete”. Usually for this website, each option corresponds to its own php script page. For example, "View" corresponds to list_customers.php. "Edit" corresponds to edit_customer.php.
(B) Another thing is that the logic for this option is on the "generalized" page of the script. I mean, several logical options are grouped into one page. An example of this is Delete. Before deleting a client, task or quote, one is sent to a PHP page with a script called auth.php to make sure that only the administrator can delete it. The logic of checking whether its administrator registration is included in AND for deleting a client, job or quote is also in auth.php. Another example is the "Search" option for the Client. Although it has its own page, search_customer.php, the actual search logic is actually in list_customers.php. This template follows for all inquiries, including customer search, for quotes or delivery reports;the search code is actually in the corresponding _ * list. php page.
, . , , , . Factory, , , , , - , ( ) - ( , , ). , , , 2 php- .
, . ( ), ( php.)
, , , - . . ?
, - . , , . , , OO, . , PHP OO, ? OO, .
? , ?