The CCK Wizard for 5.0 includes the ability for the CCK user to add a custom Help menu item and URL to the Help menu. See the CCK Wizard UI spec, "Customizing the Browser - Part 2" screen: http://www.mozilla.org/projects/cck/docs/CCKWizard/wizard.html Please coordinate with Steve Elmer to get this feature implemented in Seamonkey.

Reassigning to don.

Steve, do you want this one or shall we do it for you? I think you can add help menu items to the XUL now ...

Don, what mechanism should we use in install-builder to modify the XUL consistently?

I need a description of how it works. Is there a tool or some code or something?

Matt, can you take care of this?

As i understand it you need to add an menu item to the help menu. This could be done using the new overlay work that hyatt just did. You would have to write out a xul overlay file and insert it into the chrome directory and the edit the registry.rdf file using javascript.

Please note that this is for a customization tool that does not run in the context of a browser session. We need to be able to customize the help menu in a programmatic fashion without using javascript. In the past, this was accomplished via prefs and the help menu was dynamically generated. I don't care if 5.0 uses prefs, but the new mechanism needs to be simple and as reliable as the old one. (Editing registry.rdf doesn't sound simple.) If this is already easily done, please provide _specific_ documentation that describes how it is done.

If changing the rdf file though javascript we need to think this though. That was the only way i thought we where going to do dynamic menus but it looks like we are going to have to build the help menu at startup.

Is there a specific mechanism you're proposing then? We need to do our work before the customized installer is built. We could create a XUL file from a template, but we'd need some mechanism to get it recognized.

Matt, talk to me about this before you go implementing anything.

What's the deal moving this to M14?

Move to M15.

This is implemented. We just need hyatt to do the work on the installation API's.

Move to M16 for now ...

adding fixed since hyatt fixed his bug. Should work using the installation api's