Differences between revisions 6 and 7
⇤ ← Revision 6 as of 2009-09-04 00:52:38 →
Size: 4434
Editor: qed777
Comment:
← Revision 7 as of 2009-09-04 01:08:53 → ⇥
Size: 3884
Editor: qed777
Comment:
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
 * Fix sagenb.org so docstrings look right (sphinx).  * Fix sagenb.org so docstrings look right (Sphinx).
Line 14: Line 14:
    (1) replace tinymce by ReST editor?
    (2) %rest in cells, and get rest output.		     1. replace tinymce by ReST editor?
    2. %rest in cells, and get rest output.
Line 17: Line 17:
 * [[http://groups.google.com/group/sage-devel/msg/35e97a1d1cedfdfd | Document pexpect for users]].  * [[http://groups.google.com/group/sage-devel/msg/35e97a1d1cedfdfd | Document pexpect interface for users]].
Line 23: Line 23:
 * Add a textcha question for notebook signup.  * Fix the major bugs and issues with the current notebook that make it difficult to deploy (e.g., account management).
Line 25: Line 25:
 * LDAP authentication. (tdumont)  * Add a textcha question for notebook signup. How about [[http://recaptcha.net/ | reCAPTCHA]]?
Line 27: Line 27:
 * Ensure no matter what that worksheet and server are 'nsync.  * LDAP authentication. (tdumont)
Line 29: Line 29:
 * Reduce data loss possibilites -- see [[http://sage.math.washington.edu/home/wstein/tmp/sageuse/dataloss.txt | dataloss.txt]]  * Guaranteed worksheet-server synchronization.

 * Reduce data loss possibilites. ([[http://sage.math.washington.edu/home/wstein/tmp/sageuse/dataloss.txt | dataloss.txt]])
Line 33: Line 35:
 * Email address as username.that  * Email address as username.
Line 35: Line 37:
 * Add users as admins. (sage-support email to fprimex)  * Add users as admins. (fprimex)
Line 43: Line 45:
 * Ability to update the titlebar from sage notebook.  * Update the titlebar from the notebook.
Line 45: Line 47:
 * Ability for interacts to auto-update themselves.  * Auto-updating interacts.
Line 47: Line 49:
 * Whoosh fulltext search (search in codenode archives for discussion).  * Whoosh full-text search (search in codenode archives for discussion).
Line 51: Line 53:
 * Chat system for students/users.  * Chat system for students/users.  Is there a Google gadget for this?
Line 57: Line 59:
 * 1 week -- write something to make it easy to embed interacts in other web pages.   * Embed interacts in other web pages.
Line 61: Line 63:
 * iphone -- link to do completions.  * Completions link for iphone.
Line 63: Line 65:
 * Notebook input bug -- [[http://trac.sagemath.org/sage_trac/ticket/6729 | #6729]]  * Notebook input bug [[http://trac.sagemath.org/sage_trac/ticket/6729 | #6729]].
Line 65: Line 67:
 * Debugger in the notebook.

 * Somebody published a irrelevant worksheet (to test the button) and wanted to cancel it but he was not able. He then delete its worksheet, but apparently the worksheet was still published...:(		  * Debugger in the notebook. Python.
Line 75: Line 75:
 * What I mean is that the chance to access at the same time an history powered command line, and a powerful editor (with code completion, tabs, colors, etc.., which looks pretty standard - to not say minimal - in these modern times) looks pretty comfortable to me, but I'll be happy to listen to other comments. I've already heard talking about BeSpin ( https://bespin.mozilla.com/ ) in this list, right? Can't we have something similar? :)  * What I mean is that the chance to access at the same time an history powered command line, and a powerful editor (with code completion, tabs, colors, etc.., which looks pretty standard - to not say minimal - in these modern times) looks pretty comfortable to me, but I'll be happy to listen to other comments. I've already heard talking about !BeSpin ( https://bespin.mozilla.com/ ) in this list, right? Can't we have something similar? :)
Line 77: Line 77:
 * Fix MoinMoin  * Fix !MoinMoin.
Line 81: Line 81:
 * Implement a cross-browser web-application testing infrastructure based on webdriver http://code.google.com/p/webdriver/ for the notebook, focused on functionality, consistency and concurrency. For example, execute 10 sessions of virtual calculus students in a loop. tags: google <- for funding? notebook java stresstest Money? Don't know, motivated student who has learned webdesign, java and probably python.  * Implement a cross-browser web-application automated testing infrastructure based on webdriver http://code.google.com/p/webdriver/ for the notebook, focused on functionality, consistency, concurrency, and scalability. For example, execute 10 sessions of virtual calculus students in a loop.
Line 85: Line 85:
 * Make it so sage binaries don't use ssse3, etc. -- make them FAT!  * Make it so Sage binaries don't use SSE3, etc. -- make them FAT!
Line 87: Line 87:
 * Windows server farm  * Windows server farm.
Line 89: Line 89:
 * 1 week -- write code to do automated testing of the scalability of the Sage (or any) notebook system  * Sagelite - separate the current notebook from Sage and get it to run on Windows.
Line 91: Line 91:
 * 1 week -- get the current notebook separated out from Sage 100% for real and get it to work on windows. (this is sagelite).  * Windows port.
Line 93: Line 93:
 * 1 month -- the windows port  * !VirtualBox Sage.
Line 95: Line 95:
 * 2 days -- VirtualBox Sage  * andLinux Sage.
Line 97: Line 97:
 * 2 days -- andLinux Sage

 * 1 month -- fix the major bugs and issues with the current notebook that make it difficult to deploy (e.g., account management).

 * 1 week -- improve documentation/testing and refactor code.		  * Improve documentation/testing and refactor code.

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

Notebook

Admin

  • Fix the major bugs and issues with the current notebook that make it difficult to deploy (e.g., account management).

  • Add a textcha question for notebook signup. How about reCAPTCHA?

  • LDAP authentication. (tdumont)
  • Guaranteed worksheet-server synchronization.

  • Reduce data loss possibilites. (dataloss.txt)

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

Users

  • Reorganize the notebook help page.
  • Automatically have worksheets save their state and restore when started later.
  • Update the titlebar from the notebook.
  • Auto-updating interacts.
  • Whoosh full-text search (search in codenode archives for discussion).

  • Keith Lang's Top 10 UX Myths.

  • Chat system for students/users. Is there a Google gadget for this?
  • Implement %timeit block in notebook.

  • Worksheet tags. (Brian Granger)

  • Embed interacts in other web pages.
  • There are things that I now don't like on the Sage notebook, like that if I click on a cell, the frame gets focused (that's ok), but the text moves by one pixel. I hate that. My javascript version doesn't do that, at least on firefox. In fact, it's just a CSS styles issue, so it's easy to fix -- but I wasn't sure if it's just on my firefox, or oeverywhere. (ONDREJ)
  • Completions link for iphone.

  • Notebook input bug #6729.

  • Debugger in the notebook. Python.
  • Make it possible to delete published worksheets.
  • Slideshow mode.
  • In-browser zoom-pan-annotate of Sage plots.

  • What I mean is that the chance to access at the same time an history powered command line, and a powerful editor (with code completion, tabs, colors, etc.., which looks pretty standard - to not say minimal - in these modern times) looks pretty comfortable to me, but I'll be happy to listen to other comments. I've already heard talking about BeSpin ( https://bespin.mozilla.com/ ) in this list, right? Can't we have something similar? :)

  • Fix MoinMoin.

Build / Test

  • Implement a cross-browser web-application automated testing infrastructure based on webdriver http://code.google.com/p/webdriver/ for the notebook, focused on functionality, consistency, concurrency, and scalability. For example, execute 10 sessions of virtual calculus students in a loop.

  • http://testled.com/

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

  • VirtualBox Sage.

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