Well, if its *easier* to make modifications, then one could at least hope that the hacks for 3.5.0 would begin pouring out at a much faster pace, I would think.
I didn't say your hypothesis was wrong. I am saying that it *isn't* warranted to make any claim in the positive OR negative until there is some kind of survey.
I then followed up by showing what my own personal bias leans towards. I did not extend my bias to the majority with speculation about who would and would not switch. All my statement about my own position shows is that at least one person will be switching.
I believe most upgrade happy people probably will upgrade. What will matter is if the coders will. Object oriented programming is easier to code on a large-scale project but in the realm of an individual coder its more time consuming and adds complexity to a previously simplistic environment.
My opinion as a consumer was warranted the day the release was detailed from vbulletin pertaining to a product that I may or may not utilize.
Well, if its *easier* to make modifications, then one could at least hope that the hacks for 3.5.0 would begin pouring out at a much faster pace, I would think.
Nobody said it would be easier to create hacks. It will only be easier to implement and administer hacks that are using the plugin hooks and the Data Manager.
Nobody said it would be easier to create hacks. It will only be easier to implement and administer hacks that are using the plugin hooks and the Data Manager.
I agree that it won't take any less skill to design robust modifications. But I think it probably *will* be somewhat easier to create the modifications for the hack makers because they'll have clearly defined access points to start from.
Coding against a well doc'd API is always easier to work with than trying to modify source code directly.
Of course, the trade-off is - you're limited to what the API lets you have access to if you stick to only the API.
I agree that it won't take any less skill to design robust modifications. But I think it probably *will* be somewhat easier to create the modifications for the hack makers because they'll have clearly defined access points to start from.
Coding against a well doc'd API is always easier to work with than trying to modify source code directly.
Of course, the trade-off is - you're limited to what the API lets you have access to if you stick to only the API.
The bottom line is that its changing the code structure and adding more rules to the way it can be inserted to comply with the plug in system.
Right now its coding into whatever however within ethical range defined by the community of vbulletin.
I seen how they were double clicking on the box to edit the title. I have some java code installed that gives me the ability to click anywhere on the box to open a forum or thread. I guess that will be gone.
Personally i look forward to the new upgrade with the new plugin system, after all remember when vb brought out 2-3 upgrades in 1-2 months period and everyone got upset that they had to upgrade then install mods again and again.
Basic fact is i would prefer it more just to overwrite the vb files instead of having to reinstall all mods again and again.
I guess as the saying goes you can't please everyone.