Differences between revisions 1 and 6 (spanning 5 versions)
Revision 1 as of 2009-09-04 00:18:32
Size: 4813
Editor: qed777
Comment: Import http://sage.math.washington.edu/home/wstein/tmp/sageuse/
Revision 6 as of 2009-09-04 00:52:38
Size: 4434
Editor: qed777
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Sage Usability Improvements List =
Adapted from [[http://sage.math.washington.edu/home/wstein/tmp/sageuse/ | this repository]].
= Sage Usability Improvements =

This unofficial wish list is a
dapted from [[http://sage.math.washington.edu/home/wstein/tmp/sageuse/ | this repository]].  Please feel free to add or clarify ideas, link to trac tickets, make comments, reorganize items, point out useful links, etc.
Line 6: 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 8: Line 9:
 * [[http://groups.google.com/group/sage-devel/browse_thread/thread/8fa0d854b6928f2b/dc4cfe0a941762aa#dc4cfe0a941762aa | back tick versus $]]-- see sage-devel discussion I started on sept 3; suggestion is to patch Sphinx itself.
 * fix sagenb.org so docstrings look right (sphinx)
 * [[http://groups.google.com/group/sage-devel/browse_thread/thread/8fa0d854b6928f2b/dc4cfe0a941762aa#dc4cfe0a941762aa | reST back ticks versus $]] - Patch or extend Sphinx.

 * Fix sagenb.org so docstrings
look right (sphinx).
Line 13: Line 16:
 * [[http://groups.google.com/group/sage-devel/msg/35e97a1d1cedfdfd | document pexpect users]]
* [[http://groups.google.com/group/sage-devel/msg/35e97a1d1cedfdfd | Document pexpect for users]].
Line 19: Line 23:
 * add a textcha question for sage notebook signup  * Add a textcha question for notebook signup.
Line 21: Line 25:
 * LDAP authentication. Suggested by
"[email protected]
Hello,
I am *very* interested. I am supposed to start a Sage server for *all*
the undergraduate students of my University (at least those learning
maths and computer sciences or physics). My contribution is very small:
add ldap identification, run a server on 3 "large" machines.
Yours
t.d.
"
 * ensure no matter what that worksheet and server are 'nsync
 * LDAP authentication. (tdumont)
Line 33: Line 27:
 * reduce data loss possibilites -- see dataloss.txt  * Ensure no matter what that worksheet and server are 'nsync.
Line 35: Line 29:
 * Byungchul Cha <[email protected]>: "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."  * Reduce data loss possibilites -- see [[http://sage.math.washington.edu/home/wstein/tmp/sageuse/dataloss.txt | dataloss.txt]]
Line 37: Line 31:
 * make it so username is email address -- i really like that  * Recover passwords. (Byungchul Cha)
Line 39: Line 33:
 * add users as admin -- see sage-support email to fprimex<[email protected]>  * Email address as username.that

 * A
dd users as admins. (sage-support email to fprimex)
Line 43: Line 39:
 * reorganize the notebook help page  * Reorganize the notebook help page.
Line 45: Line 41:
 * automatically have worksheets save their state and restore when started later.  * Automatically have worksheets save their state and restore when started later.
Line 47: Line 43:
 * ability to update the titlebar from sage notebook  * Ability to update the titlebar from sage notebook.
Line 49: Line 45:
 * ability for interacts to auto-update themselves  * Ability for interacts to auto-update themselves.
Line 51: Line 47:
 * Whoosh fulltext search (search in codenode archives for discussion)  * Whoosh fulltext search (search in codenode archives for discussion).
Line 53: Line 49:
 * Keith Lang "Top 10 UX Myths"; http://carsonified.com/blog/design/top-10-ux-myths/  * [[http://carsonified.com/blog/design/top-10-ux-myths/ | Keith Lang's Top 10 UX Myths]].
Line 55: Line 51:
 * chat system for students/users  * Chat system for students/users.
Line 57: Line 53:
 * implement %timeit block in notebook  * Implement %timeit block in notebook.
Line 59: Line 55:
 * [[http://groups.google.com/group/sage-devel/browse_thread/thread/e46f0a59d5cf70dc | tags ]]-- see file tags.txt  * [[http://groups.google.com/group/sage-devel/browse_thread/thread/e46f0a59d5cf70dc | Worksheet tags]]. (Brian Granger)
Line 61: Line 57:
 * 1 week -- write something to make it easy to embed interacts in other web pages (needed for the frg, imho -- may start this at Lopez).  * 1 week -- write something to make it easy to embed interacts in other web pages.
Line 63: Line 59:
ONDREJ:
. 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.
 * 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)
Line 66: Line 61:
 * iphone -- link to do completions  * iphone -- link to do completions.
Line 68: Line 63:
 * notebook input bug -- http://trac.sagemath.org/sage_trac/ticket/6729  * Notebook input bug -- [[http://trac.sagemath.org/sage_trac/ticket/6729 | #6729]]
Line 70: Line 65:
 * debugger in the notebook  * Debugger in the notebook.
Line 74: Line 69:
 * make it possible to delete published worksheets.  * Make it possible to delete published worksheets.
Line 76: Line 71:
 * slideshow mode  * Slideshow mode.
Line 78: Line 73:
 * in-browser zoom-pan-annotate of Sage plots  * In-browser zoom-pan-annotate of Sage plots.
Line 82: Line 77:
 * fix moinmoin  * Fix MoinMoin
Line 90: Line 85:
 * make it so sage binaries don't use ssse3, etc. -- make them FAT!  * Make it so sage binaries don't use ssse3, etc. -- make them FAT!
Line 92: Line 87:
 * windows server farm  * Windows server farm

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

  • Add a textcha question for notebook signup.
  • LDAP authentication. (tdumont)
  • Ensure no matter what that worksheet and server are 'nsync.
  • Reduce data loss possibilites -- see dataloss.txt

  • Recover passwords. (Byungchul Cha)
  • Email address as username.that
  • Add users as admins. (sage-support email to fprimex)

Users

  • Reorganize the notebook help page.
  • Automatically have worksheets save their state and restore when started later.
  • Ability to update the titlebar from sage notebook.
  • Ability for interacts to auto-update themselves.
  • Whoosh fulltext search (search in codenode archives for discussion).
  • Keith Lang's Top 10 UX Myths.

  • Chat system for students/users.
  • Implement %timeit block in notebook.
  • Worksheet tags. (Brian Granger)

  • 1 week -- write something to make it easy to 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)
  • iphone -- link to do completions.
  • Notebook input bug -- #6729

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

  • http://testled.com/

  • Make it so sage binaries don't use ssse3, etc. -- make them FAT!
  • Windows server farm
  • 1 week -- write code to do automated testing of the scalability of the Sage (or any) notebook system
  • 1 week -- get the current notebook separated out from Sage 100% for real and get it to work on windows. (this is sagelite).
  • 1 month -- the windows port
  • 2 days -- VirtualBox Sage

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