Sage Usability Improvements

This unofficial wish list is adapted from this repository. Please feel free to add or clarify ideas, link to trac tickets, make comments, reorganize items, point out useful links, etc.

Documentation

• LaTeX doc mode.

• Use $ instead of back ticks for math in reST - #6892.

• Use Sphinx for sagenb.org docstrings

  • Depending on how much stress this puts on a server, we could use a less expensive hash function or hash only part of the incoming docstring. Better yet, pass the object's fully qualified name to set_introspect_html() and hash just that for introspection of read-only code.

• reST mode(s)
  1. replace tinymce by reST editor?

     • You might be able to make TinyMCE *be* a reST editor. See this example of making TinyMCE into a BBCode editor.

     • reST's implicit closing tags may make this difficult.
  2. This is better: %rest in cells, and get reST output.
     • Should this be HTML output from Sphinx? If so, perhaps we should put the Sphinx-ify code in its own module or a utility function. Note that it would be good to autohide and have doubleclick be show. Same with %html.

• Document pexpect interface for users.

• Live introspection cells.
• Introspection cross links.

• Tear-out docstrings - #6001.

Notebook

Admin

• Streamlined deployment - account management, fewer bugs, etc.

• Captcha for notebook sign-up - reCAPTCHA. This is *only* needed at registration.

• LDAP authentication. (tdumont) -- do this by refactoring auth code so that user/password is 100% separate from anything else in the notebook. Then LDAP or anything else is completely trivial.
• Guaranteed worksheet-server synchronization:
  • - at least have a timestamp on the server - TinyMCE never gets sent back somehow leading to corrupt worksheets. - maybe use the javascript ping function to push changes out.

• Reduce data loss possibilites. (dataloss.txt): easy backup of all critical data in a notebook server. Get via web interface as admin. Archives.

• Recover passwords. (Byungchul Cha)
• Email address as username.
• Add users as admins. (fprimex)
• User groups.

• Security -- see http://www.gingerlime.com/20090901_securing_sage_notebook.pdf

