iRex has released an SDK and source code for the iRex DR1000.

You can find this here (http://developer.irexnet.com/pub/iOn/).

The SDK is based on Poky (http://www.pokylinux.org/doc/poky-handbook.html#intro-quickstart), so I have some research to do. iRex also promises to release further documentation.

I'm sure developers will be busy working on discovering the internals and the many possibilities of this new development platform.

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.

Bravo for iRex! :clap:

AND the source code? Does this really mean we already get the source for the new all-in-on viewer application?

AND the source code? Does this really mean we already get the source for the new all-in-on viewer application?

:( It doesn't appear so. The binary is called "uds". I don't see anything like that in the sources.

The ctb package is the new content browser....

Looking through the sources, I'm not seeing any refresh calls... I wonder if iRex has figured out a way to automatically refresh the screen without having to manually call it.

Looking through the sources, I'm not seeing any refresh calls... I wonder if iRex has figured out a way to automatically refresh the screen without having to manually call it.Perhaps they read this forum, too :rolleyes:

http://www.mobileread.com/forums/showthread.php?t=22215

:( It doesn't appear so. The binary is called "uds". I don't see anything like that in the sources.

The ctb package is the new content browser....

It's probably just the GPL code, which is what they had release for the iLiad as well up until recently. The in-house iRex proprietary stuff will probably stay closed.

Perhaps they read this forum, too :rolleyes:

http://www.mobileread.com/forums/showthread.php?t=22215

Well thats the idea of them Opening the Source. I for one don't mind they embrace ideas from here in this deal.

I'm sure they've been working on the device a lot longer than the xepdmanager has been out.

Besides, from what I can tell, it's a similar idea but a different implementation.

:( It doesn't appear so. The binary is called "uds". I don't see anything like that in the sources.

The ctb package is the new content browser....

I expected so, well I think its about us to show what we can do with the iLiad when having full sources, so in a middletimed future they are inclined to do that as well. Maybe, maybe not. maybe the finance crisis will eat us all up until then eitherway :) Or the LHC explodes earth...

I am almost sure that I've read in a post that Irex will be open sourcing the whole thing. I guess it was a response from the irex team.(fingers crossed)

This could be the first post in a DR1000 Developer's Corner... :rolleyes:

Gogolo

Looking through the sources, I'm not seeing any refresh calls... I wonder if iRex has figured out a way to automatically refresh the screen without having to manually call it.

Hint: take a look at our GTK+ patches. ;) Happy coding!

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.

We're also looking at releasing our Poky environment (e.g. our changes to Poky as published by OpenedHand).

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

The last nail on iLiad's coffin.

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

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.

The last nail on iLiad's coffin.

no .

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.

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

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').

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,

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 (http://developer.irexnet.com/pub/iOn/Sources/1.7/iRex/) 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?

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

Cheers.

A long time ago, I posted this (http://www.mobileread.com/forums/showpost.php?p=439483&postcount=27) 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.)