Adrian Rossouw wrote:
On 09 Jun 2006, at 4:08 PM, Nedjo Rogers wrote:
(Or, alternately, I suppose, these data could be coded into an install metadata file.) My solution to the problem involves separating out the menu system, and it's actual nature.. the callback system.
Thus allowing you to register multiple callbacks, of different types.
It should be able to pick up what hooks a module implements when it is enabled, and then keep a pre-sorted callback order. (in the fapi callback format, preferably).
When it comes down to it, a hook is just an automatically registered callback. and the big problem with using a hook over a registered callback, is you have no way to give extra information about it.
Adrian - are you planning to work on this. Would be very very useful. Even if you wrote a design doc for it and left the coding to others. @Boris - Perhaps you can free up Adrian to work on this doc. Is a prerequisite for fapi 2.0.