-
Notifications
You must be signed in to change notification settings - Fork 13
mavenized JavaFrameBuffer providing direct-write BufferedImage backed by linux framebuffer #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
base: master
Are you sure you want to change the base?
Conversation
Conflicts: framebuffer/src/main/c/FrameBuffer.c framebuffer/src/main/java/org/tw/pi/framebuffer/FrameBuffer.java
…eature/api-modification
This reverts commit b6b4aa8.
…e written value differs from the cache. Only read from the cache.
|
This is so cool, thank you so much :) |
|
Yikes, looks like this pull request kept following a branch after I submitted it. I'll have to fix that. |
|
Is it good to checkout? I was going to work with this sometime today if you need something cleaned up |
|
Yeah it works just fine. There's just a raspberry pi clock in src/test/java that I was developing for my five year old, which added a ton of commits unrelated to mavenization. |
|
Oh no prob, thanks again :) |
I forked this project, stole a bunch of the JNI, but everything else is a near total rewrite.
It builds using Apache Maven, and works great on my raspberry pi with one of those TFT displays on /dev/fb1.
Provides a java.awt.image.BufferedImage whose DataBuffer provides direct and immediate read/write access to the linux framebuffer; no more background threads flushing writes since all changes are immediate.
Sample use is to grab a java.awt.Graphics from a FrameBufferedImage and start painting pretty pictures on your pi's TFT.
Should in theory work fine on other linux systems using framebuffer devices, but only tested with a raspberry pi 2, model b.