MobileRead Forums - View Single Post

Tomek · 12-26-2008, 12:59 AM

Is it possible to read ebooks in QEMU? I'm not sure what would the best way to get the ebook to the image, but it looks like 'wget' is available so that would be one way. I can't figure out however where to place the content. I tried several places with a *.txt file but I never see it available from Menu->Open... in QEMU which always takes me to the "Settings" option.

For example, there is a /usr/share/uds/ebooks symlink that points to /media/mmcblk0p1/eBooks folder which doesn't exist by default. I created the folder and a test *.txt file there, but it still doesn't open.

I'm also curious if anyone here has tried developing a custom Universal Document Shell (UDS) plugin yet? I'm studying the examples and would love to be able to bounce ideas around, ask for help, and eventually help out other newcomers. Specifically, I haven't figured out yet what is the main entry point for the plugin? That is, what is the first function/method that is called by the UDS system? So far it looks like IPluginLibrary interface's "is_supported_document" may be up there near the top... but how does the system know about the new plugin? Does the plugin register somewhere?

12-26-2008, 12:59 AM	#20
Tomek Enthusiast Posts: 29 Karma: 10 Join Date: Sep 2008 Location: USA Device: Kindle DX	Is it possible to read ebooks in QEMU? I'm not sure what would the best way to get the ebook to the image, but it looks like 'wget' is available so that would be one way. I can't figure out however where to place the content. I tried several places with a .txt file but I never see it available from Menu->Open... in QEMU which always takes me to the "Settings" option. For example, there is a /usr/share/uds/ebooks symlink that points to /media/mmcblk0p1/eBooks folder which doesn't exist by default. I created the folder and a test .txt file there, but it still doesn't open. I'm also curious if anyone here has tried developing a custom Universal Document Shell (UDS) plugin yet? I'm studying the examples and would love to be able to bounce ideas around, ask for help, and eventually help out other newcomers. Specifically, I haven't figured out yet what is the main entry point for the plugin? That is, what is the first function/method that is called by the UDS system? So far it looks like IPluginLibrary interface's "is_supported_document" may be up there near the top... but how does the system know about the new plugin? Does the plugin register somewhere? Last edited by Tomek; 12-26-2008 at 01:12 AM.