Application/Site Design

Packetrat

Now that I've been using PHP for a while now, I'm really curious about application design techniques. I've always used a very procedural method of starting from the top and working down, just like I would any other HTML document. I like to do most of my work before I start my page, adding as little as possible in the way of embedded php tags in the HTML as possible. Often times I'll write functions to perform common tasks or even to implement template-like tasks.

What I'm asking is, is this efficient application design? What are the alternatives and how are they better/worse?

I've looked at code from projects that use a OO design where the methods are the SQL queries, etc. However, I don't understand the theory/model behind this or other methods. I was hoping for some descriptions of commonly used methods and why professionals might/might not use them.

Thanks 😃

Packetrat

Is the non-answer an indication that my methods are as good as any? Or that no one here, at PHP Builder forums, is knowledgeable about the other methods? Do I need to clarify some part of my question?

anurag2003

I also started with PHP about an year ago. In fact it's the first web scripting language that I learnt. My database driven websites usually were quick and dirty initially, but it couldn't go on and it posed some serious problems in maintainence.
Then I came to know of MVC Architecture. It's really simple MVC stands for Model-View-Controller.
The way it works is as follows.

First you setup the databases and other data sources for the application. This constitutes your app MODEL. I use mysql with SQLyog frontend for this.

Next you create an interface of your application. You need not integrate the functionality in this phase But just create the layout and the interface of the app in this phase. You can take this for the templates or the html pages for a web based application.

Finally the controller, this is the PHP scripts that spoof life into your View (step 2). You just connect the application VIEW that we created in phase 2, with the application MODEL from phase 1.

This method is really helpful for me and time saver too. As of yet I didn't experience any problems with it, but if anyone is aware of it's side effects, please let me know.

Regards

Packetrat

Okay, yes, I've read about MVC architecture in the context of Visual C++ and Java applications. So as far as that goes, I understand what you're saying. However, how do you go about doing this? In other words, where can I find examples and tutorials on implementing MVC in my PHP/MySQL applications? I'd seriously like to read up on this subject, but haven't been able to find a lick of it in the books at the library, on these or other forums, etc.

Thanks for your input.

anurag2003

I tried to find something with MVC architecture and web applications but couldn't find any good tutorials.
I might be wrong but I think I have got my facts right. MVC architecture basically separates these three things [Data], [Application Logic], and [GUI].

I'll give a fairly simple example to get you started.
Let's create a generic signup form.
First design your database with all the appropriate fields.
I would go with the following
1) First Name, Last Name
2) Postal Address
3) Email Address
4) Telephone
5) City
6) State
7) Country

Once you have designed the database your MODEL is done. Now jump on to the VIEW [GUI] of the application.
Create a form for the signup page with the above fields.

Simple enough, now the last part is to get a script in place to add the form to the database. You can make the form self submitting or in a separate script as you prefer.

That does it with a very simple MVC based app. It might conflict with the n-tier architecture but I am used to keeping things simple and as far this MVC goes, the name is self evident of it's working.

I guess this was pretty basic stuff and for people who have some knowledge of PHP/mySQL.

BuzzLY

I am a Lotus Notes developer, as well as PHP/Web. One of the things I do is map out in a rough flowchart what my application is going to do. This helps me figure out what elements will be needed (in the case of Notes: Views, Forms, Outlines, etc.)

Next I write pseudo-code. Basically, it's a rough outline of what my pages will do, but written in plain English:

Set x = 500
Loop from 1 to x
   Do some really fancy stuff here with the number, like:
   Is it a prime number?  Save it into an array...
End Loop
End Program

You get the basic idea... The cool thing is, when you are ready to write your code, whether it's ASP, PHP, or LotusScript, The English code will act as a guideline, and eventually become your comments to describe what each part of your code does. Of course, there will be changes, and nothing is perfect, but it's a good way to do things. I know a lot of developers that do this.

If you are looking for something even more structured, I would suggest you look at UML. It's an established modelling language that can be applied to any OO language. It's also a great thing to have on your resume -- employers that know anything about UML will know that you could program in almost any language if you know UML.

Here are a couple of links for more information:
Unified Modelling Language Resource Center
UML Resource Page
UML Forum

Those should get you started. You may also want to pick up a book -- try these:

Use Case Driven Object Modeling With Uml: A Practical Approach
Sams Teach Yourself UML in 24 Hours

Good Luck!

Packetrat

Re: Anurag
I'm familiar with database design and the procedural way of creating a view, but I need to know more about the control part of the plan using OO. Maybe what I already do and what you're talking about is one-in-the-same - I dunno 😕

Re: Buzzly
I don't know how you or anyone can stand UML. I took a whole class on the subject, and although I see the reasoning behind it, I haven't found anything Unified about it, nor have I found it useful in designing the real deal... it seems very much overglorified to me.