mirror of
https://github.com/subsurface/subsurface.git
synced 2025-01-31 18:33:23 +00:00
This is the official upstream of the Subsurface divelog program
ecff0922d4
It was a mistake to save it - and I did it just because other dive managers did. It's a totally nonsensical measure, and nobody cares. The only thing that matters is the size of the cylinder, and the *actual* pressures. Those give actual air consumption numbers, and are meaningful and unambiguous. So the "working pressure" for a cylinder is pointless except for two things: - if you don't know the actual physical size, you need the "working pressure" along with the air size (eg "85 cuft") in order to compute the physical size. So we do use the working pressure on *input* from systems that report cylinder sizes that way. - People may well want to know what kind of cylinder they were diving, and again, you can make a good guess about this from the working pressure. So saving information like "HP100+" for the cylinder would be a good thing. But notice how in neither case do we actually want to save the working pressure itself. And in fact saving it actually makes the output format ambiguous: if we give both size and working pressure, what does 'size' mean? Is it physical size in liters, or air size in cu ft? So saving working pressure is just wrong. Get rid of it. I'm going to add some kind of "cylinder description" thing, which we can save instead (and perhaps guess standard cylinders from input like the working pressure from dive logs that don't do this sanely - which is all of them, as far as I can tell). Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> |
||
---|---|---|
dives | ||
.gitignore | ||
display.h | ||
dive.c | ||
dive.h | ||
divelist.c | ||
info.c | ||
main.c | ||
Makefile | ||
parse-xml.c | ||
profile.c | ||
README | ||
save-xml.c | ||
scripts |
Half-arsed divelog software in C. I'm tired of java programs that don't work etc. License: GPLv2 You need libxml2-devel and gtk2-devel to build this. Usage: make ./divelog dives/*.xml to see my dives (with no notes or commentary). There's a lot of duplicates in there, and divelog will de-duplicate the ones that are exactly the same (just because they were imported multiple times). But at least two of the dives have duplicates that were edited by Dirk in the Suunto Dive Manager, so they don't trigger the "exact duplicates" match. WARNING! I wasn't kidding when I said that I've done this by reading gtk2 tutorials as I've gone along. If somebody is more comfortable with gtk, feel free to send me (signed-off) patches. Just as an example of the extreme hackiness of the code, I don't even bother connecting a signal for the "somebody edited the dive info" cases. I just save/restore the dive info every single time you switch dives. Christ! That's truly lame. Also, I don't actually integrate directly with libdivecomputer, I just read the XML files it can spit out. But I included my own raw dive profile xml files for anybody who isn't a diver, but decides that they want to educate me in gtk. NOTE! Some of the dives are pretty pitiful. All the last dives are from my divemaster course, so they are from following open water students along (many of them the confined*water dives). There a lot of the action is at the surface, so some of the "dives" are 4ft deep and 2min long.