-
Notifications
You must be signed in to change notification settings - Fork 2
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
support for image file drivers #8
Comments
There my thoughts.
I have written wrappers for the pipe functionality in my GDlib wrapper and I am willing to help here when I have time |
If it is OK for you, I'll try to implement the PPM reader subroutine. Concerning the discussion external dependencies, there is an interesting post on the |
Sure, feel free to do it.
I'm really still hesitant about external dependencies. I was thinking, maybe for PNG, since implementing it all from scratch will be a lot of pain, I will use a deflating library to help. I found two options:
But still, I would like to at least try doing it all from scratch first. That's why I will leave PNG support for last. |
OK, I wish you a lot of success for your midterms! I will also get quiet in the next few weeks You can still ping me when you want. Cheers, |
Yeah, I intend for the support to be both read and write.
I agree.
Whenever you are free, feel free to do it if you want. I am not experienced with implementing piping, so I will need to do more research in the future if I implement it myself. thank you. |
I've decided on how I'll implement the image drivers. I'll work on creating Fortran bindings for some of the stb headers (https://github.com/nothings/stb). I'll do this in another repo to make it convenient for anyone who might need it standalone. Then, I'll depend on it here so that fig supports BMP and PNG formats. |
I did not know about these libraries. They are really interesting (and compatible to the MIT license). Still, I think we should keep the PPM support in the core library. |
i agree, |
I think now stabilizing the structure of the library has priority, so I do not think I will create pull requests concerning the file input/output until a somewhat stable state has been reached. |
I am wondering how the drivers for the bitmap canvas should be implemented.
Of course, these approaches are not mutably exclusive. |
I was thinking of keeping them as methods of the canvas. I can't see how separate functions would be beneficial in the current design. |
So far, the library only supports writing to PPM.
I plan to add support for other popular image formats. The initial target formats are BMP, PNG, and GIF, with consideration for additional formats in the future.
Feel free to contribute to any of the mentioned tasks or propose other file formats.
The text was updated successfully, but these errors were encountered: