Hello,
I've released sage-1.7. Thanks for everybody's help!! Improvements include inclusion of several new standard components (moin moin wiki is now standard -- type wiki() in any copy of sage-1.7 to get your own wiki with jsmath support; openssl, pyopenssl, palp-1.1 are now included standard), and lots of new and/or improved code, including more sloane functions, and the first release of Yi's distributed sage package (version 0.0.2). I've also done a bunch of work on the (now reference manual to make it more comprehensive and organized. The goals for SAGE-1.8 (to be released hopefully by Sunday) are as follows (or see http://sage.math.washington.edu:9002/sage_trac/milestone/sage-1.8) -- William == SAGE-1.8: Goal Date is Jan 20, 2007 == From the point of view of a good quality SAGE-2.0 release, the most import things below are fixing all the listed bugs, optimizing matrix algebra, and improving the SAGE constructions document. == 1. Bug fixing == * Fix the fixable important SAGE bugs listed in trac (ones below not fixed will be fixed for sage-1.9): - trac #34 -- modular symbols bug - trac #39 -- implement equality testing for ZZ[x,y,...] using M2 (or give error message) - trac #189 -- minor sage notebook formating bug - trac #45 - ntl modulus reset correclty. - trac #130 - problem with multiline history recall in IPython - trac #149 -- failure in E.sha_an() - trac #151 -- clisp.run's left running -- it's still happening though many cases have been fixed. SOLVE this frickin' zombie problem somehow once for all... - trac #168 -- Plot bounds ignored when frame=True - trac #177 -- pari interface -- new arithmetic model - trac #185 -- implement backoff when queuing for notebook updates. - trac #188 -- Python's builtin round function is funny since it always coerces to float - trac #32 -- missing coercion of polynomials between different bases functionality - trac #35 -- load "adosfile.sage" breaks - trac #63 -- in safari notebook, tab key inserts tab AND moves to beginning of cell - trac #96 -- time command doesn't work in .sage files !? - trac #154 -- gfan changes broke interface slightly. - trac #156 -- freeze of gfan (actually singular -- not gfan's fault) - trac #181 -- recursive load and symbol?? - trac #148 -- links in saved notebook worksheets - trac #192 -- polynomial arithmetic bug == 2. Documentation == * SAGE Constructions (Stein, Kohel, Joyner): Update the constructions guide to use "modern SAGE" constructions to solve the problems. No dirty tricks except in a dirty tricks section. == 3. Code == * Optimize matrix algebra over QQ, GF(p), ZZ (Stein, Bradshaw, Ifti B) - matrix permanents - multimodular algorithms - more optimizations for special rings (e.g., copy, etc.) - use ssmod as an example to motivate this - In the file matrix/docs.py is a list of base rings where specialized matrix classes should be implemented. More specialized vector space and free module classes also need to be implemented in SageX. * Update the symbolic calculus package if more is done on it. * Integrate in code from Ling Long et al for congruence subgroups * SageX: generic polynomial ring elements * SageX: generic power series over arbitrary ring * SageX: generic laurent series over arbitrary ring * Improve modular symbols and modular forms. Some algorithms haven't been completely implemented. (Some do things I never implemented in MAGMA.) - finish modular forms algorithms - enable modular forms doctests and test and fix - finish implementing modular symbols factorization in general (eisenstein part is currently not fully implemented) - computation of period mapping - more testing, examples, etc., for modular symbos for GammaH * Improve the SAGE notebook * Implement wiki typesetting for the notebook. * Change notebook disk format to plain text (no pickling -- mainly for security reasons). * Export functionality. One should be able to export a single worksheet, or a collection of worksheets to any of the following three formats: latex, html, pdf, text. * NOTES: - NOTE: for each, we should allow a single worksheet, complete notebooks, and any subset of worksheets to be exported. - Hopefully Tom Boothby and Alex C can help. * PLAN: 0. Design and implement a wiki formatting system (this means basically just getting a function wiki2html from moinmoin.) 1. Design a logical interface: - INPUT: list of worksheet names - OUTPUT: * for latex/html: a link to a tarball or zip archive * for pdf/text -- link to a single file. * the archive contains both the latex and html and the complete notebook directory, so it can be opened by anybody later. * the plain text option gives everything as a single plain text file -- no tarball. 2. Design interface that can be used from notebook. - A command --, e.g., {{{ %export latex # -- exports current worksheet in latex %export html graphs plots # exports two worksheets to html %export text * # the entire notebook %export html plot* # all worksheets begining with plot. }}} - The ordering of the worksheets is determined by the order they are given on the line. - This has to be a special %blah command, not a normal Python command, since it has to be run in the notebook process, not in the worksheet's Python sub-process (as that could be running in a chroot jail or on another machine). - The above interface could likely be easily made to work entirely through a GUI later, and will be easy to document. So it's the right first step. 3. Implement interface above: - The command %export will be mostly implemented in worksheet.py - The hard part is testing, and generating actual latex/html/text which will require adding methods to cell.py, worksheet.py and notebook.py. * POSSIBLE PROBLEMS: - The interface designed above is bad for some unforseen reason. - It will be too difficult to implement in a clean way. - Latex output -- some generating output might not actually latex correctly, which could be frusting. Providing a script to build the latex output (using pdflatex, say, and with nostopmode) would help a lot. - Should also provide pdf output, which is autogenerated by the server (Added.) - What about customization of the "style", e.g., css, layout of index into worksheets, etc.? - Should generated latex be hyper-indexed? Issues with cross-referencing of worksheets. - Eventually the documents produced this way should have the possibility of looking truly professional, which means that one should be able to include macro files, etc. It should really provide a totally new way of writing papers. Along these lines, the "Edit" mode for the notebook should support including latex instead of html. The latex would be "previewed" by the notebook using jsmath. But when exporting it would stay as latex that would get pdflatex'd. --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
