My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CRDSS_Task1_05-12_OnlineDocumentationSystem
CWCB
>
Decision Support Systems
>
DayForward
>
CRDSS_Task1_05-12_OnlineDocumentationSystem
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/25/2011 10:18:53 AM
Creation date
5/30/2008 2:34:31 PM
Metadata
Fields
Template:
Decision Support Systems
Title
CRDSS Task 1.05-12 - System Integration Issues Documentation - On-line Documentation System
Description
This memorandum discusses methods of delivering an on-line documentation system for the CRDSS.
Decision Support - Doc Type
Task Memorandum
Date
6/29/1994
DSS Category
DMI Utilities
DSS
Colorado River
Basin
Colorado Mainstem
Contract/PO #
C153658, C153727, C153752
Grant Type
Non-Reimbursable
Bill Number
SB92-87, HB93-1273, SB94-029, HB95-1155, SB96-153, HB97-008
Prepared By
Riverside Technology inc.
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
17
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
Mosaic <br /> then displays all level 1heading using the same font and allows the user to select a different <br />Mosaic <br />font family with a menu selection (or program resource). supports several different layers <br />for headings and general text formatting (e.g., emphasis, bold). <br />Hypertext links are implemented by using ?anchors.? The author of the HTML documentation is <br />responsible for determining how text is to be ?hypertexted.? For example, the author would have to <br />determine that clicking on the word ?CRSM? will cause a page defining CRSM to be displayed. In <br />this case the word ?CRSM? is an anchor and points to the document with the CRSM information. <br />Adding such hypertext links can be taken to the extreme with every other word pointing to different <br />information. <br />Mosaic <br /> works with three basic file types: <br />HTML files Mosaic <br />1. . These files contain HTML commands that understands and can <br />format. <br />GIF files Mosaic <br />2. . These are raster images files in a format that inherently understands <br />how to display. The GIF format is widely used for images and provides a relatively <br />compact storage format that supports color images. <br />Text files <br />3. . These are ASCII files that contain preformatted information such as output <br />Mosaic <br />from other programs. can import such files and does not try to format the files. <br />Mosaic <br />HTML files are the ?glue? that hold documentation together. However, the development of <br />HTML files requires that the author of documentation understand HTML syntax and be willing to <br />expend a certain amount of effort in developing HTML versions of software documentation. This <br />effort may be too expensive to implement fully in certain cases. <br />GIF files can be intermingled with text in HTML files and can even be used as anchors. Image files <br />that are not in GIF format can be displayed using an external viewing program (the default is the <br />xv lview <br />public domain program on UNIX workstations and on PCs); however, in such cases, the <br />image cannot be intermingled with the text and the use of an additional window to view the image is <br />somewhat distracting to the user. Consequently, RTi proposes to convert all images to the GIF <br />xv <br />format where possible. This can generally be done using the public domain program. <br />Text files can be used effectively when documentation consists of output from a program or is a <br />conversion of a word-processor document. For example, a text file may be an output file from an <br />analysis program. Or it may be a text version of a WordPerfect document exported from <br />WordPerfect. <br />Mosaic <br />The program will also display PostScript files using an external viewer (the default viewer is <br />Ghostview <br />the public domain program). Again, this prevents the documentation from being <br />intermingled with HTML text and requires that the user deal with an additional window. However, <br />use of the PostScript viewer may be appropriate in cases where existing documentation is in a <br />format that cannot be easily converted to HTML or text files (e.g., the WordPerfect version of the <br />MODSIM documentation, which contains equations that cannot be easily translated). Long <br />documents should be split into manageable sections or chapters in the cases where PostScript files <br />are part of the on-line documentation. <br />3 <br />A275 06.29.94 1.05-12 Malers <br />
The URL can be used to link to this page
Your browser does not support the video tag.