View Single Post
Old 05-18-2012, 06:42 PM   #13
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by geekmaster View Post
If you want to use x11, then you have all those window-naming rules you need to follow so the kindle does not hide your windows from you. But if you go below the framework, then it helps to pause the framework or capture the input devices. Whatever you do, you either need extra code for portability, or you will be locked into a specific kindle model (and even specific firmware VERSIONS on the K5(touch) thanks to recent undesirable update changes).
Correct - the question "to use x11 or to use the framebuffer" is an important question.
Hence my note that the project linked to was a qt-embedded (framebuffer) and not a qt (x11) project.

I have not finished reading the changes the author has made, including any possible changes specific to the e-ink display.
The base is qt-embedded v-4.6

But this "dead project" may become significant in the "Kindle Explorer" thread.
knc1 is offline   Reply With Quote