I'm curious about how Scribe stores Notebook data, synching behavior, etc, and plan to engage in some experimentation.
It appears that everything is stored in SQLite databases in KPF containers, each with a -journal to manage atomic commit and rollback (undo/redo/sync to cloud?). There is also a
thumbnails folder that has a .png render of the first page of each downloaded notebook.
Folder structure is like this snapshot of my Scribe:
Quote:
.notebooks
- guid-like named sub-folders e.g. "d088f501-48f6-7a6b-341c-726964927fff"
(1 for each downloaded notebook)
- thumbnails
(PNG thumbnail for each downloaded notebook, uses same filename as the notebook folder they correspond to)
- .backup (mine is empty)
|
You might see folders with '!!EBOK!!' or '!!PDOC!!' in the name. These appear to contain Pen annotations for store content and personal documents, respectively, the content itself would be in /documents folder.
@jhowell:
Quote:
|
The templates for Scribe notebooks are contained in the firmware and stored in individual subfolders under /app/standalonenotebook/templates. These are in KDF format which is a variant of KFX that uses an SQLite database.
|
@jhowell on folders:
Quote:
|
It is likely that they are handled the same way as collections, as entries in an SQLite database stored in a part of the file system that is inaccessible via USB.
|
The nbk data can be exported to NMDL ('Note Model Description Language', expressed in Amazon ion data format) using KFX input plugin.
Findings:
* it is possible to backup and restore specific notebook versions
* it is probably possible to export to SVG once NMDL is sufficiently 'understood'