Hi Regs,

but this is what they already do. They look what is requested from the field and then they look what makes sence for implementing into the product.

Something like Petz or Arcade is a nice add-on but not really important for a forum.

We as coders suffer every time from VBulletins restructures. It took ages to find out what all functions do. Now with VB3 i like a lot of the new stuff but again we suffer from things like userfields which are a pain in .... to handle them correctly.

I do not think that VBulletin will spend dollars or resources on this because they have their own coders and it is their copyright on their code. This is my personal opinion. You can correct me if i am wrong.

The idea why i suggested this via this survey, was to create a common code basement for coders like us. It can be added very easy to existing VBulletins and due to a good documentation ( which has to be created from ourselves ) it should be easy to focus on the real add-ons and be more creative.

The feedback so far was not overwhelming and i just had 2 pms from users who would like to join me in that area. The others are either not interested or they want to protect their own code. This is up to them. But we 3 users VB.org will not start a project like this. Good idea but as we say in germany: "Right time at the wrong place.".

Cheers,

Unfortunately whatever people say, vBulletin is not designed (source-code wise) to expand functionality. If this were the case you'd find vBulletin would be designed around classes with each feature of vB and it's sub-features and behaviours represented by objects. It would be great to see this one day - sort of like how PHP nowadays has class libraries such as PEAR and the new template engine that i've forgot the name of :p ;)