[Therion] distox

[marco corvi]

On Wed, 2010-04-14 at 12:22 +0100, Wookey wrote:
> +++ marco corvi [2010-04-14 09:18 +0200]:
> > hi wookey,
> 
> Is there any reason you replied off-list? I'm sure this would be
> interesting to others.

none.
i just clicked on the sender name out of abit.

> > the work on "my distox programs" is going on.
> > you can get the programs and dome docs on the page
> > http://marcocorvi.altervista.org/caving/distox/index.htm
> 
> OK. good stuff. I will download, build and test tonight if I can. 
> 
> > important catch:
> > my programs are meant to work with single survey.
> > i rely on therion for the full cave(s) survey.
> > also i do not have a portable device to take in the
> > cave, so i do not focus much on working on-line,
> > but on working off-line.
> 
> OK. I do, so maybe I can help with that. I think it's important to get
> something like the pocketopo functionality on non-windows devices. 

agree.
any help is very much appreciated.

> > recent changes (besides bug fixes), 
> > added pockettopo import/export (beat told me the file format
> > and we had an email exchange about how to address the
> > programs interoperability),
> > worked on compass export, and therion export.
> > reorganized some of the code.
> > not sure these are all online.
> 
> OK. What's the deal with the calibration algorithm? Having that remain
> secret is going to be a problem. I thought the device could do its
> own calibration, but apparently it needs an external app? Perhaps we
> can adapt the SAP calibration code (which is Free) as it must be very
> similar. 

as far as i read, beat algo is better.
beat should have a paper published soon in CREG
describing the algo.
i believe that when it is published i can put
my reimplementation in the sources.

> What do you have and what have you agreed not to disclose? If
> it's just the code then re-implementation via an explanation of the
> algorithm should be fine.
> 
> > i was considering dropping the QT3 support and work only 
> > with QT4 (better classes and easier interfaces).
> 
> OK. I guess that is the way forward now. I guess that could be a
> problem for GTK-based devices with limited storage. 

yes.

marco