#12212: Colormap for implicit_plot3d and parametric_plot3d
-------------------------------------+-------------------------------------
       Reporter:  niles              |        Owner:  jason, was
           Type:  defect             |       Status:  needs_work
       Priority:  major              |    Milestone:  sage-6.4
      Component:  graphics           |   Resolution:
       Keywords:  colormap, plot     |    Merged in:
        Authors:  Joris              |    Reviewers:  Frédéric Chapoton,
  Vankerschaver, Frédéric Chapoton   |  Niles Johnson
Report Upstream:  N/A                |  Work issues:
         Branch:  u/chapoton/12212   |       Commit:
   Dependencies:                     |  0ae10f534826c0addaf4d957bf7c0586ba0a88c4
                                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by kcrisman):

 I think I agree now that there is no real reason for the global texture
 thing, there should be a way to just use that color if it's available.
 > Yeah, mainly the `colordata` tuple, but I think it's a symptom of some
 deeper organization issues.
 I think I dug up another one of your qualms next.
 >  If I understand correctly, this is a fundamental limitation of this
 approach, because it applies colors only *after* the surface is
 constructed and therefore only has access to coordinates in 3-space, not
 the parametrization that was used to produce them.

 But I don't know that these are insurmountable.  I mean, how else
 ''could'' one give not just a cmap/color, but also a way to actually
 allocate it?  I guess one could require using it post-hoc like in
 texture_map.py but I don't think that is necessary.

 Also, I have now actually read through a lot more of the code as a whole.
 I see three things.
  * Awesome added (needed) documentation and cleanup everywhere, very nice
  * Joris' original texture map file, which seems to be used nowhere else
 and allows one to apply such a transform ''after'' creating a graphics
 object
  * chapoton's impressive direct additions of this functionality to things
 ''while'' creating the object

--
Ticket URL: <http://trac.sagemath.org/ticket/12212#comment:67>
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to