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.

If I have time, I'll give you a head start on porting existing hacks without using the plugin system.

.. and about the plugin system, we will add hooks to other places, you'll just need to ask.

without seeing the code, it will be hard to determine

i already fear upgrading all the vb.org used hacks ^^

There are some hack writrs who are not supporting their hack anymore but we are using their hacks. For example vb3arcade or some hacks the writer doesn't even visit vb.org at all. What will happen to these hacks ? How can we port these hacks to vb3.5 ?

Like i mentioned on vbulletin.com, I sure hope documentation is up to speed with vb's developments, not just for the forum administrator, but for developers as well. :)

You will have to port them yourself, or someone will have to port them for you, no one can re-release these hacks without permission from the author (however they can code their own and release it).

We have not seen the source yet, so we don't know how to port hacks yet, but at this time it looks like 3.5 will break all current hacks.

Well its at least something to look forward to playing with - Already vB3.0.x has gotten most of the good hacks already released, so its going to be a level playing field for hacks again with 3.5 ;)

Satan

that's enough, I love to code in OOP. Vb 3.5 is OOP then hack will be coded easier.

Can't wait to see the code.

Also everybody will still be unnecessarily editing the code, just like they do now when 90% of the stuff can be done without touching the PHP.

i have to recode my portal and new system now:( thank god i didnt code my directory yet. i wont bother upgrading vbjournal though since ill code for the plugin system in the 2nd version>_>

Damn, and I spent weeks getting my RPG to use globalize() and $vboptions XD
Bwaha nah I already knew this.
If your still taking suggestions for hook locations, (if you haven't already) please make the hook system able to plug in to important queries such as $posts for showthread.
Im aiming to make my hack(s) as optimised as possible, and this includes plugging into existing queries instead of making my own (where possible), so having the ability to plug into such queries would be a tremendous help :)
You can rest assured that as soon as you release the beta, I will look over where I need to plug in code and so help me God, if as much as one single placement is missing, I will be all over your asses faster than you can say "vB" ;)

Yeah I like that idea actually Revan :)

This would probably be better handled by the Data Managers. That is what they are there for. Hooks are places where you can call your own custom code from within vBulletin without actually modifying the vBulletin Code. Different technologies for different purposes.

Are there any parts of vB3.5 that haven't been rewritten?

The templates to some extent, but even they have some changes. :)

Oh. I don't really know what the Data Managers are, maybe I skipped that part of the vBcom post.
Call it hooks, Data Managers or Cookie Crumbs for all I care, as long as it works ;)

i hate OOP!!!
*dusts off the php book*

The announcement makes it seem like data managers are used for saving data, not querying for data.

I don't know much about it, but what I have seen of it so far looked quite confusing. The word "This" seemed very popular ......

The description of 3.5.0 looks nice, but sounds like virtually all hacks will have to be re-done for this new version and it's "Hooks & Plugins".

I also don't quite understand the theory of these. It sounds like they will allow you to "insert" code at various points, but many hacks don't just insert code, they actually change existing code, so how will this work ?

thats why im depressed cause i have to recode all my custom mods:(

Right... well it should help ALOT overall less edits mean happier users.But, you won't have to again for sometime, as long as you make some use of the plugins system.

Think about it, much less rehacking, no more inserting custom templates every upgrade...

This means: right here, for this ^^.

OOP is cool, someone can hate it but after playing with it for sometimes he will be in love.

This change is once and for all, newer version after 3.5 hack won't need to be rewritten.

I say we form a rebellelion! We all stay with 3.0.1-3.0.7!!!! Who's with me?!?!
...

Anyone???

Fooey! Time to learn OOP.. :(

OOP is great. OOP in PHP sucks given it's not an OO language, including PHP 5. It's great in something like Java which is strongly typed and not an interpreted behemoth like PHP.

But, few hosts support JSP, so that's what everybody uses.

That's not to say I disapprove of OOP support in vB 3.5. Every non-useless language today has OOP support, and the good ones are built around that model.

Exciting news. :)

Once this comes out I'll have the world's biggest headache since my site is one of the most modified ones around.

$this inside of a class refers to itself.

Wow, that's some great news. I'm really impressed with what they plan to do hacks. Upgrading would be an absolute breeze, it sounds too good.

Plus the template comparing thing is also quite impressive. Really happy that's been introduced. :)

Can't wait to see the beta and that.

The idea is to reduce the number of file edits you have to make, but there will always be cases where you have to edit the file regardless of hooks or not ;)

Satan

yeah but i know in the long run its better but now im summer is blown because first i have to learn oop then i have to learn the plug-in system and then i have to code. drrr.

Think of it as a challenge ;):p

Satan

WICKED COOL!

But I guess many old hack don't work then..

I do like Inline Moderation and AJAX!