[kepler-dev] [Bug 5069] The ability to create user manuals from a wiki that is continuously updated.

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Tue Jul 6 18:40:46 PDT 2010


http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5069

Christopher Brooks <cxh at eecs.berkeley.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P2                          |P3
                 CC|                            |cxh at eecs.berkeley.edu
    Estimated Hours|0.0                         |200.0
   Target Milestone|Unspecified                 |2.1.0
           Severity|normal                      |enhancement

--- Comment #1 from Christopher Brooks <cxh at eecs.berkeley.edu> 2010-07-06 18:40:45 PDT ---
I agree that making it easier for developers to update documentation is an
excellent goal.  However, it is fairly difficult to do and requires quite
a bit of effort.  

I'm not so sure wiki pages are the right solution because wiki pages heavily
hyperlinked and dependent on being on-line.  Edward Lee is working on a system
that uses LaTeX to generate pdfs that are suitable for printing or for viewing
on a computer.  The computer viewable pdfs have links to JNLP versions of
Ptolemy models.  There are likely other online systems that generate printable
files and on-line files.

Moving away from Word to LaTeX or anything else would be preferred.  A review
of what's out there would be a good start.

To close this feature request, we would need a system that would generate
something like the current Kepler printed documentation.  Such a system
should be easy for developers to use.  Ideally, it would use pre-existing
software as opposed to being developed in-house. 

I'm marking this as an enhancement and estimating 200 hours, feel free
to change.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the Kepler-dev mailing list