On Sun, Jan 18, 2015 at 6:44 PM, Jonathan <[email protected]> wrote:
> Yep, polytopes.blah().show(), is fine although I do not like the default
> green as much (It was chosen to differentiate it from the lines and
> vertices, I assume).  Yes, I think this is as good or better.  Should we put
> a ticket to simply make the regular solid calls go to polytope.blah.show().
> I'm not sure how else they are being used.
>
> I also wonder if the vertex bug is hiding in these as well?
>
> Now, for the reason I encountered the bug...I was goofing around (I needed a
> break from reviewing proposals) trying to make my 3-D version of the logo (a
> few years back :) ) adaptable.  It looks like most of what I want is
> available here.  The problem is I never would have found them without the
> above pointers.
>
> ASIDE: if you start with "geometry." or "sage.geometry." and start working
> through tab completion I am not sure you would ever get to the construction
> polytopes.blah().show() for the regular solids. You don't get to the regular
> solids until "sage.geometry.polyhedron.library.Polytopes.blah().  Why would
> I guess that I can shorten the call to "polytopes.blah().show()?  Why does
> polytopes (part of geometry) show up as a root level class?  I'm beginning
> to think a committee needs to be tasked with restructuring the class
> hierarchy so that things can be found.  Sagemath is actually quite
> wonderful, but it can be hard to find what you want.

I would guess that most people find functionality in Sage by searching
with google (or whatever, or even the search_doc function), not via
tab completing little by little.   I certainly would never consider
trying to find anything that way.

Instead of a committee to break all the code anybody ever wrote for
Sage (which would be undesirable, akin to Python2 --> Python3),
instead effort would be much better spent in making it easier to do a
global search of the documentation and functionality.   I'm sure that
could be improved a lot.  It would be interesting to hear ideas along
those lines.

Anyway, I'm generally on principle against changing things about the
sage library that breaks existing code, except fixing bugs, since I
care a lot about users.

 -- William


>
> Jonathan
>
> On Sunday, January 18, 2015 at 8:21:40 PM UTC-6, William wrote:
>>
>> On Sun, Jan 18, 2015 at 6:16 PM, William Stein <[email protected]> wrote:
>> > On Sun, Jan 18, 2015 at 6:03 PM, Jonathan <[email protected]> wrote:
>> >> OK...I haven't checked yet, but I'll bet show on all the polyhedra
>> >> primatives does something similar.
>> >
>> > Sort of, though it's significantly different than what the 3d plotting
>> > produces.  polytopes.blah.show()
>> > makes a 3d graphic with edges and dots at vertices, etc...  so it
>> > looks a lot different (maybe better).
>> >
>> >> Re: Williams comment that we would have to deprecate it...could we
>> >> effectively subsume it in the geometry types, while keeping the name
>> >> and
>> >> behavior?
>> >
>> > Yes, that should likely possible and would be very desirable.
>> >
>> >> Do the polyhedra know about their symmetry?
>> >
>> > I don't think so -- they are just used for plotting.
>> >
>> >>  That would be a nice
>> >> way of leading people to those tools?
>> >
>> > Yes, definitely.
>> >
>> > (NOTE: In case anybody tries, plotting of dodecahedrons in particular
>> > is currently broken/not implemented in SageMathCloud, since it
>> > involves polytopes defined by faces that have many vertices, and the
>> > renderer doesn't cover that case.)
>> >
>> >>
>> >> Jonathan
>> >>
>> >>
>> >> On Sunday, January 18, 2015 at 7:44:25 PM UTC-6, Volker Braun wrote:
>> >>>
>> >>> I can confirm the bug. Note that the output of "dodecahedron()" is not
>> >>> a
>> >>> Polyhedron, its just a 3d graphics primitive:
>> >>>
>> >>> sage: type(dodecahedron())
>> >>> <type 'sage.plot.plot3d.index_face_set.IndexFaceSet'>
>> >>>
>> >>> vs:
>> >>>
>> >>> sage: type(polytopes.dodecahedron())
>> >>> <class
>> >>>
>> >>> 'sage.geometry.polyhedron.backend_ppl.Polyhedra_QQ_ppl_with_category.element_class'>
>> >>>
>> >>> IMHO the current dodecahedron should just be deleted, or at least
>> >>> removed
>> >>> from the global namespace.
>> >>>
>> >>>
>> >>>
>> >>> On Monday, January 19, 2015 at 1:28:11 AM UTC+1, Jonathan wrote:
>> >>>>
>> >>>> sage: DD=dodecahedron()
>> >>>> sage: print "length of vertex list:"+str(len(DD.vertex_list()))
>> >>>> length of vertex list:20
>> >>>> sage: DD.show()
>> >>>> sage: print "length of vertex list:"+str(len(DD.vertex_list()))
>> >>>> length of vertex list:60
>> >>>>
>> >>>>
>> >>>>
>> >>>> Somehow the show command is causing the verticies to be appended to
>> >>>> the
>> >>>> vertex_list two extra times.  If others can verify, I will report a
>> >>>> bug and
>> >>>> we can start looking for this...
>> >>>>
>> >>>> I've seen this on multiple running cases of 6.4.rc1 and 6.4.
>> >>>>
>> >>>> Thanks,
>> >>>> Jonathan
>> >>
>> >> --
>> >> You received this message because you are subscribed to the Google
>> >> Groups
>> >> "sage-devel" 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-devel.
>> >> For more options, visit https://groups.google.com/d/optout.
>> >
>> >
>> >
>> > --
>> > William Stein
>> > Professor of Mathematics
>> > University of Washington
>> > http://wstein.org
>>
>>
>>
>> --
>> William Stein
>> Professor of Mathematics
>> University of Washington
>> http://wstein.org
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" 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-devel.
> For more options, visit https://groups.google.com/d/optout.



-- 
William Stein
Professor of Mathematics
University of Washington
http://wstein.org

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" 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-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to