As you know, you can create context help for VIs, polymorphic VIs, and parameters by entering documentation into the fields on the Documentation tab of the Properties dialog box. You also can create links to HTML-based help topics for the VIs and polymorphic VIs by filling in the Help Tag and Help File on the Documentation tab. However, to create the HTML-based help topics you must either manually create HTML topics for the VIs, as well as the Contents tab, or generate HTML topics for each VI using LabVIEW's printing features. The resulting HTML, however, does not have the same look and feel as the help files that ship with LabVIEW. After you create the HTML topics and edit those topics, there is no easy way to get the edited documentation back into the context help for the VI, poly VI, or parameters.
So, with that in mind, I'm interested in answers to the following questions.
And when that help in XML is generated.. Can I edit the XML and from there refill the description etc of the library again to make it consistent in the way I should have done that in all those VI's ?
This export and later import would make it a better job to do, or even better to give that job away to someone else.
I really would like the option to generate documentation from the information I put into the description of the controls, description of VIs, tipstrips, etc.
However putting that info into the VIs can be a tedious job. If you have to right click each control or VI icon to edit it's description that is really annoying.
Exporting it (to get all the controls), edit it and import it again: I do not know of an easy editor to do this in or do I have to scroll through all the meta tags in notepad to edit the info?
What I would rather have is a floating pallette which is a permanent property browser in which you can easily add this info for the selected controls and indicators. If you select more than one and change one of the properties this is field is updated for the selection. The advantage of doing the documentation from within LabVIEW is that you have the context also available otherwise you constantly have to switch between your editor and LabVIEW to see which control was meant with descriptive names like 'index' for instance.
This is like the MSVisualBasic resource editor (you can show other properties of a control or the properties in common for a group of controls as well).
As long as we are plugging software: this is a tool I created 2 years ago to get the info into LabVIEW: