#13260: Add tutorials and quickstarts from PREP workshops to standard
documentation
---------------------------------------+------------------------------------
Reporter: kcrisman | Owner: mvngu
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-5.3
Component: documentation | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Karl-Dieter Crisman | Merged in:
Dependencies: | Stopgaps:
---------------------------------------+------------------------------------
Comment (by kcrisman):
> > I personally think that either of these sets are more appropriate than
the current "tutorial", which dates from the days when the Sage user could
be expected to have familiarity with the command line etc. Feel free to
cc: me on some of your things as they become ready for review.
>
> On a related note: is it possible to write documentation with typeset
output? I.e. I still want the output to be computed automatically and
checked against what's in the file, but for long polynomials and
complicated/decorated arrays text output can be very difficult to read and
annoying to produce... When jsMath fonts are not an issue, I don't see any
reason why anyone would not want to use typeset output in notebooks, so
why not use in the documentation?
I don't know. That would be a good different ticket. I mean, I can make
the output look nice, but I don't know whether it would doctest correctly.
I only {{{.. skip}}} ones I really don't want tested (random output or
interactive stuff).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13260#comment:13>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
