vb3.5 News
 

<a href="http://www.vbulletin.com/forum/showthread.php?p=863307#post863307" target="_blank">http://www.vbulletin.com/forum/showt...307#post863307</a>

more hack orientated it seems, new features, plus more, read what kier said.

++++ING AMAZING !

WOW, even quicker than vb2 to vb3.

I love all updates but this is the best
If you are using Gmail you'll know what this is, an extremely superb feature.

darn this is so crazy.

Yeah...looks awesome. How hard will it be for you coders to port over hacks into the module like system assuming that for the most part the general coding stays the same...

And if that sentence sounds like I don't know what I'm talking about...I don't. :p

i wouldn't expect any of the larger hacks till around a month after release, though you'll get a few from a week - a fortnight later, rebuilt code will take a tad longer, all in all you can get any 3.0 hack working given an hour or two.

Expect to see the vBmarket explode with add-on's btw, you'll begin seeing stuff like blogs, cms, hot or not scripts, link dirs and any other thing someone can think of and hope to make money from being released :)

I really wouldn't get overexcited by the idea of the plugin system. I think it'll just be an external class which allows you to point to included files.

what do you mean, couldn't you just, nevermind you mean the other way round, i know we won't have to edit admincp/index.php anymore as well as fucntions/adminfunctions_template.php, i dunno what the real hope is for in the new system, though the new store hack will be quite delicious in it's implementation, plug and play store hack is droolworthy.

The point is we won't know what is required until the source is dropped on us. The beta peroid will give us some time to play with it but I doubt you will see anything big from hackers until 3.5 goes 'gold'.

There are other things that will help right away, the biggest begin phpdoc source. Data API's will allow easier intergartion, so you might start seeing portals (or CMS systems) (or other large scripts) that don't even need to hack the source.

The biggest problem with hooks is that someone around here is bound to need one where one does not exist. You might see common 'hook hacks' to place a hook into a certain part of the source so other larger projects can use them.

3.5 is going to change how we define 'hacks', the old ways are going out the door and we are going to have to figure out a new bag of tricks :). It's welcomed change, but its going to take getting used to, I can't wait to get my hands on the beta so I can start reading the source code.

Hmm... let's see the globalize() function is gone so all that needs to be changed, the options are in a "vBulletin" class and no longer accessed via a simple array. Database functions have changed and all calls to the database class are handled differently. I think most Data is handled via classes. There is an optional MySQL interface that might need to be accounted for depending on your queries. I am sure there is more. Most hacks can probably work with minor modifications, unless you rely heavily on existing vBulletin functions.

As Kier said months ago, read up on Object Oriented Programming in PHP. It is what you will need for the future.

Yeah, this is also pretty much what I feel is going to happen. I guess I'll have to delay any 3.5 upgrade plans until it's clearer how the current hacks will (or won't) be ported/integrated into 3.5.

I don't think it will be a simple matter of changing a few snippits of code to get the existing hacks to play nice on vb 3.5 - sure that cand probably will happen in some cases, but I think there is alot of potential to be had with intergrating things like AJAX into existing hacks and that could take time to code.