OOP question

[G-Net]

I've been learning the OOP way of coding, and now can better see the benefits of doing so. Up to this point in my coding, I've always had the code and outputted HTML in the same script. I see the benefits of seperating the code from the presentation. My question is this:

What's the best way to do this? Do you build methods that display outputted data for you? Or do you leave that in the same script being called?

An example:
Say I have a forum, and you have classes that handle the db access, posting, sessions, etc. Would you build another class/method to display your various items (threads, member info, mod options, etc)?

I'm assuming so, but would really appreciate feedback from experienced OOP coders. :p

TIA!

[paulnaj]

In 'classic' OOP, you would make every section class-based. It does make scripts much easier to handle, especially larger projects.

On the downside of OOP, there is definitely more work for the server.

But, remember, OOP is really for the programmer and doesn't have any direct benefits for the user. So, in the end, it's a decision for the individual scripter.

Hope that helps (a bit)!

[G-Net]

Thanks!

I find myself always reusing sections of code (db access, processing, etc), so I see the benefits of building classes to handle such. I'm not thrilled of putting more load on the server, but appreciate less load on myself. :p

[planetsim]

Well PHP5 when comes out and is widely used will have more benefits with OOP, not sure if the there will be a difference in speed though.