|
|
Posted by NC on 10/24/05 23:40
steve wrote:
> "NC" <nc@iname.com> wrote in message
> news:1130175442.823069.267960@z14g2000cwz.googlegroups.com...
> | rush wrote:
> | >
> | > > -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.
> |
> | Or you could have a single function that would do absolutely the same
> | thing with less overhead...
>
> that depends nc.
Of course. The OP's question, however, was, "Why would _I_ need OOP?"
And the answer to that is very simple: if the OP doesn't see how OOP
benefits his development process, there's a good chance it actually
doesn't.
> generally though, with sufficient complexity, it is easier
> to manage the specifics of validation and presentation in
> the manner he described...
It's quite possible. But there will be a cost to that; the OOP will
have to rewrite his base of reusable code (assuming he has one) from
scratch. So, again, the OP is the only person who has information
sufficient to conclude that OOP is (or is not) beneficial to his
development process.
Cheers,
NC
Navigation:
[Reply to this message]
|