I agree that it would be a good idea to join these two ways to access the
documentation but I am not sure what the best solution is.
A drawback with the Help button for the critics is that there isn't a
solution to know what chapter and section i.e. what file, each of the
critics description reside in. For that reason, the printable version (i.e.
the entire manual) is used for this instead of opening the correct file of
the chunked manual.
Several years back we had the javahelp version of the manual generated to be
deployed with ArgoUML. Now, since we are moving towards Eclipse and Eclipse
seems to use html files provided from a local web server, generating and
deploying html files takes us a long way.
/Linus
2008/7/4, Michiel van der Wulp <[EMAIL PROTECTED]>:
>
> Hi *,
>
> There is a new menu-item Help -> Help, which opens a window (JFrame)
> showing the html manual in one tab (
> http://argouml-stats.tigris.org/nonav/documentation/manual-0.24/) and the
> support page (http://argouml.tigris.org/nonav/support.html).
> This window allows clicking on links, and navigates like a browser, but it
> lacks all other functionality of a browser (like a "back" button).
> Implementation: org.argouml.ui.HelpBox, used by ActionHelp.
>
> On the other hand, there is the old "Help" button for critics,
> implementation in the WizStep class, which opens the standard browser of the
> system, see StartBrowser.openUrl(). This function has been tested to be
> working on all OSes, since it has been in the code long time.
>
> Would it not be better to abandon the HelpBox class, and use the
> StartBrowser way also for the Help menu-item?
>
> Regards,
> Michiel
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
