Differences between revisions 5 and 11 (spanning 6 versions)
⇤ ← Revision 5 as of 2009-09-04 00:45:43 →
Size: 4571
Editor: qed777
Comment:
← Revision 11 as of 2009-09-04 17:24:30 → ⇥
Size: 5245
Editor: was
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
 * [[http://groups.google.com/group/sage-devel/msg/e86932eeadd88c6a | latex doc mode]]  * [[http://groups.google.com/group/sage-devel/msg/e86932eeadd88c6a | LaTeX doc mode]].
Line 9: Line 9:
 * [[http://groups.google.com/group/sage-devel/browse_thread/thread/8fa0d854b6928f2b/dc4cfe0a941762aa#dc4cfe0a941762aa | back tick versus $]] suggestion is to patch Sphinx itself  * [[http://groups.google.com/group/sage-devel/browse_thread/thread/8fa0d854b6928f2b/dc4cfe0a941762aa#dc4cfe0a941762aa | reST back ticks versus $]] - Patch or extend Sphinx.
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?
      * You might be able to make TinyMCE *be* a ReST editor. See [[http://tinymce.moxiecode.com/examples/example_09.php#|this example]] of making TinyMCE into a BBCode editor.
Line 17: Line 17:
 * [[http://groups.google.com/group/sage-devel/msg/35e97a1d1cedfdfd | document pexpect users]]     2. %rest in cells, and get rest output.

 * [[http://groups.google.com/group/sage-devel/msg/35e97a1d1cedfdfd | Document pexpect interface for users]].
Line 23: Line 25:
 * add a textcha question for sage 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 27:
 * LDAP authentication. (tdumont)  * Add a textcha question for notebook signup. How about [[http://recaptcha.net/ | reCAPTCHA]]?
Line 27: Line 29:
 * ensure no matter what that worksheet and server are 'nsync  * LDAP authentication. (tdumont)
Line 29: Line 31:
 * reduce data loss possibilites -- see [[http://sage.math.washington.edu/home/wstein/tmp/sageuse/dataloss.txt | dataloss.txt]]  * Guaranteed worksheet-server synchronization.
Line 31: Line 33:
 * "I am running sage in one of our department servers, so that my students can use them. If my students lose their password, how can I recover it for them? Thanks." (Byungchul Cha)  * Reduce data loss possibilites. ([[http://sage.math.washington.edu/home/wstein/tmp/sageuse/dataloss.txt | dataloss.txt]])
Line 33: Line 35:
 * make it so username is email address -- i really like that  * Recover passwords. (Byungchul Cha)
Line 35: Line 37:
 * add users as admin -- see sage-support email to fprimex  * Email address as username.

 * Add users as admins. (fprimex)
Line 39: Line 43:
 * reorganize the notebook help page  * 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.
}}}
Line 41: Line 54:
 * automatically have worksheets save their state and restore when started later.  * Account approval:
{{{
> 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?
}}}
Line 43: Line 63:
 * ability to update the titlebar from sage notebook  * Reorganize the notebook help page.
Line 45: Line 65:
 * ability for interacts to auto-update themselves  * Automatically have worksheets save their state and restore when started later.
Line 47: Line 67:
 * Whoosh fulltext search (search in codenode archives for discussion)  * Update the titlebar from the notebook.
Line 49: Line 69:
 * Keith Lang "Top 10 UX Myths"; http://carsonified.com/blog/design/top-10-ux-myths/  * Auto-updating interacts.
Line 51: Line 71:
 * chat system for students/users  * Whoosh full-text search (search in codenode archives for discussion).
Line 53: Line 73:
 * implement %timeit block in notebook  * [[http://carsonified.com/blog/design/top-10-ux-myths/ | Keith Lang's Top 10 UI Myths]].
Line 55: Line 75:
 * [[http://groups.google.com/group/sage-devel/browse_thread/thread/e46f0a59d5cf70dc | tags]] (Brian Granger)  * Chat system for students/users. Is there a Google gadget for this?
Line 57: Line 77:
 * 1 week -- write something to make it easy to embed interacts in other web pages  * Implement %timeit block in notebook.

 * [[http://groups.google.com/group/sage-devel/browse_thread/thread/e46f0a59d5cf70dc | Worksheet tags]]. (Brian Granger)

 * Embed interacts in other web pages.
Line 61: Line 85:
 * iphone -- link to do completions  * Completions link for iphone.
Line 63: Line 87:
 * notebook input bug -- http://trac.sagemath.org/sage_trac/ticket/6729  * Notebook input bug [[http://trac.sagemath.org/sage_trac/ticket/6729 | #6729]].
Line 65: Line 89:
 * debugger in the notebook  * Debugger in the notebook. Python.
Line 67: Line 91:
 * 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...:(  * Make it possible to delete published worksheets.
Line 69: Line 93:
 * make it possible to delete published worksheets.  * Slideshow mode.
Line 71: Line 95:
 * slideshow mode  * In-browser zoom-pan-annotate of Sage plots.
Line 73: Line 97:
 * 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? :)
Line 75: Line 99:
 * 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.
Line 77: Line 101:
 * fix moinmoin  * Publishing notebook pages to selected users or groups (to make this effective, groups of users probably needs to be implemented as well).

 * GUI plugins for inputing mathematics. See the thread http://article.gmane.org/gmane.comp.mathematics.sage.devel/27294/

 * SVG editing: http://code.google.com/p/svg-edit/
Line 81: Line 109:
 * 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 113:
 * 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 115:
 * windows server farm  * Windows server farm.
Line 89: Line 117:
 * 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 119:
 * 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 121:
 * 1 month -- the windows port  * !VirtualBox Sage.
Line 95: Line 123:
 * 2 days -- VirtualBox Sage  * andLinux Sage.
Line 97: Line 125:
 * 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

  • 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: 

> 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?
  • 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 UI 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.

  • Publishing notebook pages to selected users or groups (to make this effective, groups of users probably needs to be implemented as well).

  • GUI plugins for inputing mathematics. See the thread http://article.gmane.org/gmane.comp.mathematics.sage.devel/27294/

  • SVG editing: http://code.google.com/p/svg-edit/

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.