The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
![]()
okay, cyberfolks--
i'm not a coder (and don't think I wanna be one)--I'm a page designer. I know javascript, not PHP. When I hear people talking about OOP, I think object models and elements and properties... is that what's happening? Will I, when modifying templates, be able to use things like forum.thread.message.parent.poster? I know that the Hooks and plugins are very exciting for developers, but what kind of impact should the UI guys expect--little, none? --don |
#2
|
|||
|
|||
![]() Quote:
--don |
#3
|
|||
|
|||
![]()
Not 100% sure, but i think that there are no significant changes to the template system.
|
#4
|
|||
|
|||
![]()
Unfortunatly the OOP of javascript you're talking about is not the OOP that vbulletin is using or leveraging.
Expect very little difference except variables you use change from $vboptions[blah] to $vbulletin->blah (from memory). |
#5
|
|||
|
|||
![]()
The OOP begin discussed currently are the changes to the php source code. Coding in the templates will not change much, save a few changes in the way you access things (re-named vars/arrays etc.)
|
#6
|
|||
|
|||
![]() Quote:
--don |
#7
|
|||
|
|||
![]() Quote:
|
![]() |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|