Currently there is a tasks menu which lists some useful apps, there needs to be a way of adding other apps into that menu (such as a server based calendar client - e.g. nscal32 or corporate time's equivalent). I'm not sure this is logged against the correct component so feel free to correct.

There is no tasks menu any more. Anyway there is an a way, edit the chrome for the menus ...

Reopening and adjusting summary to better reflect request

mpt writes ui specs, this is a doc bug, sending to someone who might care or know someone who could help.

Thanks timeless for sending this my way. CCing some folks who are involved with writing documentation for NS customizations. Chris, Kristi, do you cover the customizations mentioned (do the products you're working on allow/enable such customizations?)?

It would be nice to have a unified, documented way to add apps so that they appear in a predicatable place, and that the user can find them as well. Apps like Dreamweaver specify a particular location in their app's subdirectories for helper apps to be located. Perhaps doing something like that here would help. Another aspect of this is that since there is no "uninstall" - if 3rd party apps all behaved in a consistent way, we could create a fairly simple uninstall FAQ for folks. As it is now, given that there are no guidelines, apps might show up just about anywhere - both on the user's HD and in the UI. Accepting Bug.

As of now you can use CCK to add separate executables that install at the time you install a customized browser, however I don't believe that these apps appear in any browser menus, and I don't believe there's a plan to add this functionality in CCK. Copying customization engineers and Rodney Velasco,the customization QA person who's familiar with the process for adding Calendar app.

This might be something to look at as well. http://www.xulplanet.com/tutorials/xulapp/overlays.shtml New tools should come in as overlays, not directly editing the xul.

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614