🚀 go-pugleaf

The Odyssey must be the most under-documented, bogus load of garbage
I've ever had the displeasure of programming.  GRRR!

It comes with all sorts of neat examples, some of which actually work,
with tiny ammounts of documentation, if any at all.  On the software
support end, there's a package called odyssey-tools that is supposed
to make it possible to run stuff on the odyssey controlled from a lisp
environment, but there's not one scrap of printed documentation in the
manual about this toolset.  sure, these examples work, but if you want
to write your own stuff, you're SOL.  Ok, so I managed to get the "forth"
version (actually written in tms320 assembly for the forth interpreter)
of the codec-linear converter into object code like the odyssey-tools
likes it.  then i find out about some control thing which 1) has no
documentation a la the documentation form 2) has no printed documentation,
as NONE of the odyssey-tools have any printed documentation whatsoever.
the stupid thing isn't even intuitive!  I've pretty much managed to get
as far as i have just from hacking things until they worked.

it's pretty frustrating.  there are only three explanations i can come
up with:
	1) we didn't get the complete set of software and documents
	2) we got a pre-release set
	3) the whole odyssey project was never really finished


(rant, rave)

i'd loved to be proved wrong about this, any takers?