I wouldn't think that writing a basic HTML4 (no JS) browser in Tk would be that difficult.
HTML::Parser and a dispatch table should do the trick. (Note: I have exactly 0 Tk experience.)
As for userdocs in general ... I have to disagree with you. The best people to write and edit user guides are power users. The best people to provide feedback on user guides are novice users. So, merge the two of them together, a la the MySQL manual.
- Anyone can add comments to the documentation. These can be questions, clarifications, answers to prior questions ... whatever is appropriate
- When a comment is added, an email is sent to the moderator(s) of that page/section/manual
- The moderator(s) may remove comments and edit the documentation, as appropriate
The moderator(s) should include a developer, a tester, and several end users who have volunteered for this. They should meet at least once a month to go over anything that pops up.
Now, in terms of the docs themselves - I would have the documentation maintained in a source control repository - my favorite is Subversion. This way, whenever an app loads, it can go ahead and update to the latest version of the docs.
You can also track how the user guide has changed over time, so that the next user guide that's written can be done with "lessons learned" in mind.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.