I forgot another thing. It would be nice if there were DHTML animations that showed say a problem and showed the SAGE code being written out with highlighting to show exactly how the code was connected to the problem.
On 3/9/07, Timothy Clemans <[EMAIL PROTECTED]> wrote: > LaTex formulas do not appear in the doc browser. For example > http://sage.math.washington.edu/sage/doc/html/tut/node20.html compared > to http://sage.math.washington.edu:8100/doc_browser?/tut/?node20.html > > Could there be some definition in SAGE of what say a pair-wise > function is so a user could bring up a random pairwise function and > see the LaTex notation, SAGE notation, and various examples? > > It would be nice if there some commands for hiding navigation for the > documentation. > > Maybe at some point we could get the people who like making > encyclopedia entries about mathematical stuff to help put together one > for the SAGE Notebook that would combine with the SAGE documentation. > "Don't know what a ring is? Well then in the documentation, just click > on ring." Mathworld, PlanetMath, and Wikipedia are all static in a > sense, because they do not have a system for accessing information > based on skill level. There is a lack of extremely technical > information on say Wikipedia or an article is too technical for a > general audience. > > So yeah it would be nice if there was system for generating examples > of just about any thing in mathematics and in SAGE with examples of > computation around that. Then it would be nice if there was a > mathematics encyclopedia that was merged with the SAGE examples system > and data execution interface like the doc browser is. > > On 1/29/07, William Stein <[EMAIL PROTECTED]> wrote: > > > > On Sun, 28 Jan 2007 23:58:33 -0800, Iftikhar Burhanuddin <[EMAIL > > PROTECTED]> wrote: > > > On Sat, 27 Jan 2007, William Stein wrote: > > >> It would be helpful if somebody would try out the doc browser by > > >> going to http://sage.math.washington.edu:8100/ and clicking > > >> on Documentation (in the upper right), and tell me what you think. > > >> I'm aware that if you bring up a *huge* page that your browser > > >> will likely be very unhappy, but there are very few such pages > > >> now. > > > ... > > >> But overall, do you think this is useful and a good addition > > >> to SAGE? > > > > > > This takes the coolness factor of the notebook up to eleven!!!!!!!!!!! > > > > And earlier this evening Nils Bruin emailed a bunch of good ideas > > for improving it much more. > > > > > We should think about doc (re-)writing keeping the doc browser in mind. > > > > E.g., Nils suggested cross referencing. I think that's fully supported > > by the doc browser, but just not used much in creating the doc files. > > But it could be -- it would just mean using standard latex cross > > referencing in docstrings, for the most part. > > > > > For instance should we split huge doc files like the following: > > > > > > http://sage.math.washington.edu/sage/doc/html/ref/module-sage.schemes.elliptic-curves.ell-rational-field.html > > > > > > into parts? > > > > Heck yeah. Huge doc files are horrible. The one corresponds to a huge > > code file, the dreaded 4182 line ell_rational_field.py. I would love > > to split that up in some sensible way. E.g., Nick recently helped > > some by moving the formal groups code out, but much more could be done. > > > > -- William > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
