|
|
Posted by db_guy on 10/21/05 18:38
Hi,
I have been developing procedural, PHP-based apps for about 2 years
now- mostly payroll and client-management systems. Recently, however, I
have begun to research the object-oriented features available in PHP as
I felt I was "falling behind" in my programming skills, as OO is
supposed to be the future. For the life of me, however, I can not see
the value in using OO design for the type of apps I have been creating.
Here are some examples:
-Why would I need for an html form (ex: an Add Client Contact form) to
be an object when there will only be one copy of this form ever
created, on one page (ex: the Add Client Contact page).
-Why would I want each client in a list of clients to be an object,
when they are just being displayed for the user to view, or click on
for more detailed information? This is really just a database table
dump.
Can anyone shed some light on the true, real benefits of using OO
design in PHP? I really feel as though I am missing something here.
Navigation:
[Reply to this message]
|