UDDF Export Format

Hi, I'm currently working on some patches to the UDDF export format, to address a few issues which I'm seeing in the files. For example, I've separated buddies out, and linked to multiply buddies, rather than the current method which is to always link to a single buddy, which may actually be

Re: [PATCH 1/7] Separate out buddies into individual entities when exporting to UDDF.

On 10 December 2014 at 13:25, Dirk Hohndel d...@hohndel.org wrote: On Wed, Dec 10, 2014 at 12:31:41PM +0200, Miika Turkia wrote: Thanks for all the feedback. node-set should be available across pretty much every linux distro now (it's been in libxslt for over 10 years). This should be

Re: [PATCH 1/7] Separate out buddies into individual entities when exporting to UDDF.

I need to make a few changes anyway, so I'll just resubmit them all. Unless you want to get a build out to start testing these as they are, in which case: All seven patches in this series are Signed-Off-By: Martin Long mar...@longhome.co.uk ___

Repetition groups in UDDF

I think I'm starting to be the 'annoying neighbour' :-) So, the last patch adds proper trip support in the UDDF export, rather than hijacking the repetition group. With this done I'm wondering if there is a better way we can use the repetition group. I'm looking for a bit of input for this, as

Re: Repetition groups in UDDF

In that case it is good to go. Working off trips is probably a decent solution. Great. On 10 Dec 2014 23:21, Dirk Hohndel d...@hohndel.org wrote: On Wed, Dec 10, 2014 at 11:15:54PM +, Long, Martin wrote: I think I'm starting to be the 'annoying neighbour' :-) Not at all - we love adding

Windows dailies.

Hi, Maybe I'm being dumb. Where can I find the Windows daily binaries? thanks Martin ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

UDDF Export

So. I ran the UDDF output through the XSL schema from the uddf site. It looks like there are still lots of areas where we are not compliant. - Lots of areas where there are mandatory tags we need to provide (looks like most of this is static). - Lots of ID which aren't compliant. I think this

UDDF export - nearly there.

So another 7 patches. This makes it almost 100% UDDF 3.2 compliant. I say almost. There are a couple of places where the schema doesn't agree with the documentation, where I believe the schema. I believe there are also some bugs in the schema too. In both cases I'll raise these with the authors.

Re: [PATCH 4/7] Fix divecomputer part of UDDF export

On 13 December 2014 at 16:40, Dirk Hohndel d...@hohndel.org wrote: Well, there are divecomputer sections in each dive, but the nickname, serial, firmware, etc, should be stored in the settings at the beginning. And that has been true at least since Subsurface 3. Also, if the nickname is

Re: [PATCH 4/7] Fix divecomputer part of UDDF export

So, the info in every profile (for my Suunto) is: divecomputer model='Suunto Vyper Air' deviceid='cef51609' diveid='8ab03c43' And the details in the settings section, when I add a nickname: divecomputerid model='Suunto Vyper Air' deviceid='cef51609' nickname='nick'/ So, it looks like there

Re: [PATCH 4/7] Fix divecomputer part of UDDF export

I'll have to test this tomorrow hopefully. i've not been able to do anything on this tonight, so hopefully I'll get a chance tomorrow. ___ subsurface mailing list subsurface@subsurface-divelog.org

Re: [PATCH 6/7] Lots of minor UDDF export tweaks.

I'll look into this. The weight at the end was removed intentionally. I admit I'm not entirely sure what happened here. I think it was when I added the correct namespace this stopped working, and removing weight made it work for me. I'll investigate this further tonight. Btw, weights are now in

Re: [PATCH 6/7] Lots of minor UDDF export tweaks.

as possible (and here I refer to both written specs and the xml schema). However, for the import we need to be quite lax as I think every single application produces different UDDF output - at least that is my take from the sample files I have received. miika On Sun, Dec 14, 2014 at 1:37 AM, Long

Re: [PATCH 4/7] Fix divecomputer part of UDDF export

On 13 December 2014 at 23:33, Long, Martin mar...@longhome.co.uk wrote: I'll have to test this tomorrow hopefully. i've not been able to do anything on this tonight, so hopefully I'll get a chance tomorrow. Am I missing something? I don't see a Subsurface-testing branch in libdivecomputer. I'm

Re: Debian, Fedora, OpenSUSE people...

So I have been told by people who are much more familiar with Ubuntu and Debian than I am that I should be able to use pretty much the same scripts that I have for Ubuntu (and LinuxMint) to build a Debian package. Could someone elaborate on this? And where would I post those - there

Re: After 4.3 is out...

You may be amused to learn that when Linus and I came up with the crazy idea of doing git storage for Subsurface the actual goal had always been remote git storage. And the reason why we wanted to do this was because we figured that when working both on a computer and on a device you'd sooner

Re: GSoC 2015

We have very good HTML export as a result of the last GSoC. Have you played with it? Are there features missing from it? If yes, I’m sure Gehad will be curious to hear what you’d like to see added… I only mentioned HTML as some form that could be printed as a log book. Yes, it is excellent,

Re: Download from Suunto Gekko - procedure?

On 5 January 2015 at 04:02, Linus Torvalds torva...@linux-foundation.org wrote: On Jan 4, 2015 5:50 PM, Gary David gda...@ntlworld.com wrote: I came across your post this evening whilst looking for a simple way to download the data off my ageing Suunto Gekko dive computer. Is there a way to

Re: [PATCH] Increase the limits for recursion and variables on XSLT parsing

Dirk, just interested in this. Do you cross compile the win32 binaries? I've been assuming that is what you do, but can't actually find it written down anywhere. On 11 February 2015 at 23:59, Dirk Hohndel d...@hohndel.org wrote: On Feb 11, 2015, at 3:44 PM, Lubomir I. Ivanov

Re: Which protocol to implement on a home brewed diving computer ?

I agree with Linus that UDDF is the definition of bloated. Otoh it sees to be the least common divisor if a lot of software in this sector. If you do decide to go the UDDF route (and I strongly recommend you don't), then get in touch with me. We're currently on a 'beta' version of the UDDF

Re: Customizable Print Formats GSoC 2015

I've only really scanned this thread, so please excuse me if I'm raising something that's already been covered. It seems we're talking about rendering using HTML along with a few other things. Have we considered pagination? I know this is something that HTML isn't great at. You can, of course,

Re: GSoC 2015 - Introduction

*MANY* thanks for your powerful explanation. =D You're welcome :) I have many ideas about how it should looks like and work... I'm doing some mockups and I will let you see it soon. Great, I'd love to see them. I'm thinking about structures where users could add or/and group things

Re: GSoC 2015 - Introduction

I haven't been through it in great detail, but that looks good, and would form a good starting point for your proposal/application. ___ subsurface mailing list subsurface@subsurface-divelog.org

Re: GSoC 2015 - Introduction

Hi Marcos, *- Asset Management* The main concept of this project is very clear[2], but as I'm not a diver, I really appreciate your help to better understand all the details expected for this project. In this way I would have more knowledge to think about the data structure. Do you

Re: prososal to code for Asset management- project through gsoc 2015

Sorry... I missed this line, previously: cloned the repo in a fedora vm built it from the code using instructions given However, I don't see any patches from you on the mailing list. This should probably be your next step. Regards Martin On 23 March 2015 at 09:37, Long, Martin mar

Re: GSoC - Customizable print formats

On 7 May 2015 at 07:28, Lubomir I. Ivanov neolit...@gmail.com wrote: also GSoC wise, do you think the new printing code should enter master while WIP or should it do so all at once when mostly done? Just my 2c... I would favour doing it in a branch (or in this case in Gehads own github

Re: making remote git storage work [was Re: Subsurface ans Dropbox]

A little feedback: Advanced mode - I'd most likely use this. I think this is quite important, and opens up the possibility or using Github, Bitbucket, or privately hosted git repos. You keep saying PIN. Could that actually be any passphrase? i.e. why limit it to numbers, or limit the length? I'd

Re: making remote git storage work [was Re: Subsurface ans Dropbox]

On 29 May 2015 at 14:23, Dirk Hohndel d...@hohndel.org wrote: On Fri, May 29, 2015 at 08:13:44AM +0100, Long, Martin wrote: A little feedback: Advanced mode - I'd most likely use this. I think this is quite important, and opens up the possibility or using Github, Bitbucket, or privately

Re: Build errors

> > > > The thing that completely baffles me is that this is our daily build. > NOTHING in that area has changed in Subsurface and the "daily" build a few > days ago worked fine. > > I'm beginning to ask myself if this is maybe a corruption somewhere. I'll > push another commit and trigger new

Re: Build errors

On 26 October 2015 at 21:01, Dirk Hohndel <d...@hohndel.org> wrote: > On Mon, Oct 26, 2015 at 08:54:48PM +0000, Long, Martin wrote: > > > > > > > > > > > > The thing that completely baffles me is that this is our daily build. > > > NOTHING

Re: Build errors

> > > Figured it out. > > And of course it was my personal stupidity that caused it. > You can't modify a list in cmake by treating it as a string. That breaks > things in apparently really creative ways. > > And trusty is the only platform we build on with BT so old that we disable > it in cmake.

Re: Oreo - has anyone tested the Subsurface-mobile app?

I've been using it for a little while now. I was on the developer preview of Oreo, and got the full version on release day. I also spent all of last week diving in the red sea, and happily downloading and logging dives from my Petrel AI - all working very well. It's amazing that this entire

Re: A few changes to the QML UI

Foiled. I'm using this forum to drop encoded messages to the NSA (or perhaps MI5) in Haitian Creole, disguised as English (that be correct English English). We were one step away from catching the eBay Rambler. You might be interested to know my wife is a native Creole speaker, but Seychelles

Re: A few changes to the QML UI

org> wrote: > > > On May 14, 2018, at 1:40 PM, Long, Martin <mar...@longhome.co.uk> wrote: > > > > Aside from the jerky/weird scrolling, I'm getting the old issue where > whichever dive I "tap" on the list, a random one seems to be show. It > doesn't *seem

Re: A few changes to the QML UI

Aside from the jerky/weird scrolling, I'm getting the old issue where whichever dive I "tap" on the list, a random one seems to be show. It doesn't *seem* to be deterministic. Tapping the same dive over and over can result in different ones showing. They're not always necessarily from the same

Re: converting logbook formats

Actually there is a good point here. It would be great to have options to use self hosted git repos, or even github, bitbucket etc. I've quite fancied building my own website around the repo - I like the one hosted on subsurface, but that one doesn't allow me to share links with other divers. If

Re: Missing pO2 samples from CCR download [was: 4.7.8: a couple of questions]

I'm in agreement with Davide that any interim solution we can get running is better than the way it is working now. It's a regression, and tbh if there isn't an interim solution then it ought to be reverted to the old behaviour. At the moment I'm having to use Shearwater desktop for reviewing all

Re: Missing pO2 samples from CCR download [was: 4.7.8: a couple of questions]

, Dirk Hohndel wrote: > > On Jun 17, 2018, at 6:52 PM, Davide DB wrote: > > On Thu, Jun 14, 2018, 15:34 Long, Martin wrote: > >> I'm in agreement with Davide that any interim solution we can get running >> is better than the way it is working now. It's a regression

Re: Missing pO2 samples from CCR download [was: 4.7.8: a couple of questions]

why. If someone > sends it to me I'll be happy to add it. I said that before as well. > If hate to see Davide abandon Subsurface over this... > > /D > > > On June 18, 2018 5:39:43 AM GMT+09:00, "Long, Martin" < > mar...@longhome.co.uk> wrote: >> >&

ppO2 data has changed

Hi, I've noticed that the data downloaded from my Shearwater Petrel (JJ Divecan) has changed recently. Older dives have the actual recorded ppO2, whereas the newer dives have only the setpoint. Worse still, looking at the data files it looks like the actual ppO2 data is not recorded - the data is

Re: Missing pO2 samples from CCR download [was: 4.7.8: a couple of questions]

me up with a better way. >> >> Aaron >> >> On Sun, Jun 17, 2018, 11:53 Davide DB wrote: >> >>> On Thu, Jun 14, 2018, 15:34 Long, Martin wrote: >>> >>>> I'm in agreement with Davide that any interim solution we can get >>>&g

Android - expose tissues

Hi, I have a feature request, which I think is pretty small, but I'm a Java guy, and don't have the confidence to implement the native part. I'm currently writing some deco planning software for Android. It would be really great if I could query the Subsurface Android app for tissue loading, as

Re: Perdix AI won't download

Malcolm, Your best bet is to download it using Subsurface mobile, then sync it through to the desktop using your cloud account. I do this using both my Perdix AI and the Petrel 2 on my rebreather. Works a treat. Martin On 13 February 2018 at 18:43, Dirk Hohndel wrote: >

Re: Legacy Bluetooth missing again

I seem to have got it back by: - Deleting app and reinstalling - Deleting the pairing (in phone BT settings) and recreating Though I tried several times. Both of those steps on their own didn't seem to work. Regards Martin On 5 July 2018 at 13:34, Long, Martin wrote: > Hi, > >

Re: Legacy Bluetooth missing again

Ah, so maybe it disappeared because I'd paired my petrel with my PC in order to test the ppo2 download. Thing is I'd tried unpairing and re-pairing several times, to no avail. Anyway it's working now, and the good news is that the ppO2 data also came through for my new dives. Excellent work. On

Re: Legacy Bluetooth missing again

me to rely on stops working. Martin On 5 July 2018 at 16:41, Dirk Hohndel wrote: > > > On Jul 5, 2018, at 8:29 AM, Long, Martin wrote: > > > > Ah, so maybe it disappeared because I'd paired my petrel with my PC in > order to test the ppo2 download. > > Yes - I c

Re: Legacy Bluetooth missing again

Just had a brainwave, and pulled the USB dongle out of my PC. Re-paired on phone, and suddenly it all works. I think the Petrel is doing a scan, and latching onto the first BT device it remembers, which is then preventing it from pairing properly with the phone (although it SEEMS to complete

Re: Bluetooth fails on mobile

On 11 April 2018 at 11:42, Davide DB wrote: > On 11 April 2018 at 12:36, Davide DB wrote: > > On 11 April 2018 at 12:28, Willem Ferguson > > wrote: > > > >> Davide, > >> > >> I think these are two separate issues. Peter

Re: Bluetooth fails on mobile

Is there any chance of adding back in the ability to select either the BT or LE address for a dual stack device? Forcing it to use the legacy bluetooth stack was the only way I could download dives successfully without crashing the BLE stack on my phone and/or Shearwater. Thanks Martin On 13

Re: Problems with gases on Shearwater

appened when added the dives to a trip, and renumbered them. > > The second problem, however, is not so much a bug as a challenge. How to > map transmitter data to gasses. > > I'll keep you posted > > thanks > > Martin > > On Thu, 6 Dec 2018 at 15:42, Jef Driesen wrote: &g

Re: Problems with gases on Shearwater

. The second problem, however, is not so much a bug as a challenge. How to map transmitter data to gasses. I'll keep you posted thanks Martin On Thu, 6 Dec 2018 at 15:42, Jef Driesen wrote: > On 2018-12-05 17:17, Long, Martin wrote: > > I've noticed some problems with the import

Re: Problems with gases on Shearwater

wrote: > On Wed, Dec 5, 2018 at 8:18 AM Long, Martin wrote: > > > > 1) I just imported 4 dives from last weekend, all CCR. The first 3 > >were on 13/60 diluent and the last one on 15/57. However, it put > >all of the divers in as 15/57, which seems to just be

Re: Legacy Bluetooth Vs LE regression on Android / Shearwater.

I've found a thread: http://lists.subsurface-divelog.org/pipermail/subsurface/2018-July/032464.html However in that thread I managed to fix myself eventually. Those steps don't seem to be working now. Legacy doesn't show, BLE does, but doesn't work. On Tue, 26 Mar 2019, 00:37 Long, Martin

Re: Legacy Bluetooth Vs LE regression on Android / Shearwater.

this a bit easier on the user. On Tue, 26 Mar 2019, 18:55 Long, Martin, wrote: > I've found a thread: > http://lists.subsurface-divelog.org/pipermail/subsurface/2018-July/032464.html > > However in that thread I managed to fix myself eventually. Those steps > don't seem to be work

Re: Shearwater / CCR / ppO2 tracking

On Wed, 13 Mar 2019 at 03:27, Dirk Hohndel wrote: > On Tue, Mar 12, 2019 at 05:07:04PM -0700, Linus Torvalds wrote: > > On Tue, Mar 12, 2019 at 8:29 AM Long, Martin > wrote: > > > > > > The old problem of the ppO2 setpoint being shown or imported, rather > tha