> They would (continue to) point at the already existing beezer. > Beezer's book wouldn't explicitly reference beezer, since all > references should be relative in that collection of worksheets.
Yes, but then you probably sooner or later need a tool for merging two such collections of worksheets. > Note again that I want to implement a hierarchy of worksheets, so a > worksheet can have a bunch of subworksheets, just like a web page has > pages that hang off of it with relative links. Note that for web pages, source code, etc., we do have tools to do hierarchical merges. Which, to me, argues again for making a distinction between a Sage source tree and the Sage cache. The Sage source tree should only contain those files that I have actually typed in. It could be hierarchical and the directory and file names could be the labels. Then I can manipulate that source tree with all the standard tools I have at my disposal: version control, merge, diff, etc. Tom -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
