Re: Features Listing

In article <bk7a3d$a95$1-111RdWWlOxkOkXtL6OYfHgC/[email protected]>, "Jason Judge" <[email protected]> wrote:
>...
>You know a bit about hooks: is is possible to provide different types of
>hooks from a module to different modules? For example, could Autolinks
>provide a transform hook to all modules, but a create/update GUI hook to a
>selected few modules? Or is it an all-hooks-or-nothing system, with the hook
>module deciding when it should and should not supply hook details? I'm
>probably asking the wrong questions there - as I am not very familiar with
>the GUI side of hooks.
>
>Just something I am beginning to mull over as I see transform hooks with
>preg-replaces pop up all over BK...
>
>-- JJ

Hooks are an all-or-nothing business (excepting if you delete individual
entries in the xar_hooks table). However, you could return immediately
when some modules call one of your hook functions, and handle calls
from other modules in a different way.

For example, the ratings module allows you to configure different
rating styles depending on who's calling, the changelog module
allows you to specify which fields to save for each module, and
of course, dynamicdata does different things for everybody who
calls too :-)

Or you could also imagine supporting different sets of transforms
depending on who's calling, for instance...

Mike.