On 6/26/07, Timothy Clemans <[EMAIL PROTECTED]> wrote: > Here is what I plan to implement today for courses in SAGE. > > home/~username~/courses > > Teacher makes a document like: > ---------------------------------------------------------------------------------------------------------------------------------- > SIMUW 2007: What is Riemann's Hypothesis? > > * Monday, June 25: Introduction to SAGE > ** Schedule > ** Factorization Trees > ** Serious Integer Factorization > > * Tuesday, June 26: State RH 1; integer factorization; enumeration of primes > ** Overview > ** Sieve of Eratosthenes > ** Infinitely Many Primes > ** Primes Modulo 4 > ** Prime Race Modulo 4! > ** Prime Generators > ---------------------------------------------------------------------------------------------------------------------------------- > > Then a page would come up that shows that outline with all the > subtitles as hyperlinks to empty worksheets with those titles.
It would be much better to come up with a simple system to link to an existing worksheet. It would accomplish the same purpose and be much more generally applicable. I.e., even right now one can write in a worksheet: <a href="/home/username/number/">that other worksheet</a> and get a link to another worksheet. This is less than ideal. Better would be to do something like <a href="worksheet://Name of Worksheet">that other worksheet</a> and have this give a link to the other worksheet. Moreover, if one renames the other worksheet, such hyperlinks should automatically be updated. Another option would be <a href="/home/username/name/Name of Worksheet">that other worksheet</a> I.e., the url /home/username/name refers to a worksheet by its name instead of its number. If multiple worksheets have the same name, then, e.g,. the most recently modified one is chosen. Also, if one writes <a href="/name/Name of Worksheet">...</a> then the workshets of only the user who owns the current worksheet are queried first. Please don't implement what you describe above, since I won't accept it as is. Frankly, henceforth I am going to be very picky about how the SAGE notebook develops, since I see it as "flagship functionality" for SAGE. In fact, I think any nontrivial feature enhancements to the notebook should be run through sage-devel before being implemented. And, at this point it is much better to spend time polishing, fixing existing bugs, etc. then adding much in the way of new features. Regarding wiki formatting versus html, that's not really a major issue, since at some point we can always implement/use a wiki-->html conversion script. If the basic functionality is there in html, the wiki stuff is fairly straightforward to build on top. 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/ -~----------~----~----~----~------~----~------~--~---
