vBulletin Guru's Knowledge

[Mr Pink]

As far I know vBulletin world, I've understand that for become a good (tecnically) coder, a good vB Guru, you need to know these languages (and not) [I also attach links to W3S tutorials]:

• HTML

• XHTML

• CSS

• XML

• PHP

• SQL

• AJAX

• JavaScript [not essentially required]

I'm posting this becose I want know if mine is a mistake, and also for receive suggestions and help for complete this list! So, post and let me know, vB.org's people!

[Marco van Herwaarden]

I have been doing fine (i think) with only PHP & SQL knowledge and a good bit of common sense.

[Mr Pink]

Originally Posted by Marco van Herwaarden

I have been doing fine (i think) with only PHP & SQL knowledge and a good bit of common sense.

But, for example, if you want develope your own hack, you need to know XML, for your files..
I don't know XML, but I've seen that it is used in alot of vB files.

[Marco van Herwaarden]

All (most) XML that is needed to write a modification is generated for you. No XML knowledge needed at all.

And the most common use for handwritten XML is the cpnav and bitfield xml-files, and those are very simple files that you can easily create by copying and editing an existing file without XML knowledge.

[Mr Pink]

Thanks for your replies, Marco.

Originally Posted by Marco van Herwaarden

All (most) XML that is needed to write a modification is generated for you. No XML knowledge needed at all.

What you mean with "is generated for you"?

the XML you find for templates, products, plugins, are generated by vBulletin itself when you export the tools you create... we, coders, never have to touch them really.

as i can tell by being a guru for a lot of useless things, i can tell you that when you are not into design, you need to know PHP with some OO twist, and MySQL when you explore database extractions... otherwise, PHP itself is enough...

i'm into design too, so i had to learn and apply a lot of XHTML/CSS2/3 before calling myself a cool designer...

and i find AJAX/Javascript very obscur...

[Mr Pink]

Originally Posted by nexialys

the XML you find for templates, products, plugins, are generated by vBulletin itself when you export the tools you create... we, coders, never have to touch them really.

Oh, ok. Thanks for reply!

i'm into design too, so i had to learn and apply a lot of XHTML/CSS2/3 before calling myself a cool designer...

Yes, but I think you should know CSS, anyway, becouse is the image-late of the project.. and without that, you can be the best coder, but if your site come without a simple scheme, a simple image-late.. it's bad to see!

and i find AJAX/Javascript very obscur...

Explain "obscur", please! Lol.

obscur, like dark, unknown... ya know, Darth Vader... the obscur side of the force!

[Mr Pink]

Yes, I know what obscure in english means.. but.. why AJAX and JavaScript are 'obscure'!?

[Zachariah]

Originally Posted by nexialys

the XML you find for templates, products, plugins, are generated by vBulletin itself when you export the tools you create... we, coders, never have to touch them really.

I have found I can make changes on large scale in the XML outputs vs. edit each template, phrase, plugin, admin help, install/uninstall code within vBulletin AdminCP. (search and replace)

I also use Araxis Merge on XML's for quick view of changed data and migrations.
It's also easy to add phrases, plugins, templates, ect ... within the XML plugin/product.

I split screen SQL dump, PHP , XML product all the time.