Posted by rush on 10/21/05 22:11

"db_guy" <karl7712@yahoo.com> wrote in message
news:1129909115.120095.113810@g49g2000cwa.googlegroups.com...
> 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.

it is well known that any technology no matter how superior in theory, if
used in anger is inferior to any technology used in good will. So until you
are really confotable with OO you may be better of by not using it.

> -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).

If you have some other forms on that site, you could have AbstractForm class
describing general form handling flow, and sublcass each form on the site
from it. If you have only contact form on most of your sites, you could have
ContactForm class that you would share between your projects, by subclassing
it with sepcific for each project.

rush
--
http://www.templatetamer.com/
http://www.folderscavenger.com/

[Back to original message]