Hi Dirk, Thanks for your little distraction. This looks very nice, and much more attractive than the current cloud.subsurface-divelog.org.
On Tue, 27 Jan 2026 at 11:45, Dirk Hohndel via subsurface < [email protected]> wrote: > Hi Michael, > > On Jan 26, 2026, at 15:23, Michael Keller <[email protected]> wrote: > > On Tue, Jan 27, 2026 at 8:25 AM Dirk Hohndel via subsurface < > [email protected]> wrote: > >> Have you created cylinders that are named based on the gas they carry >> instead of based on their size? >> > > I haven't, but the UDDF importer has, when importing dives from and APD > Inspiration CCR - 'it's a feature, not a bug'. 😉 > > > Ah. Well, too bad. You get what you pay for :) > > As for the tags, would it make sense to place to fill the screen width, to > make better use of space: > > [image: image.png] > > > That would mean breaking out of the grid. So totally possible, but also... > a lot more work. > > And would it be possible to show the dive number in the dive list, to make > it easier to find dives by number? > > > Totally. Good idea. > > > On Tue, Jan 27, 2026 at 8:21 AM Dirk Hohndel via subsurface < > [email protected]> wrote: > > - currently all gases are shown in the same way, irrespective of them > being used during the dive or not - this means it will be confusing for > technical CCR dives where bailout gases were carried, or for dive computers > where there is no way to mark gases as 'inactive' (the example above). > > > > That may be beyond what I am able to implement there without a lot more > code... > > Makes sense - in the application this is evaluated based on checking which > gases were switched to at least once during the dive from events. > > But a similar request that will improve the situation for CCR dives is if > we started showing gasmixes explicitly as 'diluent' vs 'OC gas' - it is > much less common to carry extra diluent than it is to carry OC bailout gas. > And we should probably show the dive mode in the 'Dive Metrics' or even in > the header / dive list. > > > I think it's quite obvious that right now this was done mainly with an eye > to the recreational scuba diver, with no thoughts given to tech divers, > CCR, etc. > But that's the thing - we can continue this exercise until I have > implemented a full HTML/JS UI. Or we can get it to a point where it is more > useful than what we had before, without turning into its own full thing. > > And I know that soon someone will say "it would be nice if I could edit > the notes, or the buddy names"... I'm not against turning this into a > fully equivalent webUI. But that wasn't what I set out to do. This all > started with reimplementing the horrible hodgepodge of backend apps and > replacing them with something new that I built from scratch, building on > what I had learned from running that backend for about a dozen years... > > If you're looking for feature requests, I'd like "next dive" and "previous dive" buttons. But to be honest, I found the old webUI helpful prior to having the Subsurface mobile app we have today. If I was away from my computer and wanted to look at a dive log it was great. But now I have a nearly full-featured version of subsurface on my phone, so I don't find myself needing a webUI (even a much prettier version). Cheers, Rick
_______________________________________________ subsurface mailing list -- [email protected] To unsubscribe send an email to [email protected]
