2013-02-07, 03:15 PM
I think it'd be good if there were a lot more hooks available for use and if they were documented better. Currently the only real list just points to their line number which forces developers to keep looking back at the code, and sometimes there's actually no way to modify the data you need to while the hook is called, so I think it'd be awesome to have hooks cleared up and moved to places where it can actually be used (For example, when searching in the AdminCP, the hook is called at the start of the method, which will not allow any modification to the results, see this) and including data that can easily be modified, instead of just 'being there', they would be even more useful and flexible.
Hooks should be implemented for almost all core functions like formatting names (Which should be used everywhere a name is shown, or of course a central function to set the display name before formatting/putting into a link), pages which display data of some kind (Searches, Forum Indexes etc) should have an easy way to modify the data (Passing the array even, but some hooks are in bad positions that cannot modify outgoing data, even then the html output is set before it's even usable by any hook right now)
Hooks should also be documented differently, if they have data that can be modified it should be defined in a documentation page like Java's javadoc generated pages, it might be a big project but it'd speed up development time for a lot of plugin developers.
This is kind of a big change for 1.6, so if it would be nice to see implemented in 1.8 before the release
Hooks should be implemented for almost all core functions like formatting names (Which should be used everywhere a name is shown, or of course a central function to set the display name before formatting/putting into a link), pages which display data of some kind (Searches, Forum Indexes etc) should have an easy way to modify the data (Passing the array even, but some hooks are in bad positions that cannot modify outgoing data, even then the html output is set before it's even usable by any hook right now)
Hooks should also be documented differently, if they have data that can be modified it should be defined in a documentation page like Java's javadoc generated pages, it might be a big project but it'd speed up development time for a lot of plugin developers.
This is kind of a big change for 1.6, so if it would be nice to see implemented in 1.8 before the release