Quote:
Originally Posted by Jumpn Jack Flash
Can I suggest 2 things 
a) a repository, such as github or sourceforge, etc.
b) some abstraction layer possibly built on autoconf  to handle rolling forward iRex api changes. |
Good suggestions,
I do not have any experience with either, so some help would be appriciated. Which repository best to use, w.r.t. ease of use and performance (of the used server)? Is the
MobileRead Development Hub a good alternative?
W.r.t. the second point I hope with the new firmware for the DR1000 the libs will be the same again and that afterward new firmware will be released for both 1000 and 800 at the same time. But it would be wise to think of it.
The iRex code uses constructions like:
#if MACHINE_IS_DR1000S || MACHINE_IS_DR1000SW
for machine specific code, may be best to align to this.