Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Refactor graphics / graphics array #18033

Open
vbraun opened this issue Mar 21, 2015 · 4 comments
Open

Refactor graphics / graphics array #18033

vbraun opened this issue Mar 21, 2015 · 4 comments
Labels
c: graphics p: major / 3 s: needs info wishlist item

Comments

@vbraun
Copy link
Member

vbraun commented Mar 21, 2015

In graphics.py, a bit of refactoring could be done
by creating a common parent for Graphics
and GraphicsArray (maybe something like GraphicsBase).

Various show methods should maybe get moved to the
SageObject class, or perhaps in some category.

Depends on #17821

CC: @novoselt @slel

Component: graphics

Issue created by migration from https://trac.sagemath.org/ticket/18033
@vbraun vbraun added this to the sage-6.6 milestone Mar 21, 2015
@vbraun
Copy link
Member Author

vbraun commented Mar 21, 2015

Dependencies: #17821

@vbraun

This comment has been minimized.

Sign in to view
@slel
Copy link
Member

slel commented May 2, 2021

comment:4

If #27865 solved this, set the ticket's milestone
to sage-duplicate/invalid/wontfix, so we can close.

Otherwise, it would be good to assess more precisely
what is left to do here.

@slel

This comment has been minimized.

Sign in to view
@slel slel added s: needs info and removed t: bug labels May 2, 2021
@slel slel removed this from the sage-6.6 milestone May 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c: graphics p: major / 3 s: needs info wishlist item
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vbraun @slel