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

Current status of graphics library development. #15413

Closed
JimBobSquarePants opened this issue Oct 12, 2015 · 6 comments
Closed

Current status of graphics library development. #15413

JimBobSquarePants opened this issue Oct 12, 2015 · 6 comments
Labels
area-System.Drawing question Answer questions and provide assistance, not an issue with source code or documentation.
Milestone

Comments

@JimBobSquarePants
Copy link

Hi all,
I've been following the various conversations regarding graphics in corefx: #14503, #13999, etc and also following the progress of the library in corefxlab https://github.com/dotnet/corefxlab/tree/master/src/System.Drawing.Graphics and I'm still left wondering what the overall plan is. Progress in the lab repo seems to have stopped and there seems to be no further discussion I can find anywhere on what is happening.

I'm the primary author of the project ImageProcessor which I wrote to make System.Drawing a little easier to work with. It's been fairly successful in adoption but as far as I can fathom my work (~3 years) will become obsolete very soon.

Since corefx was announced I've started working on a library which can do basic stuff like encode/decode pngs, bmps, jpegs, and gifs (animated too), I've partially implemented some primitives for shapes and colors, and am experimenting with resampling algorithms now.

All that work can be found here

I'm super uneasy about doing all this work though as I don't want it to be in vain, superseded immediately by something out of Microsoft. Should I continue? If so is it something that you would think the community could invest in and help me deliver (Graphics is tricky stuff and I'm no computer scientist).

@joshfree
Copy link
Member

/cc @terrajobst @dsplaisted @Priya91

@JimBobSquarePants
Copy link
Author

Hello?

@ikourfaln
Copy link

so ?!!

@alexperovich
Copy link
Member

@terrajobst do we have any plans in this area?

@karelz
Copy link
Member

karelz commented Nov 10, 2016

@JimBobSquarePants very sorry for the extra delay. We are finally getting to proper triage of all issues on GitHub.
To my knowledge we do not have any immediate or medium-term plans to create new libraries. Definitely not unless there is a high demand from customers.
I think that it is a great thing that you have a library which is used. I would recommend you to keep working on it. If we ever go into graphics library space, we should try to look for existing solutions first (at least I would).

If you have any feedback on CoreFX from your point of view and if you think that some of your types should move to the platform, please let us know.

Closing for now as the question was (finally) answered :).

@karelz karelz closed this as completed Nov 10, 2016
@JimBobSquarePants
Copy link
Author

Thanks @karelz I appreciate it.

We've been making excellent progress so far with my xPlat library now called ImageSharp and would welcome any input from anyone interested in the subject.

@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the 2.0.0 milestone Jan 31, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Jan 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Drawing question Answer questions and provide assistance, not an issue with source code or documentation.
Projects
None yet
Development

No branches or pull requests

7 participants