I would like to inject help on views displays (block, page, attachment, ect..)

Adding to blocks would be good ... but here's what I'm seeing ...

The need to add "help inject buttons" to views would be pretty much taken care of by using both the "path" and (proposed) "block" type, but a specific "view" type would take care of attached views as well as being a more accurate "attachment point" for view specific documentation.

I'm developing complete "pre-configured" website packages for small business owners. These packages consist of an install profile, a theme, and a custom module, built on top of a standard Drupal distribution (like Acquia Drupal). In this case, the targeted end users are not Drupal savvy, and probably don't care to be. In fact, this might be their first website. In these "pre-configured" packages, It would benefit both package developers and the end users to have an in depth "owners manual" available, and integrated into the navigation of the site. With such an owners manual, these business owners could understand (without relating to modules) the "high level" architecture and administration of their specific Drupal configuration.

Seems to me, that this sort of Documentation would best be delivered "in context" using the "advanced_help" module. Your "helpinject" module is a great tool to create these documentation texts, but so far they are only available to "inject" on forms and paths. A true "in context" help injecting solution (in this case) would include more attachment points. One per every view, would be a good way to document the purpose of each view in the site's architecture. One per every menu would be good to, for the same reason. The point being (in this case) to provide an an easy "in context" assistance to new website owners.

So far, to get advanced_help on every view, I have added the following code to views-view.tpl.php in my packaged theme:

         // Get the name of the module that contains the injected help
	 $help_module = theme_get_setting('help_module') ;
	 	if ($help_module && module_exists('advanced_help') && module_exists('helpinject') ) {
                        // create a unique identifier for this views display
			$help_file = 'view-'.$name.'-'.$display_id;
                        // look for a help file with that identifier
			$help = theme('advanced_help_topic', $help_module, $help_file);
                        // No Find? add a helpinject button 
                        // THIS is where I would use 'view' instead of 'path' as the type argument
			$help = $help ? $help : _helpinject_admin_link('path', $help_file);
                        // print advanced_help button OR helpinject button
			print $help;
		}

I'm not counting on this to work in injecting usable help on the views. But at least I can write my book pages, and get them referenced to a view ID. When I export the module, I'll probably have to tweak it. But that's where I'm going with this.

How can we get this module developed to "inject help" in views (and blocks and menus?) as well as paths and forms?

Thanks,
M.M.