• Functions to delete worksheets/USER/*/BLAH where BLAH is cells, code, data, or snapshots? Does this affect the size of .sws files? Admin pane showing usage for various things, e.g., snapshots. Allow easy trimming of old snapshots, configuring how their kepts, etc.

• Balancing server_pool:

I managed to do a little of this by exporting the directory that the
notebook is running in via NFS to the other machines and maintaining
the same permissions and file structure for everything else.  However,
this raised another issue in that not all my machines are of
comparable power.  How complicated would it be to add something that
allows you to balance how many processes go to each server?  I'm
thinking something along the lines of distcc's host list.

• Account approval: Possible solution -- just have an interface like Google groups where new users can be "moderated by default".

> We have a small server and would like provide SAGE (in form of the
> notebook) for the students. However, it maybe a bit
> "risky" (especially, we have no experts to manage it) to open it up to
> everyone. So we would like to have some kind of "account approval"
> procedure. Can that be done, if so how?

Users

• Sage Forge -- idea posted on Sage Devel by Matthew Turk

• "It could be really useful to have Sage generate RSS feeds when sharing or publishing worksheets. There is a firefox extension for reading RSS feeds called Sage which could also be developed further to work with Sage software." -- Serge A. Salamanka (on sage-devel)

• See http://routes.groovie.org/ to handle URLS (which is basically all twist.py is doing a lot of).

• Sage could (and should!) ship copies of the jsmath fonts, and explain clearly what to do to install them whenever they aren't already installed. The current system, which involves visiting the jsmath website in response to subtle hints is not very good.

• Fix TinyMCE issues, as mentioned here: http://groups.google.com/group/sage-devel/browse_frm/thread/4cd1cc188470c723/c2477e1bdba68028?q=tinymce+bug+group:sage-devel#c2477e1bdba68028 and http://groups.google.com/group/sage-devel/msg/e2eb3f848a21faa3

• Move preparsing to the worksheet (not server). This (1) solves implicit multiplication problem, and (2) fits well with the "notebook server computers the least possible" philosophy.
• Improve handling of multiple users using the same worksheet.
• Trivial to set implicit multiplication option for the notebook. On a per worksheet basis with a user default. Same for typeset option.
• Reorganize the notebook help page.
• Automatically have worksheets save their state and restore when started later. Something like "vmware resume saved state", "pause".
• Update the titlebar from the notebook: just a little javascript wrapper function to do this.

   set_title_status("almost done!")

• Auto-updating interacts and cells (like notebook hack but official).

• Optimize fulltext search (could be moving everything to database). Use SQLalchemy? Whoosh full-text search (codenode-devel).

• Keith Lang's Top 10 UI Myths.

• Chat system for students/users - Google gadget?

• Implement %timeit block in notebook.

• Worksheet tags. (Brian Granger)

• Embed cells, including interacts, in other web pages.
• Prevent text movement by a pixel on cell frame focus. (Ondrej)
• Completions link for iphone.
• Improve the introspection / completion interface. (boothby: contrary to my previous claims, it may be possible to display a floating div below the cursor -- otherwise, I think that moving the div to the right-hand side of the screen is the right thing to do).
  • Could you please elaborate about these ideas? Google suggest?

• Notebook input bug - #6729.

• Python debugger in the notebook: basically pylons implements something like this which could be inspiring. At least try it to see their design! Check this out: https://developer.mozilla.org/En/Pylons

• Make it possible to delete published worksheets.
• Slideshow mode.
• Interactively zoom, pan, and annotate plots. SVG? Png's? FLOT? Canvas + matplotlib?

• Powerful editor with command-line history, syntax highlighting, context-sensitive completions, etc. - BeSpin.

• Syntax highlighting for published worksheets - pygmentize.

• Fix MoinMoin.

• Update some output cells after the new output arrives. For example, smoothly update Jmol via its JS interface.

• Publishing notebook pages to selected users or groups. (This *is* share, but with groups added.) -- No, publish means "read-only" too, which is part of the feature request.

• GUI plugins for math input.

• Vector graphics editing - SVG-edit.

• Account tokens:

A preliminary patch for this is available at
http://www.math.leidenuniv.nl/~wpalenst/sage/account_tokens.patch . It is a
patch against 4.1.1 with tickets 4552
('trac_4552-notebook_account_email.patch'), 6843, 6856 applied.

(TODO: add doctests, implement token-generation page to the interface added by
ticket 4135, allow enabling/disabling the token feature from that page too.)

• The 'forgot password' feature (enabled by enabling the 'email' setting of the notebook) currently allows anyone to reset the password of anyone they know the email address of, since it currently directly resets the password and mails the new password to the email address associated with the account. It would probably be better to instead generate a second password for the account, that would only become permanent once it has been used once. Or, alternatively, to email a link with a secure token to a password-change-page.
• Make it possible to use the notebook as an IDE for the instance of sage that's running.
• Make it possible to download zip files of multiple worksheets, even if accounts=True
• Make it possible for Sage servers to sync worksheets between each other (i.e., let me sync all of my worksheets on a given server, with a given username and password). This helps tremendously with keeping backup copies. Should each user directory maybe be an hg repository with the worksheet.txt files and the files in DATA checked in? That would maybe make pushing/pulling changes easier.

• Parens matching: Has there been any progress on this? http://www.mail-archive.com/sage-support@googlegroups.com/msg03975.html One of the often heard comments from lecturers is that they are wasting time on basic syntax, when students mismatch parenthesis. In the simplest instance, when a closing ] or ) is typed it helps to highlight the correct (nested or not) matching left one. See http://trac.sagemath.org/sage_trac/ticket/3646

Build / Test

• Notebook testing infrastructure - automated, cross-browser and platform, focused on functionality, consistency, concurrency, and scalability - Selenium, Testled, WebDriver. For example, execute 10 sessions of virtual calculus students in a loop. WebTest, which is included in Pylons, is what mhansen recommends.

• Make it so Sage binaries don't use SSE3, etc. -- make them FAT!
• Windows build farm.
• Sagelite - separate the current notebook from Sage. Windows port.
• Windows port.

• VirtualBox Sage.

• andLinux Sage.
• Improve documentation/testing and refactor code.