Usually the information in the help perspective (as in the content of the help pages) is provided by the UserManual directory of the plugins which have been switched on. There should not be a Module doxygen page.

The MITK User Manual (which most application manuals link to) can be found in the org.mitk.gui.qt.ext plugin.

Are you aiming to remove one of the views (Contents/Index/Search) a help page (corresponding to a plugin UserManual) or specific sections (part of such)?

Hi Caspar,
one feature would be to overwrite one help page, in case the documentation needs some extension. The next example is to exclude certain help pages of modules / views that are provided by MITK but are not shown in an application.

;) Best,
Ingmar

For the sake of an example we can look at the changes we made for our MITK Diffusion releases:
http://mitk.org/git/?p=MITK.git;a=commit;h=4ee4983863a0b16d0785d7c0dff18ad788c8b1a6

Is a customization commit, where we remove manuals of views we do not use and adapt the general application manual to our workflow. This is more of a stopgap solution though, so if we collect specifications we can probably try to implement a better solution.

Sascha if you have specific plans regarding this for the new application system, would you care to comment?

Hi Ingmar,

writing your own help plugin like org.blueberry.ui.qt.help is possible but should only be done if nothing else is satisfactory (writing such a plug-in is a lot of overhead).

Currently, there is no possibility to filter / overwrite existing help pages. We could think about several mechanisms, e.g.

http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fextension-points%2Forg_eclipse_help_webapp_contentFilter.html

That mechanism sounds very well! How much efford would such a feature be?

Best,
Ingmar