Hi Anđela.
You know what comes across as arrogant in community driven open source projects like Subsurface? People on the outside telling people on the inside that implementing feature X (that they want) should not be that difficult to implement.
In this project, like in many others similar to it, there is a massive overhang of features that are desired by users compared to the free time and motivation that is available from volunteers to implement these features. Which means 'code written' is currency in here, 'features requested' are just a distraction from other features desired by other users.
Since you seem to have the skills to 'scratch your own itch' and implement the feature that you want, can I suggest that you go ahead and put in the effort to get familiar with the project, and then open a pull request to implement it? This will give everybody a much better starting point to discuss what needs to happen for this to be accepted.
Regarding gas usage start-end pressure, it’s simply a nice statistic to have, and it’s something that is stored in many different dive logbooks.
I suspect that this is a 'value of convenience' that is a left over from the days of paper logbooks, where it was something that users could calculate in their head without having to do complicated operations. But it has only value as long as you are always diving with the same tank size - as soon as you do dives with different tank sizes it becomes meaningless.
So, a better value to track in a computerised logbook (where we don't worry about being able to calculate values in our head) will be the gas volume used (in liter or cubic feet) - this will allow you to compare gas usage across dives with different tank sizes.
Or even better, we could then factor in the duration and average depth of the dive, and we'd get the volume of gas consumed by the diver every minute of the dive, normalised for surface pressure - this is also called the Surface Air Consumption (SAC). This will be a useful proxy for workload, effectiveness, and training level.
And lo and behold, Subsurface already supports this, and it can be used to filter dives, and generate statistics:

As I said above, if you still feel that Subsurface is missing something here, feel free to open a pull request to propose a change to implement it.
Ngā mihi
Michael Keller
--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/156c3e20-c6b9-47db-afca-65ffa8dde57en%40googlegroups.com.