> I've asked this before, but I'm going to ask it again. Does anyone know
> the format for GEOS bookreader
> files? I know it isn't public knowledge, but somebody must be hacking it by
You can derive most of the format by using the header files in the SDK (OmniGo
would be best... :-)) and some knowledge of the underlying structure of Geos VM
files, because Help Files are based largely on the VisText object transfer
format...
In the OmniGo SDK, the file CONVIEW.DEF defines the actual book reader format,
HELPFILE.DEF tells you about the structure of help files [which are nearly the
same thing], OBJECTS\VTEXTC.DEF defines the format of a "text transfer item"
(storing text, attributes and styles) itself.
This is quite heavy stuff if you want to look at it without "any" help from Geos
system libraries, but most of it is taken care of automagically if you're using
the help of a VisText object or the TextAllocClipboardObject routines... The
reason is that Book Reader files have not been defined as a format independant
of Geos, but rather along the lines of "whatever comes out when you tell the
standard text object to store itself to a file".
Obviously, this is the reason why there is no Windows-based environment for
creating OmniGo content.
> Also, does anyone have any information on the Notepad and Jotter files
> used on the Omnigo? I'd like to
All *.?db files are based on Hewlett Packard's own PDA database format, which is
also used on the 100/200LX, so you can use LX-series utilities to access them,
the most prominent of them being probably GDBIO (which comes with full source
code, if I remember correctly).
ciao marcus