On 04-09-14 00:07, Dirk Hohndel wrote:
Here's what I learned from your response:
- MacDive, just like Subsurface, ended up implementing custom parsers for information that isn't extracted by libdivecomputer.
Almost right. The original reason is a bit different. Macdive is a few years older than subsurface, and started around the same time as libdivecomputer itself. At that time the libdivecomputer parser was pretty much non-existing or at least even more basic than it is now (e.g. sample data only). So writing a custom parser was basically the only option. Nowadays the libdivecomputer has much improved (although their is certainly room for improvement!) and while Nick and I discussed switching to the libdivecomputer parsers more than once, that just didn't happen yet. It works, and there have been always some more urgent things on the todo list :-)
We're mostly in sync, but sometimes we have minor differences (or different bugs if you prefer :-)) here or there.
- MacDive, just like Subsurface, would prefer to get such data from libdivecomputer, as long as it is easy to tell if the data is available or not - so no made up, interpolated or otherwise fabricated data. Either an indication "the data aren't available", or actual data from the dive computer.
It's hard to disagree with that!
Jef