6.96 KB, text/html
The new hooks mechanism, from bug 229658, requires documenting so that organisations and companies extending Bugzilla can make good use of it. Gerv
Severity: normal → major
Priority: -- → P2
Target Milestone: --- → Bugzilla 2.18
Created attachment 139303 [details] documentation of the hooks mechanism, including example Here ya go.
I checked in a modified version to the customisation part of the guide. Feel free to look and edit it some more. It certainly needs work to clarify that both extensions and custom have hooks, for different purposes. Checking in customization.xml; /cvsroot/mozilla/webtools/bugzilla/docs/xml/customization.xml,v <-- customization.xml new revision: 1.2; previous revision: 1.1 done Gerv
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
Thanks Gerv. I've checked in an update that among other things adds a note explaining hooks' applicability to installation customizers. It remains to be seen how useful hooks will be for that constituency, and since support for customizers was a side-effect of the hooks architecture rather than its principal goal, advertising it even more would probably place too much emphasis on that potential use, especially before we get at least one report back from an installation that tried it. We should mention it in passing when we advertise the feature in the "what's new" section of the release notes, though, with the caveat about its side-effectness and a request for feedback from customizers that try it.
It looks like the documentation has gotten a bit ahead of the implementation. I went to look for the hook in the example and could not find it. I will make a point of locating some of the UI customizations I have made and will suggest some hooks that would have worked for me.
Joel: bug 232908 filed for that issue. Gerv
You need to log in before you can comment on or make changes to this bug.