iRex Releases DR1000 SDK and source code

[stonehat]

Hoorah, and a good, business move for iRex, IMHO.

[Format C:]

The last nail on iLiad's coffin.

[eth777]

Ok, I've got a question regarding the dr1000. How easy is it to recover from bricking it? Is there an external way to reload to factory defaults, similar to the way iliad finally had it with the cf card?

Thanks
Eth

[Adam B.]

Originally Posted by eth777

Ok, I've got a question regarding the dr1000. How easy is it to recover from bricking it? Is there an external way to reload to factory defaults, similar to the way iliad finally had it with the cf card?

Thanks
Eth

I believe the DR checks for a software update on the SD card every time it boots. If the internal operating system is broken, it should automatically reflash if the firmware is available.

[axel77]

Originally Posted by Format C:

The last nail on iLiad's coffin.

no .

[joblack]

Originally Posted by pthwaite

I look forward to the results not having a clue about programming any more. (gave up 20 yrs ago after machine code on intel 8080 & z80 at University).

I do hope that several of the iliad programmes can be ported across though.

If you programmed Assembly Language it is no problem to settle for C.

[sarikan]

A question for the guys out there who has more experience in this domain more than I do:
What kind of extensions does the sdk allow? Is it possible to replace the existing reader with a new one?
I have not been into low level programming for a very long time, so trying to figure out basics would take a huge effort for me, some clues would be really nice

Kind regards
Seref

[Matthijs]

Originally Posted by Adam B.

I believe the DR checks for a software update on the SD card every time it boots. If the internal operating system is broken, it should automatically reflash if the firmware is available.

Indeed, every time it cold boots (after reset switch, completely empty battery or software 'reboot').

[plisken]

Originally Posted by Matthijs

P.S. The document viewer (uds) will remain closed source.The API for plugins is fully open however and all current plugins except Mobipocket are GPL'ed as well. So adding more document formats or improving current plugins is very well possible.

Ok, so for example instead of using evince as djvu reader it should be possible to cripple it a bit to be just a plugin and make it compatible with uds API, right? Where is the documentation for the API?


:-) Funny, I almost have feeling like in early days of Amiga, the same "uncharted territory" (almost), only the days are now somehow shorter.

Cheers,

[Mackx]

Originally Posted by plisken

Ok, so for example instead of using evince as djvu reader it should be possible to cripple it a bit to be just a plugin and make it compatible with uds API, right? Where is the documentation for the API?

In the interface files ofcourse .
Serious, there is a lot of documentation in the header files and there is the implementation of the interface for plaintext, pdf and images. No tutorial or manual, but with some puzzling and experimenting it should be possible to make your own plug-in, although I have never tried ...
Good luck, if you have a go at it, please make a 'tutorial' as you go, so others can also benefit?

[plisken]

Thank you for the answer. I'll start from something simple, if I succeed, sure I will share my experience with others.

Cheers.

[Mackx]

A long time ago, I posted this which might be a good starting point to get developing on the DR. I hope there is something usefull in it. (If you already have development experience on the DR, it might be too simple.)