Development eDGe Library filesystem and backup structure

This is an attempt to document the structure of the eDGe library and the files that are backed up by the Local Backup application.

Local backup of the library creates a file ending in .esi which is actually just a plain zip file. Rename the file extension to .zip and the zip/unzip utilities should be able to examine and manipulate the file. There is no password and no apparent encryption of the file itself.

My edge has the library moved to the external SD card. The .esi/.zip file produced contains two *absolute* paths, /fridge and /sdcard. (This absolute path part may be an issue later when restoring a backup that has had the contents manipulated with zip/unzip on a PC.)

Here is a list of all the directories containing one or more files in the .esi/.zip file:

/fridge/.edge/.esi-data/.databases/
/fridge/.edge/.esi-data/.edb/
/fridge/.edge/.esi-system/
/fridge/.edge/.esi-system/.fontconfig/
/sdcard/.edge/.esi-content/
/sdcard/.edge/.esi-content/.esa/

On initial perusal it appears /fridge contains a series of sqllite databases. Some contain configuration information, but most are related to library files and used to link separate files together -- books to annotations, etc.

All the real content -- PDFs, annotations, Journals -- are stored under the /sdcard path.


TO BE CONTINUED

I've done some work on this:

http://andy.aspellclark.org.uk/eDGeLibraryNotes.doc

ok, i realize i'm probably WAAAAY oversimplifying this, but here's my opinion/idea. If programmers on here understand linux and have used other versions of SDK/Android versions could you not copy the original source code from the eDGe and then compare them side by side. My reasoning here is let's say you have the original source code for the eDGe and the new source code for Android 3.1. If you put them beside each other could you not tell which is for the eInk side and which is for the LCD side ----then take the portion that is related to the eInk side and implement this into the new code for Android 3.1?
I realize anyone who actually programs is probably looking at this post and saying why is this guy allowed to breathe, but it makes sense in my pea brain....so tell me if I'm smokin' crack.

Originally Posted by wdcorbitt

ok, i realize i'm probably WAAAAY oversimplifying this, but here's my opinion/idea. If programmers on here understand linux and have used other versions of SDK/Android versions could you not copy the original source code from the eDGe and then compare them side by side. My reasoning here is let's say you have the original source code for the eDGe and the new source code for Android 3.1. If you put them beside each other could you not tell which is for the eInk side and which is for the LCD side ----then take the portion that is related to the eInk side and implement this into the new code for Android 3.1?
I realize anyone who actually programs is probably looking at this post and saying why is this guy allowed to breathe, but it makes sense in my pea brain....so tell me if I'm smokin' crack.

AFAIK, we do not have all the source code. We have the entourage code for running the Android side, but as far as I know nobody has seen the actual code for anything running the eInk side.

I wouldn't even care if they neglected to pass out the documentation. If entourage simply gave out the source for driving the eInk side and the existing Edge programs that use it then we'll figure out everything else.