I need a guideline!

Anon

Hi,

I need to develop a web based manual for a corporative intranet.

After thorougly browsing the paper version of the manual, I concluded that each main topic will have a maximum of 4 threads or branches (each level or branch can hold a variable amount of sub-items).

The question is, if OOP would be the best way to cope with this? For example creating objects and implementing methods to create; drop or mofify branches.

I know nothing about OOP; but if statements are strong enough; I will learn how to do OOP.

Thanx in advance.

toma42

NO. Use docbook. It's a steep learning curve but once you overcome it you will thank me.

nashirak

The point of programing in styles such as OOP is to make the code easy to completely, efficient, easily readable, and easy to modify. OOP does this through being very modular. So on big projects its great. You can say I will have this class that does such and such, and not have to worry about (yet) how to implement this. Now... this being said, I know of people that would say always use OOP. I kinda dont like that necessarily. If you have a small project, just use an simple straight through approach (I forget the technical term for it). So all that being said you need to decide, is this a simple project and would be better suited without OOP, or does is this project going to require something bigger where I need to use the OOP approach. From the sounds of it (this is just my humble opinion) a OOP approach would be good.
Hope this Helps!

Anon

This project is a mid-range one I would say at first, but I want to decide my steps before to start; so I think OOP might be a good choice as you say

thanx

Anon

I'd suggest looking at a few OOP examples and seeing if they make sense to you. Chapter 9 of Professional PHP Programming (Wrox) is a good intro. Just spend a few hours researching. If it makes your head spin, or you find yourself saying "Why not do it... some other way?" probably skip OOP and do it in a way you're more comfortable with. If you start thinking things like "This is exacltly what I need" and "Why didn't I think of that?" Then go ahead and go with OOP.

djresonance

I believe the technical term is 'KISS' (keep it simple, stupid) 🙂

If you have a small project, just use an > mple straight through approach (I forget
the technical term for it). So all that

nashirak

Its actually called Procedural Programing... (just remembered it)... if you were really ambitious you could do Genetic Programing. 🙂 So the choices to date are:

Procedural
Object Oriented
Genetic Programing (just in case you dont beleive me http://www2.informatik.uni-erlangen.de/~jacob/Evolvica/GP/Java/html/)

🙂

Anon

jajjajajajajajaja

Anon

I do believe !!! Indeed this world is amazing!!!!!!!!!
I was pondering the virtues of OOP;
and now I ended up knowing it´s basics, but ... genetic Programing turned my brains upside down

:-)