Changes between Version 157 and Version 158 of Ticket #9238


Ignore:
Timestamp:
06/16/11 15:42:50 (10 years ago)
Author:
gutow
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9238 – Description

    v157 v158  
    11Ready for testing.
     2
     3For inclusion in new Flask notebook see: #11080
    24
    35Setting this up on your own copy of Sage requires two steps.  Starting with a clean Sage 4.6.2 (for 4.7+ skip step 1): [[BR]]
    46
    57 1. Patch for Jmol at the command line (not for 4.7+). See [http://trac.sagemath.org/sage_trac/ticket/9232 #9232].
    6  1. Apply the .spkg to get the new Jmol {{{ ./sage -f "http://www.uwosh.edu/faculty_staff/gutow/Jmol_for_SageNoteBook-1.1.6.spkg"}}}
     8 1. Apply the .spkg to get the new Jmol ` ./sage -f "http://www.uwosh.edu/faculty_staff/gutow/Jmol_for_SageNoteBook-1.1.6.spkg"`
    79 1. Apply the following patches in order (not necessary for Flask): [attachment:trac_9238_interactive_js.patch], [attachment:trac_9238-add-help.patch] , [attachment:trac_9238_jmol_lib_async.patch],  [attachment:trac_9238_memory_IE.patch] and [attachment:trac_9238_nice_IE_warnings.patch]. These are best applied using the hg_sagenb.apply(...) command within sage.
    8  1. Apply the patch (not necessary for 4.7+) [attachment:Trac_9238_script_extension.patch] using the hg_sage.apply(...) command within sage.   Exit sage and run a {{{ ./sage -b}}}.
     10 1. Apply the patch (not necessary for 4.7+) [attachment:Trac_9238_script_extension.patch] using the hg_sage.apply(...) command within sage.   Exit sage and run a ` ./sage -b`.
    911
    1012I have addressed the following issues (let me know if I've missed anything): [[BR]]