Summary: | [Chameleon - DocBuilder] HTML output option using xslt's | ||
---|---|---|---|
Product: | Chameleon | Reporter: | Chris Thorne <cthorne@dmsolutions.ca> |
Component: | AutoDoc | Assignee: | William Bronsema <wbronsema@dmsolutions.ca> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | chameleon-dev@lists.maptools.org |
Priority: | P2 | ||
Version: | 1.99 | ||
Target Milestone: | 2.0 Final | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Assign to bill, target to rc1
I think the HTML generation can be (and should be) kept very simple. It should be a checkbox in the doc_builder prcess. This will allow for generation of HTML at the same time the XML is updated as well as allow the user to exclusively generate HTML docs from the existing XML docs. It will be CLEARLY indicated on the checkbox that the HTML docs are being generated from exisiting (or newly generated) XML files and NOT from the widgets themselves. If an XML doc does not exist for the selected widget, an appropriate error message will be displayed.
bill, I think it is important to have the doc builder first update/check the xml doc during the output of the html documents. But you are assuming that the xml doc process is perfect. :) There will be instances where a missing attribute will be added manually, and if not registered by doc builder correctly it will be commented out and not show up in the html output. How should be deal with this?
I understand what you are getting at, but because the HTML output is only needed as a secondary measure for the help viewer I don't see the need (or think the time should be spent) to create another interface for something like this. As I indicated earlier, the process (i.e. checkbox for HTML output) can be run as a stand alone process using the same interface. Just select the widgets you want to gerneate HTML docs for and click "Gen Docs". How does that sound?
I agree with your statement. Check box options vs. a new interface would be best. How about. Two checkboxes: 1) for xml output and 2) for html output. * If both are checked xml will be processed after html. * If 1) is only checked than xml will be generated (this should be the default setting). * If 2) is only checked than html is genrated. If not xml is found than an error message should be presented. Is that ok?
Yes, that sounds fine to me, that is what I meant by "stand alone process" (although I didn't explcitly say so ;)).
moving target to final release.
Fixed in CVS. In the intrest of saving time, the process has been greatly simplified. The last step of the doc builder is a list of available XML docs. Select the doc(s) from the list and click the "translate" button.