Open Source and Pocketbook: ideas, proposals, criticism... - Page 2

mtravellerh · 10-20-2010, 04:02 AM

Quote:

Originally Posted by LoneTech

Thank you, that wiki would be a great place to collect information. I already noted one niggle; in the networking API, one should test for NET_CONNECTED rather than the individual NET_*READY bits, to allow for future connection methods (USB tethered, perhaps). I haven't figured out how to enable editing or join the pocketbook-free project, though.

I've started in slightly on Doxygen-tagging the inkview.h header. Combined with the demo app, this got me some clarifications such as what Long (long tap) and Hold (pointer stopped after moving) pointer events are.

A copy of the current progress (limited, I know) is at http://donkey.vernier.se/~yann/pbapi/. The API itself looks fairly manageable, but eventually I'll probably be down to a few questions or points that need testing.

If you have unsurmountable problems, I am willing to link you to our head programmer. I am sure Igor can help you out.

LoneTech · 10-20-2010, 05:49 AM

See what I mean by liking the service? I'm not at a stage to be asking questions just yet but am already being offered help!

I can do quite a bit more on the API documentation (and personal app ports, perhapt sgt-puzzles) without further assistance. inkdemo seems outdated (incompatible types when compiling, bugs with configuration editor in prebuilt version) but it's likely I can even debug that on my own.

What I can't do easily is check how nicely the device itself complies with the letter and spirit of free software. The one downvote the PocketBook-free project got is from this; it's not very nice, for instance, if we get kernel sources but can't install them. Worse if they can't even be built.

For now, I'll concentrate on inkview from the programmer's perspective.

LoneTech · 10-20-2010, 12:35 PM

Uploaded a patch for inkdemo to make the configuration editor example work again (structure had changed). Unfortunately the info button doesn't seem to do anything. Also updated the documentation a little, it's slowly beginning to get a little structure.

reader42 · 10-20-2010, 02:11 PM

Quote:

Originally Posted by LoneTech

Thank you, that wiki would be a great place to collect information. I already noted one niggle; in the networking API, one should test for NET_CONNECTED rather than the individual NET_*READY bits, to allow for future connection methods (USB tethered, perhaps). I haven't figured out how to enable editing or join the pocketbook-free project, though.

You need a sourceforge-account and then write a message to klu4nik or t_tarnavski, they are the owners and can add you.

You also might be interested in this:
https://www.mobileread.com/forums/sho...d.php?t=101144
It is a telnetd for the pocketbook 302. I still want to upload the source to the svn, but havn't had the time ...

LoneTech · 10-31-2010, 07:13 AM

I tried sending a message to klu4nik. As for the inkview API, I feel it suffers a bit from mixed levels of abstraction (we can draw a menu, but not a polygon?) and abuse of #defines. Most of the ones in there should have been enums, allowing more informative types for the functions.
At this point, I'm maybe halfway towards a proof of concept port of some Tatham puzzles, but a full port requires more support code - there's no polygon, circle, or thick line support in inkview (aside from one undocumented function, DrawCircleLine).
To get a more flexible and widely maintained library, I am leaning toward just porting DirectFB to the eink drivers, but can't really start testing that without a device. I haven't found real documentation for those drivers, either, which is a disappointment. A datasheet for the Epson controllers would be nice.
FWIW, it wouldn't be the first time I mucked about with that type of code - I did some work on PicoGUI way back.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Open Source bei Pocketbook – Vorschläge, Ideen	Alaska	PocketBook	14	08-25-2010 03:50 PM
An IDEAL POCKETBOOK - what is it? Throwing your ideas in:)	Yar-PocketBooker	PocketBook	60	01-20-2010 10:49 AM
Open source	bradrice	Kindle Formats	2	12-21-2009 09:30 AM
iRex and Open Source	jrial	iRex	8	03-03-2009 10:34 AM
Open source lrs2lrf	kovidgoyal	LRF	14	07-25-2008 09:17 PM

10-20-2010, 05:49 AM	#17
LoneTech Zealot Posts: 135 Karma: 7767 Join Date: Oct 2010 Device: PocketBook Pro 903	See what I mean by liking the service? I'm not at a stage to be asking questions just yet but am already being offered help! I can do quite a bit more on the API documentation (and personal app ports, perhapt sgt-puzzles) without further assistance. inkdemo seems outdated (incompatible types when compiling, bugs with configuration editor in prebuilt version) but it's likely I can even debug that on my own. What I can't do easily is check how nicely the device itself complies with the letter and spirit of free software. The one downvote the PocketBook-free project got is from this; it's not very nice, for instance, if we get kernel sources but can't install them. Worse if they can't even be built. For now, I'll concentrate on inkview from the programmer's perspective.

10-20-2010, 12:35 PM	#18
LoneTech Zealot Posts: 135 Karma: 7767 Join Date: Oct 2010 Device: PocketBook Pro 903	Uploaded a patch for inkdemo to make the configuration editor example work again (structure had changed). Unfortunately the info button doesn't seem to do anything. Also updated the documentation a little, it's slowly beginning to get a little structure.

10-31-2010, 07:13 AM	#20
LoneTech Zealot Posts: 135 Karma: 7767 Join Date: Oct 2010 Device: PocketBook Pro 903	I tried sending a message to klu4nik. As for the inkview API, I feel it suffers a bit from mixed levels of abstraction (we can draw a menu, but not a polygon?) and abuse of #defines. Most of the ones in there should have been enums, allowing more informative types for the functions. At this point, I'm maybe halfway towards a proof of concept port of some Tatham puzzles, but a full port requires more support code - there's no polygon, circle, or thick line support in inkview (aside from one undocumented function, DrawCircleLine). To get a more flexible and widely maintained library, I am leaning toward just porting DirectFB to the eink drivers, but can't really start testing that without a device. I haven't found real documentation for those drivers, either, which is a disappointment. A datasheet for the Epson controllers would be nice. FWIW, it wouldn't be the first time I mucked about with that type of code - I did some work on PicoGUI way back.

Advert

Advert