App design and OOP

[G-Net]

I'm relatively new to PHP, coming from a ColdFusion background. I've been reading up on OOP, and I understand the principles of it (I think), but I'm not sure when you would want to use it (which prolly means I DON'T understand it).

Currently I just write the code in order of processing. Code I use more than once I write functions for, so I spare myself the need to re-write the same code.

So I suppose I'm still trying to understand when and why you would want to use it. 🙂 Currently my sites are pretty simple. Query data from the db and display it, along with using sessions to track members.

TIA!

[superwormy]

OOP is just another way to look at programming, theres really no good rule of thumb on when you should use it and when you shouldn't except that you should do what you're comfortable with and what you think is the best solution to the problem.

That said, one thing OOP does well FOR ME is to help group related functoins together. I have several applications which have users, and originall had several functions dealing with those users:

register_user();
check_user();
login_user();
new_user();

When I started using OOP, I grouped all of those functions together into one class, it made things a little more organized for me, AND I now use one class file in 4 different applications, with no need to change the class at all.

[G-Net]

Thanks! That helps alot. I see why it's a good idea. I just loath redoing a site I just completely converted from ColdFusion. :p

But on my next project I may use it just so I can wrap my brain around it, to learn it.

Thanks for the feedback.