On Thu, 2014-02-27 at 16:42 +0100, Jef Driesen wrote: > Hi, > > For the "Ability to Configure Dive Computers" idea, one of the > prerequisites is access to a supported dive computer. I think you can > easily drop this requirement. The most likely target dive computer for > this feature is the Heinrichs-Weikamp OSTC. It's open source, the > available settings are fully documented, and modifying them is already > supported by libdivecomputer. But reading and writing the OSTC EEPROM > (which is where the settings are stored) is also supported by the > libdivecomputer simulator. That means you can test your code without > needing an OSTC at all. Even firmware updates can be simulated! Dropping > this requirement will probably make it easier to find a student that can > work on this :-)
Please edit the wiki - you have an account and can do that :-) Would you like to mentor this project? > Of course I'm also happy to assist a student with the libdivecomputer > related parts of this idea. Hehehe.... > If the Gsoc ideas are not restricted to subsurface, but can be extended > into libdivecomputer territory, then I may have another suggestion: > integrate the subsurface Uemis code in libdivecomputer. I seem to remember that you and I talked about this multiple times in the past - and came to the conclusion that because of the weird way that the Uemis works (with the FAT filesystem that fills up) current libdivecomputer architecture made it extremely hard to add that support. So we had agreed to do this with the new API. But my memory may be wrong. /D _______________________________________________ subsurface mailing list subsurface@hohndel.org http://lists.hohndel.org/cgi-bin/mailman/listinfo/subsurface