OOP + vB
 

Without pointing to a tutorial or an article anywhere could someone please, atleast try and explain what Object Orientated Programming is? how and why it's gonna be a part of vBulletin? and what are it's benefits over the current methods of programming (procedural)? please, if it's not too much trouble.

examples of OOP are more than welcome, but if you're gonna do something like "hello world" please don't as it don't really help me in how i'm trying to grasp it.

oop basically creates an organized structure through classes allowing multiple instances of the same class without having to write code multiple times. the benefits besides more organization is beyond me. an example is the $DB_site class which uses some oop;)

It's a more semantec method of developing code than functional code. It's also far more modular and pluggable.

Heres a tutorial made by Zero Tolerance:

http://gzevolution.net/?type=page&id...tutorial&tut=9

Just have a look at ImpEx, this has a lot of OOP coding in it.

It just seems to be a long winded way to achieve the same thing. Functions have always existed - where is the advantage ?

Properties and Functions are a part of OOP. The advantages are far too numerous to put down - but in a nutshell it allows other coders (ie mod/hack writers) to not worry about how a particular function works, or where it is located - they just call a particular function and get what they need.

Say for instance there was a mammouth object called vB and you wanted to get a particular users name, you could do something like vb.users(51).username;
(yes, that isnt php... more like vB... but easier to read IMO ;) ).

Anyhoo... you wouldnt have to worry about a particular query, where the table is, worry about table prefixes, etc... More importantly, you wouldnt have to worry about future changes affecting how you usually get a username as it would all be black boxed.

Thats my 3.8 cents (?.02 at current exchange rate).

yes it is the same but just a longer way of doing things. it is really only a coding style which allows a program to be easily extended upon because every is a class which can be changed and not have to be changed over several files.

Also doesnt it make programs easier to be designed by mutiple people instead of one person.

yes because its a written standard. so basically as hacks are designed in oop in the future it will become easier for others to port, upgrade, or change. as there will be no need as to "wait what is he doing?"