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.

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

image future directions #4301

Closed
antoinerg opened this issue Oct 24, 2019 · 8 comments
Closed

image future directions #4301

antoinerg opened this issue Oct 24, 2019 · 8 comments
Labels
feature something new

Comments

@antoinerg
Copy link
Contributor

Following the introduction of image trace type in #4289, here are a few future directions this trace type could go:

  • add support for x and y
  • add new color models
  • add optimized rendering pathway in browsers that support it by drawing the image once and rely on CSS image-rendering: pixelated to provide a pixelated view of it
@antoinerg antoinerg added the feature something new label Oct 24, 2019
@etpinard
Copy link
Contributor

  • renaming it pixmap 😄

@archmoj
Copy link
Contributor

archmoj commented Oct 24, 2019

I was wondering it might be of interest to have an option of printing numbers (or other characters) instead of drawing rectangles. Something similar to pixmap actually!
https://franz.com/support/documentation/current/doc/cg/cg-pixmaps.htm
Also that reminds me of this article http://www.cs.utah.edu/~gk/papers/vissym04/vissym04kindlmann.pdf which @nicolaskruchten showed me a while ago may be possible using vectors.

@archmoj
Copy link
Contributor

archmoj commented Oct 25, 2019

Also to metion:

@emmanuelle

This comment has been minimized.

@antoinerg

This comment has been minimized.

@emmanuelle
Copy link
Contributor

The optimized rendering pathway would be great to display large images (1000x1000 and larger) in reasonable time. I'm a big fan of adding this possibility.

@antoinerg
Copy link
Contributor Author

Commit d9a17cd shows an early example using image-rendering: pixelated.

@gvwilson
Copy link
Contributor

Hi - we are trying to tidy up the stale issues and PRs in Plotly's public repositories so that we can focus on things that are still important to our community. Since this one has been sitting for several years, I'm going to close it; if it is still a concern, please add a comment letting us know what recent version of our software you've checked it with so that I can reopen it and add it to our backlog. Thanks for your help - @gvwilson

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature something new
Projects
None yet
Development

No branches or pull requests

5 participants