![]() |
I can honestly say that what me and zt have been talking about sounds amazing. I know all my hacks will use this system to avoid file edits.
|
this is creepy, but ill test it out, running a test forum anyway
|
wait till you see the next version. ;)
|
v2 released, this is what eXtremeTim gave me the idea about and was excited about :p
Quote:
- Zero Tolerance |
I can tell you this so far this hack looks great.
|
The button 'Show File Contents' seems not to work in firefox.
A second one.... I want to add a hook in includes/class_bbcode.php PHP Code:
May you have to expand your option to put a hook not online above or below a specified php line, but maybe also 2, 3, 4, 5 lines above or below... |
After some long thought on this, I'd like to make a proposal to all the entire vb.com community to make allour lives easier.
1. Only hacks that require changes to sql queries should be hacks. 2. Take THIS hack and place it in a seperate forum calls "Add-on Hooks". When a someone codes a hack that can't use a standard hook, they add an add-on hook into this forum. Then they can release their hack as a plug-in. One the add-on hook is released, it can be used by anyone. It becomes an unoffical extension of VB. 3. In the description for plugins, add an additional 2 fields: Requires add-on hook (y/n) ThreadID of Add-on Hook. 4. The folsk at VB.Com now have a way to see how many plugins use these add-on hooks. If we have an add-on hook that is used by 20 or more hacks, they know that it should be incorporated into the next release. As they do so, then that add-on hook can be removed from the forum and the hacks updated as full-plugin without add-on hooks. 5. For those of us with hacked boards, all it means is that we have to reinstall our hooks, not the entire hack. Comments/questions/concerns? |
i am in love - this hack is great
|
Hi,
I'm not sure how well this would work, but when patching the linux kernel, they use something called context diffs. Could this be adapted for this mod ? The idea is that when you add a new hook, your system would take say 10 lines of code before and 10 lines after the hook location. When an upgrade is performed, any hooks in code that has not changed would be easily detected. However, if the 10 lines above / below the code have changed, then you would know that the hook needed redoing manually. On applying the hooks to an upgraded board, you could then generate a list of failed patches that would need to be added manually. Not perfect, I know, but it would pick up the majority of failed hooks. Martin |
Wow, exceeded yourself again.
|
All times are GMT. The time now is 07:57 AM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|