17 replies to this topic

[Coldhearth]

Hi there,

I've always created normal HTML/CSS websites and since I started using PHP for some simple stuff like guestbooks/news scripts/login script etc...
I have decided I would like to write (first a simple) backend system that I would just have to implement in future site I create so that my clients could customize their site through my own system.

The problem is that people say (and google) says almost all the time that it's best to use a framework build with de MVC pattern.

I think writing this MVC framework is a bit to difficult for my level of PHP writing at this time.

Can someone help me with this? Should I just learn an existing framework to build my backend on or what should I do?

[John]

Are you familiar with object oriented programming?

[Coldhearth]

I know some Java yes :) but I'm certainly no expert that's for sure...

[John]

Before I started building my backend/cms I took the time to garner a solid understanding OOP, how it works with PHP, and several design patterns including the MVC. That said, I would recommend taking the time to advance to this level as it will save you time in the long run.

I would venture to say it is near impossible to create a procedural backend that will have seamless integration with your future websites. You will most likely resort to recreating the entire backend each new site you implement. With good OOP practice and an MVC design, this is not an issue.

[Coldhearth]

Okay :) so can you give me any good resources or books that you used for example to learn about these subjects...? That would be realy helpfull :)

So maybe it's better to start designing stuff like a normal news script but in the OOP way of PHP rather than the procedural way? And by doing this learning the OOP of PHP and advancing to a higher level of understanding before building a backend/CMS

[WingedPanther]

One way to get a better understanding of OOP is to find aspects of web design that you would like to use without seeing the ugly details every time. For example, in ASP, text form submissions, binary form submissions, and address-bar parameters are accessed in three completely different ways. Creating an OOP wrapper for that (obviously a different situation, but a good example) is a nice way to improve your understanding of OOP AND make your life easier.

I'd give more examples in PHP, but I don't know it that well myself.

[Coldhearth]

Okay thx I'll look those up and also try to look for some OOP based PHP scripts on the internet to get a better view on this.

I already know some OOP but the problem I keep having is that I know my theory but when I have to start a project lets say something simple as a guestbook, I never know how to start, wish classes to use etc...
I think that's one of my biggest problems... and I don't realy know how to get rid of this (I have read a lot about OOP but to do something like that myself from the beginning keeps bothering me... :( )

[WingedPanther]

One of the other problems most books on OOP have is they tend to get you thinking you need OOP for EVERYTHING! The reality tends to be very different. I use a mixture of OOP and procedural programming. I use OOP to encapsulate certain things in a handy package. Some things are specific to what you're doing and no amount of OOP will make your code reusable.

[Coldhearth]

Hmz I guess I'll need to practice a lot... I would realy want to learn this because I want to start writing my own framework and CMS... this is my goal... Hope I can achieve it :)