[bashy]

Laymans terms please lol

[Protoman]

it works!

[Trigunflame]

Originally Posted by bashy

Laymans terms please lol

If you use a lot of "Plugins" via the Vbulletin Plugin System, this will make your site faster when I get an actual version working.

[Andreas]

Interesting
I wrote a little windows application to prepare a "slipstreamed" vBulletin with all Plugins included back in beta stage.

Worked very well, though you loose the flexibility of the Plugin system:
You can't easily enable/disable Plugins/Products through ACP anymore, as this requires reprocessing the files.
And having them +w might not be a too good option, especially in shared environments.

[Trigunflame]

Originally Posted by Andreas

Interesting
I wrote a little windows application to prepare a "slipstreamed" vBulletin with all Plugins included back in beta stage.

Worked very well, though you loose the flexibility of the Plugin system:
You can't easily enable/disable Plugins/Products through ACP anymore, as this requires reprocessing the files.
And having them +w might not be a too good option, especially in shared environments.

Well this is the thing, you Will be able to easily "enable/disable" the plugins and products from the ACP; this system will not hinder the use of that, I will keep a cache of the hook_name => file pairs, by good use of power of preg via comments I can control where code is placed in the vbulletin files and be able to add and remove plugin code easily (Only) on the needed files, no need to scan the files again for every plugin code change.

As for the chmod options, there is a truth to that; but I can probably write a suitable php implementation that can control the chmod options to a degree when files need to be wrote, then set back to 755.. ofcourse this will defer depending on the system; in the end people can always chmod their files to 777 when they want to make a change, then back to 755 when they finish.

[Andreas]

Yeah, but if I turn Off the Plugin System you will have to re-process all files that contain active Hooks

Also, you would have to add a check for DISABLE_HOOKS being set on every Hoook location, or that won't work any longer - which again adds some overhead.

[Trigunflame]

Originally Posted by Andreas

Yeah, but if I turn Off the Plugin System you will have to re-process all files that contain active Hooks

Also, you would have to add a check for DISABLE_HOOKS being set on every Hoook location, or that won't work any longer - which again adds some overhead.

That is true, but you are talking hypothetically. Realistically no one is going to turn their plugin system on and off several times a day every day. There are lots of plugin hooks, but not all of them are used.. as such not every file has to be modified and not every hook has to be replaced. If the file contains hooks that are not currently used by the system they are simply commented out.

I plan to keep existing compatability; Even if used an if() construct for each plugin segment that still takes less cpu cycles than an empty function call.

[Trigunflame]

Update:

Integrated Test Number 2, this does an actual hook cache, hook replace with php code, output with 2 included example files.

This is a proof of concept attempt, and will be further expanded probably tomorrow.. but this is a good foundation to work from.

No need to worry about modification of your files, this is performed on the 2 test files e_1.php and e_2.php included with the archive.

[Zia]

hello...
im not a coder or a xpert...
in easy way...does it help speed up vb3.5.3 ?????
.i read the description mentioned...:S kinda hard to realize..

it will create another plug in system that will work faster than the defult system?




sorry for this kind of raw qus...but im not a coder or an xpert..
thnx

[Trigunflame]

Originally Posted by Zia

hello...
im not a coder or a xpert...
in easy way...does it help speed up vb3.5.3 ?????
.i read the description mentioned...:S kinda hard to realize..

it will create another plug in system that will work faster than the defult system?




sorry for this kind of raw qus...but im not a coder or an xpert..
thnx

This is alpha quality code, we are just in the testing stages; the current code in the archive simply provides 2 tests that you can run to see if the plugin system code will work on your server/forum/site.

We should have "fully" operational code with the next day or so.

[Zia]

Thans let us try with it in our test site ...

thnx

[uae]

Hey thanks,
But there is no file called static_plugins.php in the zip file!

[Trigunflame]

Originally Posted by uae

Hey thanks,
But there is no file called static_plugins.php in the zip file!

I renamed it to test.php, sorry I'll update page.

[The Realist]

Re: No4 below, what findings do you want?

1) Instructions:
2) Download the zip file.
3) Place the static_plugins folder in your forum directory.
4) Run the script via the url [U]http:// yoursite.com/static_plugins/test.php
5) Report your finding back here if you would please.