#9238: J. Gutow's update to Jmol in the notebook...
---------------------------+------------------------------------------------
   Reporter:  gutow        |       Owner:  jason, was
       Type:  enhancement  |      Status:  new       
   Priority:  major        |   Milestone:  sage-4.4.4
  Component:  notebook     |    Keywords:            
     Author:               |    Upstream:  N/A       
   Reviewer:               |      Merged:            
Work_issues:               |  
---------------------------+------------------------------------------------

Comment(by gutow):

 Replying to [comment:19 kcrisman]:
 > Sweet.  Great work!
 Glad you like it.
 >
 > Some comments upon a very small amount of testing (which is all I have
 time for right now).  I apologize for their telegraphic nature.
 >
 > Popup 3dviewer is great.
 >
 > Functions tab did not immediately have something in it, I had to click
 "request...", which is nonintuitive.  I understand if that step is
 necessary, but the message could be better; as it is, the person using it
 wouldn't necessarily realize that this would give mesh etc. info for each
 object (nice to do it separately, so so so nice).
 >
 You are correct that I could not originally get the information from Jmol
 on load because of timing issues.  I have an idea about this and will work
 on it a little.  In the meantime, I think you are correct that we need
 better instructions in this tab.
 > Colorpicker in Functions tab: awesome.
 We use it for other Jmol stuff, but it was originally inspired by the
 needs of SAGE.
 >
 > Initial size Small might be good for iPhone (if Jmol even works there?)
 but is a little on the small side for normal laptop/PC web browsing.   Can
 the browsing thing be detected for this?
 >
 I believe we can get the surrounding window size.  I will look into that.
 Maybe it should default to no more than 405 of width or height, whichever
 is higher?

 > There is an awful lot of space given to the info, not so much to the
 actual graphic.  Would it be possible to put that stuff below the image as
 opposed to on the right?  In fact, that stuff should not necessarily
 resize with the graphic...
 >
 I can play with the table formatting a little. I don't see any problems
 off the top of my head with it not resizing. I think underneath is a
 problem as the applet can be big enough that the controls will be off
 screen.

 > State is cool for those of us who might want to access it, but it should
 default (when clicked upon) to creating a slider or something, or "click
 here for full" or something like that.  Otherwise the potential for really
 upsetting work flow is there, it changes the window size so much.
 >
 Eventually I want it hidden.  But I think I can set it up to be
 scrolling....

 > Sleep/Wake works great, might be nice to CSS those words into something
 less \texttt{}-ish.  Note that "Arbitrarily resizable in own window Get
 static image to save" looks like one command; maybe some <ul></ul> useful
 here?
 >
 These are formatting issues that I can deal with easily.

 > Didn't break any old worksheets, though they all have this new little
 Jmol double window now, which makes sense.
 >
 Good!

 > This may be unrelated, but the axes seem to be in the wrong spots, at
 least in
 > {{{
 > var('y')
 > P=plot3d(x^2+y^2,(x,-3,3),(y,-3,3))
 > Q=plot3d(sin(x^2+y^2),(x,-3,3),(y,-3,3))
 > show(P+Q)
 > }}}
 >
 That is likely to be a SAGE python bug as Jmol just draws lines where SAGE
 tells it to.  I will double check the parsing, but since the axes look
 correct for everything I've tried, I'm guessing something funny is passed
 to Jmol.

 > I did *not* get to test having billions of applets open at the same
 time, unfortunately, but will be happy to do so if no one else can over
 the next week or two.
 >
 > One really interesting thing is this.  We had complaints about the
 snappiness of 3D interacts recently, but now I get almost instantaneous
 recomputation with 'small', which is great.

 This is because I switched to using the incrementally loaded applet.  Thus
 only the parts needed are loaded.  This significantly reduces load time.


 However
 > {{{
 > TypeError: Result of expression '(stateStr.match(re_modelinline))'
 [null] is not an object.
 > }}}
 > occurs if I change the size in an interact, and then move the slider.
 Obviously, other things don't stay the same with an interact - say if I
 change one function to green, it goes back to blue after moving the
 slider, but there shouldn't be the error message (ideally).
 >
 Is that completely reproducible?  I've seen it occasionally when
 javascript gets executed before the applets are completely loaded.
 However, I've never seen any ill effects since things get reset later.  If
 it causes problems and you can pin it down, let me know.

 Thanks for the initial testing.

 Jonathan

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9238#comment:22>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to