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, pri
> 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
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 r
Somali,
I'm not a mentor. Mentors haven't yet been assigned as this happens much
later in the process. However, I can give you some feedback on your
proposal.
The first thing you should know is that there are people interested in
almost every project on the list. It will be competitive, and those
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
>
>
>>
> *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 gr
>
>
>> That sounds good. The specification uses the word "groups", but I don't
>> really like this because groups seems to imply that an item belongs to a
>> single group. I prefer "sets". My Suunto dive computer, for example would
>> be part of both my "UK Cold Water" set, and my "Tropical" set, a
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
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/
On 7 May 2015 at 07:28, Lubomir I. Ivanov 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 repo), and then merg
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'
On 29 May 2015 at 14:23, Dirk Hohndel 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 us
>
>
> Doing this via ssh seemed easier and straight forward as it integrated
> into an existing backend infrastructure, but the more time I spent
> thinking about the details of how this would be implemented, the more I
> questioned my earlier assumptions.
>
>
I always just felt icky about this. Us
>
>
> Are there other characters that are legal?
'+' is often used as a sub-address delimiter. GMail uses it to allow you to
create 'disposable' addresses. Users may use it to create mutliple accounts
for a single GMail account.
> A quick search for patterns for
> legal email addresses was a bi
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
workflo
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 a
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:
> Correct. We currently d
I believe it is a simple setting in the manifest. android:installLocation
which can be either "preferExternal" or "auto" (or not present, to disallow
moving to SD). I suspect this may have changed.
However, there are certain types of app which can not/should not be moved
to SD. It may be that sub
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 and myself cannot make a
> >> connection at all because an ordinary bluetoo
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 Apr
The BLE thing has basically made subsurface unusable for me for the last
month or so. Oddly, it works fine with my Perdix AI, but not with the
dual-stack Petrel 2 that's wired up to my rebreather - last time I was able
to use it was when I was able to select and force the legacy BT stack.
Does thi
On 25 April 2018 at 09:07, Chirana Gheorghita Eugeniu Theodor <
off...@adaptcom.ro> wrote:
> Hmm very weird.
> I use now latest 4.7.8 and successfully connects to Petrel 1 but will not
> connect to mh older tusa zen iq-900 over usb ftdi.
>
It's likely to connect to Petrel one because it is single
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 trip
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 Kreol
t; > On May 14, 2018, at 1:40 PM, Long, Martin 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* to be deterministic. Tapping the sa
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
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 I
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 m
7 June 2018 at 12:02, 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
patch. No idea 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> wr
l have a look at it again and try and come 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 i
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,
>
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 5
oftware I've come 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.
Just a small further update. I seem to have reproduced the problem. But
haven't been able to break back out of the state using any of the suggested
means.
Opened subsurface on PC, and did a test download, worked OK.
Back to phone, and Petrel has completely disappeared from subsurface. It's
also ju
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 succe
valds
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
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:
> On 2018-12-05 17:17, Long, Martin wrote:
> > I've noticed some problems wit
like it happened 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, Je
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
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
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
On 26 October 2015 at 17:24, Tomaz Canabrava wrote:
> dude... I have no idea.
> are you sure that CMake found the right Qt ?
>
> try to look at CMakeCache.txt, look for Qt5_DIR
>
>
I'm getting the same issue.
Qt5_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/Qt5
I have no idea what this means thoug
>
>
>
> 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 buil
On 26 October 2015 at 21:01, Dirk Hohndel 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 in that area has cha
>
>
> 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.
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 seve
Excellent. Thanks for the input. I'll continue along my current line
of work, and hopefully there should be a patch within the next few
days.
Best
Martin
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/c
Ok... I'll do my best. I'm a complete xslt newbie, so it's a little
bit of a learning, curve, but I've already cracked what I believe is
the biggest hurdle (splitting the buddies).
Small patches shouldn't be a problem.
Martin
___
subsurface mailing list
You'll probably see I've added a few patches. Hopefully these are ok.
This should be the bulk of it. I still want to look a bit further into
some of the details. There may be some other useful bits I can extract
such as start/end pressure etc. However, it looks to be a lot more
compliant now, if n
> This extension is something that we need to make sure is available on all
> the xslt libraries we use. At least Windows and Mac need to be tested. On my
> Ubuntu it works fine, but how about other Linux distributions? I do remember
> that I tried to use the node-set in the past but had to give it
On 10 December 2014 at 13:25, Dirk Hohndel 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 g
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
___
subsurface mailing list
subsur
Ok, if the buddy part works on Windows then I'll leave it using the xt
namespace rather than risk it not working if I change it.
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/sub
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 wi
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" wrote:
> On Wed, Dec 10, 2014 at 11:15:54PM +, Long, Martin wrote:
> > I think I'm starting to be the 'annoying neighbour' :-)
&
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
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 wa
> In general I have a dim view of the UDDF format (it's over designed and
> horribly verbose), but that doesn't mean that we shouldn't do it right on
> export.
Yes, and yes. Although it is a little more normalised than the
subsurface format, which feels a bit nicer for handling buddies,
sites, tri
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.
> Can you elaborate on this one as on my divelog all the dive computers are
> listed on the settings section and the original code worked with that
> properly. The sample dives are incorrect in this regard, but when you open
> them in Subsurface and save to new file, they get the stored in the sett
On 13 December 2014 at 16:40, Dirk Hohndel 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 removed, then it
So, the info in every profile (for my Suunto) is:
And the details in the section, when I add a nickname:
So, it looks like there are no version details, or fimware. I suppose
if there is more data then it might create this section anyway.
Also, if the section isn't there, then log -> edit
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
http://lists.subsurface-divelog.org/cgi-bin/mailman/listin
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 th
closely 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.
>
> miik
On 13 December 2014 at 23:33, Long, Martin 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
libd
The last patch brings it all inline with the spec, and passing the schema.
There is still some work to be done, however that will take more time.
I believe it is now sufficient for release. I can add in event types
and more equipment mapping after the release.
Thanks for all the help.
___
>
> 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 do
> 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 soon
On 5 January 2015 at 04:02, Linus Torvalds
wrote:
>
> On Jan 4, 2015 5:50 PM, "Gary David" 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 do this? If so, I would appreciate an
I'd love to see more equipment options, and equipment 'sets'. So stuff like
Male the "suit" field a type of equipment.
Make cylinders and weights follow the same scheme.
Add regs, mask, fins, computer, CCR, BCD, anything goes I guess.
Allow predifined equipment sets to be selected. eg
"Travel" s
Going to post this separately, and sorry for top posting in the last
one, gmail makes that an easy mistake.
Better options for print layouts. Even possibility for advance uses to
edit template files.
I find the options for printing to be quite limited. For example I
often write a quite long, deta
> 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,
To: k...@streit.cc
CC:
r...@virtual-sub.org
stephan.ve...@aquadivelog.org
str...@streit.cc
borisboes...@users.sourceforge.net
jefdrie...@telenet.be
pmaresc...@yahoo.com
dan...@mohni.net
creind...@frobese.de
sandra.ster...@gmx.net
wrob...@pld-linux.org
Hi,
Please accept my apologies for the distri
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 wrote:
>
>> On Feb 11, 2015, at 3:44 PM, Lubomir I. Ivanov wrote:
>>
>> On 8 February 2015
75 matches
Mail list logo
