Re: Subsurface-mobile for iOS

[Murillo Bernardes]

On Wed, Nov 29, 2017 at 2:04 PM, Dirk Hohndel  wrote:

>
> I forgot my power supply and my Mac is literally about to shut down. For
> some reason iTunes rejected my upload, so right now all I can do is tease
> you with a screen shot...
>
> The ironic thing is that for once I didn't take a dive computer with me on
> this business trip, so I wasn't able to check if the download via BLE
> actually works, but you'll have to admit that this looks promising :-)
>
> Hopefully I'll find time tomorrow to figure out why my upload to
> TestFlight was rejected and can then create a first alpha version of
> Subsurface-mobile 2.0.1 for iOS.
>
> Just out of curiosity - who here actually has an iPad or iPhone and would
> be testing this? We seem to have just a few active users of
> Subsurface-mobile for iOS, based on the iTunes stats... but I'm guessing
> this might change once we support download from BLE dive computers :-)
>
>
I'm eager to test this on my iPhone with a Perdix AI.




> Anyway, gotta send this before the laptop shuts down.
>
> /D
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
>


-- 
Murillo Bernardes
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Subsurface-mobile for iOS

[Miika Turkia]

On Wed, Nov 29, 2017 at 8:04 AM, Dirk Hohndel  wrote:

>
> I forgot my power supply and my Mac is literally about to shut down. For
> some reason iTunes rejected my upload, so right now all I can do is tease
> you with a screen shot...
>
> The ironic thing is that for once I didn't take a dive computer with me on
> this business trip, so I wasn't able to check if the download via BLE
> actually works, but you'll have to admit that this looks promising :-)
>
> Hopefully I'll find time tomorrow to figure out why my upload to
> TestFlight was rejected and can then create a first alpha version of
> Subsurface-mobile 2.0.1 for iOS.
>
> Just out of curiosity - who here actually has an iPad or iPhone and would
> be testing this? We seem to have just a few active users of
> Subsurface-mobile for iOS, based on the iTunes stats... but I'm guessing
> this might change once we support download from BLE dive computers :-)
>

Cool. Time to book next scuba trip to be able to test this when it is still
fresh :D (It really doesn't make much sense to download data that has
already been downloaded, you know)

miika
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Martin Měřinský]

On Wed, 2017-11-29 at 07:34 +0200, Willem Ferguson wrote:
> On 29/11/2017 00:31, Tim Wootton wrote:
> > On 28/11/17 20:18, Bill Perry wrote:
> > > It appears that Wikipedia pushes the term "Diving Cylinder"
> > > https://en.wikipedia.org/wiki/Diving_cylinder
> > > And in their terminology section, they say:
> > > 
> > > "The term "diving cylinder" tends to be used by gas equipment
> > > engineers, manufacturers, support professionals, and divers
> > > speaking British English. "Scuba tank" or "diving tank" is more
> > > often used colloquially by non-professionals and native speakers
> > > of
> > > American English"
> > 
> > If that's the case perhaps we could use "tank" and just replace
> > "tank"
> > with "cylinder" in the UK English translation
> 
> I suggest that the term goes with the units preference in the 
> Preferences panel. If the preference is set to Imperial, then use
> tank. 
> For the rest of the world that does not use imperial, if the
> preference is set to metric then use cylinder.

Please no. Units has nothing to do with cylinder/tank think.

And I personaly do not think, translating cylinder/tank is worth the
work.

Probably every diver understands both terms. For our UI, choose one and
be consistent with it. I don't care which one will it be.

Martin M.
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Willem Ferguson]

On 29/11/2017 00:31, Tim Wootton wrote:

On 28/11/17 20:18, Bill Perry wrote:

It appears that Wikipedia pushes the term "Diving Cylinder"
https://en.wikipedia.org/wiki/Diving_cylinder
And in their terminology section, they say:

"The term "diving cylinder" tends to be used by gas equipment engineers, manufacturers, support 
professionals, and divers speaking British English. "Scuba tank" or "diving tank" is more 
often used colloquially by non-professionals and native speakers of
American English"

If that's the case perhaps we could use "tank" and just replace "tank"
with "cylinder" in the UK English translation
I suggest that the term goes with the units preference in the 
Preferences panel. If the preference is set to Imperial, then use tank. 
For the rest of the world that does not use imperial, if the preference 
is set to metric then use cylinder. We NEVER use the term "tank"

Does this sound reasonable?
Kind regards,
willem



--
This message and attachments are subject to a disclaimer.
Please refer to 
http://upnet.up.ac.za/services/it/documentation/docs/004167.pdf for full 
details.

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Dirk Hohndel]

Oh... memory lane... this actually made me compile Subsurface-1.0 again. And as 
expected, the hardest part was to find a matching libdivecomputer version. I 
really need to tackle that submodule thing. But instead I'm spending time on 
archeology... :-)

> On Nov 28, 2017, at 12:45 PM, Linus Torvalds  
> wrote:
> On Tue, Nov 28, 2017 at 12:29 PM, Dirk Hohndel  > wrote:
> >
> > You mean the amazing user interface that we used to have? The brilliance 
> > that was Subsurface 1.0?
> 
> I don't think "brilliance" really is sufficient to describe the stark beauty 
> of early versions. 

Yes, definitely.

> The tank pressure graph that shrinks upwards is particularly good.
> 
> It's the same axis as the depth, so smaller values are higher. Logical!

Yes, very much so - but by 1.0 we had already lost that brilliant concept.
Some ignorant twit made you change this. I found the commit:

commit d5b102bdf3c2f1e78c51fe8b81e8ff134c30d012
Author: Dirk Hohndel 
Date:   Fri Sep 16 20:53:05 2011 -0700

Flip tank pressure graph to show the RIGHT way

This annoyed me from the first moment Linus added the tank pressure graph.
As the pressure goes down, the graph needs to go down. Seriously.

Signed-off-by: Dirk Hohndel 

Just 10 days before 1.0 came out... and in those ten days you added 72 commits 
to Subsurface. Those were the days :-)

> Me likey.​

Yeah, that was part of the problem... :-)

/D

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Lubomir I. Ivanov]

On 29 November 2017 at 02:54, Lubomir I. Ivanov  wrote:
>
> the containers on ones back when scuba diving are far from "large",
> which implies that unless the word "tank" is used prefixed with
> something like "small", one might assume that the word is misused or
> just slang.
> on the other hand, "cylinder" is quite vague, as it's a geometric
> object if not prefixed with "gas"...and still seems like slang.
>
> in my country we call them "bottles" and both "tanks" and "cylinders"
> don't translate well as they have different and or vague(er) meanings.
>

actually "tank" and "bottle" seem like the slang words and "cylinder"
is the vague, but more scientific one.

lubomir
--
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Lubomir I. Ivanov]

if one goes in google and searches for the actual English dictionary
meaning of the word "tank" (not the armored vehicle), he/she might
find that the majority of dictionaries have the adjective "large" in
the descriptions for the word.

examples:
http://www.dictionary.com/browse/tank
"a large receptacle, container, or structure for holding a liquid or gas"
https://www.collinsdictionary.com/dictionary/english/tank
"A tank is a large container for holding liquid or gas."
https://www.merriam-webster.com/dictionary/tank
"a usually large receptacle for holding, transporting, or storing
liquids (such as water or fuel)"

the containers on ones back when scuba diving are far from "large",
which implies that unless the word "tank" is used prefixed with
something like "small", one might assume that the word is misused or
just slang.
on the other hand, "cylinder" is quite vague, as it's a geometric
object if not prefixed with "gas"...and still seems like slang.

in my country we call them "bottles" and both "tanks" and "cylinders"
don't translate well as they have different and or vague(er) meanings.

lubomir
--
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Rick Walsh]

On 29 Nov. 2017 9:31 am, "Tim Wootton"  wrote:

On 28/11/17 20:18, Bill Perry wrote:
> It appears that Wikipedia pushes the term "Diving Cylinder"
> https://en.wikipedia.org/wiki/Diving_cylinder
> And in their terminology section, they say:
>
> "The term "diving cylinder" tends to be used by gas equipment engineers,
manufacturers, support professionals, and divers speaking British English.
"Scuba tank" or "diving tank" is more often used colloquially by
non-professionals and native speakers of
> American English"
If that's the case perhaps we could use "tank" and just replace "tank"
with "cylinder" in the UK English translation
>
> So from Wikipedia's perspective it appears to be somewhat a American
English vs British English thing...
> Although it appears that many of the Dive computer manufacturers have
leaned towards "tank".
>
>
> Could it be handled as a "language" thing like other translation items?
> using the locale information?
> Even if it could be done that way is it a good idea or worth it?
>
> It is kind of funny (actually in a sad way) that different dive computers
from the same manufacturer are not consistent with respect to their
terminology,
> and a couple device manuals intermix the terms in the same manual.
>
>  bill
>
>
>

Just out of interest I decided to look through (use the search function)
some diving resources on my computer (admittedly mostly tech related - I'll
see if I can check padi's encyclopedia of recreational diving when I get
home). It appears we're not the only one who can't decide on tank vs
cylinder.

Deco for divers: consistent use of cylinder (except when referring to water
tanks)
GUE tech 1 manual: mixed use of cylinder and tank throughout, even in the
same paragraph
GUE SOPs: mixed use throughout
Cave Divers Association of Australia training standards: mixed use
throughout, even within same sentence
Hollis DG03 user manual: consistent use of tank
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Tim Wootton]

On 28/11/17 20:18, Bill Perry wrote:
> It appears that Wikipedia pushes the term "Diving Cylinder"
> https://en.wikipedia.org/wiki/Diving_cylinder
> And in their terminology section, they say:
>
> "The term "diving cylinder" tends to be used by gas equipment engineers, 
> manufacturers, support professionals, and divers speaking British English. 
> "Scuba tank" or "diving tank" is more often used colloquially by 
> non-professionals and native speakers of
> American English"
If that's the case perhaps we could use "tank" and just replace "tank"
with "cylinder" in the UK English translation
>
> So from Wikipedia's perspective it appears to be somewhat a American English 
> vs British English thing...
> Although it appears that many of the Dive computer manufacturers have leaned 
> towards "tank".
>
>
> Could it be handled as a "language" thing like other translation items?
> using the locale information?
> Even if it could be done that way is it a good idea or worth it?
>
> It is kind of funny (actually in a sad way) that different dive computers 
> from the same manufacturer are not consistent with respect to their 
> terminology,
> and a couple device manuals intermix the terms in the same manual.
>
>  bill
>
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface


___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: ReleaseNotes.txt and merge conflicts

[Lubomir I. Ivanov]

On 28 November 2017 at 22:52, Lubomir I. Ivanov  wrote:
> On 28 November 2017 at 22:45, Dirk Hohndel  wrote:
>> On Tue, Nov 28, 2017 at 10:32:24PM +0200, Lubomir I. Ivanov wrote:
>>> >
>>> > Thanks for figuring this out, Lubomir!
>>> >
>>> > so, how are we supposed to write those now? A simple hack would of course 
>>> > be
>>> > to actually have a folder release_notes where everybody add _files_ for
>>> > things to report and then for a release we cat all those files…
>>>
>>> yesterday, we figured out that if we have a "release notes" file where
>>> multiple branches / commits add notes on top of it (i.e. line 1) there
>>> won't be any conflicts between the branches if we add this:
>>>
>>> /ReleaseNotes.txt -text merge=union
>>> in a file /.gitattributes
>>>
>>> until we restructure our ReleaseNotes, we have to resolve conflicts
>>> locally and force push to the remote branch from which the PR is
>>> happening.
>>> the github "resolve conflicts" feature with the online editor merges
>>> master into the user branch without fast-forward (--no-ff) and i don't
>>> think we want that.
>>
>> Lubomir, can you create a pull request that adds the .gitattributes file
>> as well as a Changelog file in the correct format plus a note at the top
>> of ReleaseNotes.txt that points to that (and of course we need to adjust
>> the PR instructions as well).
>>
>> I can do that this evening if it's not clear what I'm looking for :-/
>>
>
> should the Changelog file be in the root folder?
>
> i'm not sure about the format

made a PR:
https://github.com/Subsurface-divelog/subsurface/pull/883

not sure if i got it 100% right, so let's amend the PR if needed.

thanks
lubomir
--
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: ReleaseNotes.txt and merge conflicts

[Lubomir I. Ivanov]

On 28 November 2017 at 22:45, Dirk Hohndel  wrote:
> On Tue, Nov 28, 2017 at 10:32:24PM +0200, Lubomir I. Ivanov wrote:
>> >
>> > Thanks for figuring this out, Lubomir!
>> >
>> > so, how are we supposed to write those now? A simple hack would of course 
>> > be
>> > to actually have a folder release_notes where everybody add _files_ for
>> > things to report and then for a release we cat all those files…
>>
>> yesterday, we figured out that if we have a "release notes" file where
>> multiple branches / commits add notes on top of it (i.e. line 1) there
>> won't be any conflicts between the branches if we add this:
>>
>> /ReleaseNotes.txt -text merge=union
>> in a file /.gitattributes
>>
>> until we restructure our ReleaseNotes, we have to resolve conflicts
>> locally and force push to the remote branch from which the PR is
>> happening.
>> the github "resolve conflicts" feature with the online editor merges
>> master into the user branch without fast-forward (--no-ff) and i don't
>> think we want that.
>
> Lubomir, can you create a pull request that adds the .gitattributes file
> as well as a Changelog file in the correct format plus a note at the top
> of ReleaseNotes.txt that points to that (and of course we need to adjust
> the PR instructions as well).
>
> I can do that this evening if it's not clear what I'm looking for :-/
>

should the Changelog file be in the root folder?

i'm not sure about the format
should it be something like:

-
<---  new entries are added here on top and once we are
done we place a version X on top

- entry 1
- entry 2
- entry 3
- entry 4

some version 

- entry 1
- entry 2
- entry 3
- entry 4
--

lubomir
--
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: ReleaseNotes.txt and merge conflicts

[Dirk Hohndel]

On Tue, Nov 28, 2017 at 10:32:24PM +0200, Lubomir I. Ivanov wrote:
> >
> > Thanks for figuring this out, Lubomir!
> >
> > so, how are we supposed to write those now? A simple hack would of course be
> > to actually have a folder release_notes where everybody add _files_ for
> > things to report and then for a release we cat all those files…
> 
> yesterday, we figured out that if we have a "release notes" file where
> multiple branches / commits add notes on top of it (i.e. line 1) there
> won't be any conflicts between the branches if we add this:
> 
> /ReleaseNotes.txt -text merge=union
> in a file /.gitattributes
> 
> until we restructure our ReleaseNotes, we have to resolve conflicts
> locally and force push to the remote branch from which the PR is
> happening.
> the github "resolve conflicts" feature with the online editor merges
> master into the user branch without fast-forward (--no-ff) and i don't
> think we want that.

Lubomir, can you create a pull request that adds the .gitattributes file
as well as a Changelog file in the correct format plus a note at the top
of ReleaseNotes.txt that points to that (and of course we need to adjust
the PR instructions as well).

I can do that this evening if it's not clear what I'm looking for :-/

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Lubomir I. Ivanov]

On 28 November 2017 at 22:29, Dirk Hohndel  wrote:
>
>
> On November 28, 2017 12:05:09 PM PST, Linus Torvalds 
>  wrote:
>>On Tue, Nov 28, 2017 at 11:57 AM, Linus Torvalds
>> wrote:
>>>
>>> Maybe the discussion still exists somewhere (it would likely be late
>>> August and early September 2011).
>>
>>Couldn't find anything in my emails.
>>
>>But I did find some funky screenshots of early versions of subsurface.
>>
>>We've definitely lost something over time.
>
> You mean the amazing user interface that we used to have? The brilliance that 
> was Subsurface 1.0?
>
>

the profile background used to be black and it was in a tab. :-)

lubomir
--
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: ReleaseNotes.txt and merge conflicts

[Lubomir I. Ivanov]

On 28 November 2017 at 22:24, Robert Helling  wrote:
> Hi,
>
>
> On 28. Nov 2017, at 03:48, Dirk Hohndel  wrote:
>
> We should try this - but in a simpler way. Have an actual Changelog style
> file instead of the current format.
> So change ReleaseNotes.txt to simply say "As of v4.7.5 we are tracking the
> changes in the Changelog file"
> I can come up with a way to add the version markers in the Changelog file
> automatically at release time.
> And if I feel ambitious, I can even copy things over
>
> Thanks for figuring this out, Lubomir!
>
>
> so, how are we supposed to write those now? A simple hack would of course be
> to actually have a folder release_notes where everybody add _files_ for
> things to report and then for a release we cat all those files…
>

yesterday, we figured out that if we have a "release notes" file where
multiple branches / commits add notes on top of it (i.e. line 1) there
won't be any conflicts between the branches if we add this:

/ReleaseNotes.txt -text merge=union
in a file /.gitattributes

until we restructure our ReleaseNotes, we have to resolve conflicts
locally and force push to the remote branch from which the PR is
happening.
the github "resolve conflicts" feature with the online editor merges
master into the user branch without fast-forward (--no-ff) and i don't
think we want that.

lubomir
--
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Dirk Hohndel]

On November 28, 2017 12:05:09 PM PST, Linus Torvalds 
 wrote:
>On Tue, Nov 28, 2017 at 11:57 AM, Linus Torvalds
> wrote:
>>
>> Maybe the discussion still exists somewhere (it would likely be late
>> August and early September 2011).
>
>Couldn't find anything in my emails.
>
>But I did find some funky screenshots of early versions of subsurface.
>
>We've definitely lost something over time.

You mean the amazing user interface that we used to have? The brilliance that 
was Subsurface 1.0?


-- 
from my phone.
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: ReleaseNotes.txt and merge conflicts

[Robert Helling]

Hi,


> On 28. Nov 2017, at 03:48, Dirk Hohndel  wrote:
> 
> We should try this - but in a simpler way. Have an actual Changelog style 
> file instead of the current format.
> So change ReleaseNotes.txt to simply say "As of v4.7.5 we are tracking the 
> changes in the Changelog file"
> I can come up with a way to add the version markers in the Changelog file 
> automatically at release time.
> And if I feel ambitious, I can even copy things over
> 
> Thanks for figuring this out, Lubomir!

so, how are we supposed to write those now? A simple hack would of course be to 
actually have a folder release_notes where everybody add _files_ for things to 
report and then for a release we cat all those files…

Best
Robert


signature.asc
Description: Message signed with OpenPGP
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Bill Perry]

It appears that Wikipedia pushes the term "Diving Cylinder"
https://en.wikipedia.org/wiki/Diving_cylinder
And in their terminology section, they say:

"The term "diving cylinder" tends to be used by gas equipment engineers, 
manufacturers, support professionals, and divers speaking British English. 
"Scuba tank" or "diving tank" is more often used colloquially by 
non-professionals and native speakers of
American English"

So from Wikipedia's perspective it appears to be somewhat a American English vs 
British English thing...
Although it appears that many of the Dive computer manufacturers have leaned 
towards "tank".


Could it be handled as a "language" thing like other translation items?
using the locale information?
Even if it could be done that way is it a good idea or worth it?

It is kind of funny (actually in a sad way) that different dive computers from 
the same manufacturer are not consistent with respect to their terminology,
and a couple device manuals intermix the terms in the same manual.

 bill


___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Pedro Neves]

On 28-11-2017 19:23, Dirk Hohndel wrote:


I'd love to hear from more people here.


Hi all:

Although I'm not a (native) english speaker, I use the term "tank" more 
often than "cylinder".


So tank +1 it is...

Cheers:

Pedro
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Linus Torvalds]

On Tue, Nov 28, 2017 at 11:57 AM, Linus Torvalds
 wrote:
>
> Maybe the discussion still exists somewhere (it would likely be late
> August and early September 2011).

Couldn't find anything in my emails.

But I did find some funky screenshots of early versions of subsurface.

We've definitely lost something over time.

  Linus
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Linus Torvalds]

On Tue, Nov 28, 2017 at 11:23 AM, Dirk Hohndel  wrote:
>
> I'd love to hear from more people here.

So I have this dim memory that early on we had exactly this "tank vs
cylinder" discussion, and ended up using "cylinder" because it was
more common in some document.

Because we actually used to have "tank". See commit b176daf6d ("Do
better cylinder information management") from six years ago.

Maybe the discussion still exists somewhere (it would likely be late
August and early September 2011).

Because I always used "tank", but the argument was that "cylinder" is
the correct term.

End  result: I don't much care, other than a slight annoyance at the
back-and-forth ;)

 Linus
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Dirk Hohndel]

Hey Bill,

Thanks for that detailed analysis. That's actually great data.

I'd love to hear from more people here.

Obviously we won't change the data structures (they are cylinders). But
for the UI I'm open to a discussion on the preferred term. It seems like
the dive computer makers are leaning towards tank. Personally, that's the
term I use as well ("Hey Linus, would you grab a tank for me as well?" -
I'd never ask someone to grab a "cylinder" for me or to help me with my
"cylinder", etc).

So we have two votes for tank here so far :-)

/D

On Tue, Nov 28, 2017 at 12:08:55PM -0600, Bill Perry wrote:
> I believe that the answer of changing to the term "cylinder" from "tank" is 
> no.
> 
> Here is is the reason.
> Most manufacturers appear to have settled on the term "tank" not "cylinder".
> I checked several manuals.
> 
> Aeris Atmos AI
> Aeris Atmos Elite
> Aeris A300 CS
> Atomic Cobalt
> Aqualung i750tc
> Aqualung i550
> Mares Icon HD
> Oceanic OCI
> Oceanic vtx
> Scubapro Aladin h
> Scubapro Mantis 2
> Scubapro g2
> Scubapro/Uwatec Galileo Sol
> Scubapro/Uwatec Galileo LUNA
> Shearwater perdix
> Sherwood Amphos
> Sherwood Sage
> Sherwood Vision
> Sherwood Wisdom 3
> Suunto EONSteel
> Suunto D4i
> Suunto D6i
> Suunto DX
> 
> They all use the term "tank".
> A few (g2, EONSteel, Wisdom) have 1 or 2 references to cylinder; however, 
> "tank" is the normal term.
> 
> Suunto Zoop: uses the term "cylinder" throughout its manual, but then they 
> use "tank" to refer to "tank pressure".
> Suunto Cobra: uses the term "cylinder" throughout its manual, but has 3 
> references to "tank pressure".
> Suunto Suunto HelO2: uses both
> Shearwater: Petrel 2 never refers to either "tank" or Cylinder".
> Oceanic proplus 2: uses both
> Oceanic proplus X: never uses either "tank" or "cylinder" and uses "Gas n" or 
> "Gas pressure"
> 
> 
> So far I've only seen the Suunto Zoop, Suunto HelO2,  and the Oceanic proplus 
> 2 using the term "cylinder".
> 
> I would heavily lean to the term "tank" as that is in more wide spread use in 
> the computer documentation
> and many dive computers use the word "tank" or "T" on the actual computer 
> display.
> 
> I would prefer not to use a different term than the actual manufacturer 
> documentation.
> 
> 
> --- bill
> 
> 
> 
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Bill Perry]

I believe that the answer of changing to the term "cylinder" from "tank" is no.

Here is is the reason.
Most manufacturers appear to have settled on the term "tank" not "cylinder".
I checked several manuals.

Aeris Atmos AI
Aeris Atmos Elite
Aeris A300 CS
Atomic Cobalt
Aqualung i750tc
Aqualung i550
Mares Icon HD
Oceanic OCI
Oceanic vtx
Scubapro Aladin h
Scubapro Mantis 2
Scubapro g2
Scubapro/Uwatec Galileo Sol
Scubapro/Uwatec Galileo LUNA
Shearwater perdix
Sherwood Amphos
Sherwood Sage
Sherwood Vision
Sherwood Wisdom 3
Suunto EONSteel
Suunto D4i
Suunto D6i
Suunto DX

They all use the term "tank".
A few (g2, EONSteel, Wisdom) have 1 or 2 references to cylinder; however, 
"tank" is the normal term.

Suunto Zoop: uses the term "cylinder" throughout its manual, but then they use 
"tank" to refer to "tank pressure".
Suunto Cobra: uses the term "cylinder" throughout its manual, but has 3 
references to "tank pressure".
Suunto Suunto HelO2: uses both
Shearwater: Petrel 2 never refers to either "tank" or Cylinder".
Oceanic proplus 2: uses both
Oceanic proplus X: never uses either "tank" or "cylinder" and uses "Gas n" or 
"Gas pressure"


So far I've only seen the Suunto Zoop, Suunto HelO2,  and the Oceanic proplus 2 
using the term "cylinder".

I would heavily lean to the term "tank" as that is in more wide spread use in 
the computer documentation
and many dive computers use the word "tank" or "T" on the actual computer 
display.

I would prefer not to use a different term than the actual manufacturer 
documentation.


--- bill



___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Stefan Fuchs]

Am 28.11.2017 um 09:50 schrieb Stefan Fuchs:
>
>> "Cylinder bar" +1
>> "Tank bar" 0
>> "Gas bar" +5
>>
>
And the winner is... "Gas bar"

PR for this will follow...

-- 

Stefan Fuchs
E-Mail: sfu...@gmx.de 

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Salvador Cuñat]

Gas or gases bar  +1.
Current Spanish translation looks pretty ridiculous.

Best regards,
Salva.
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RFC: Print templates for 4 dives per page and 6 dives per

[Chirana Gheorghita Eugeniu Theodor]

Hey,
>From my point of view the profile of the dive is the modt important. It can
tell exactly what went wrong or good and why during a dive.

On Nov 28, 2017 02:27, "Hartley Horwitz"  wrote:

> -- Forwarded message --
>> From: Willem Ferguson 
>> To: Subsurface Mailing List 
>> Cc:
>> Bcc:
>> Date: Sat, 25 Nov 2017 15:10:12 +0200
>> Subject: RFC: Print templates for 4 dives per page and 6 dives per page
>>
>> I attach two images for some print templates that I have been working
>> with. I would appreciate comments from any members of this list, but
>> especially from anyone who prints dives to paper.
>>
>
> HH - I'm a recreational diver and I 'used to' print out my logs.  When I
> moved to using Subsurface I wanted to get many diver/page to save paper and
> in that case I didn't care about the profile.  I did care about the notes.
> The thinking is that a dive operator doesn't care how long you spent at 30m
> or 40m, just that you did.  Or they don't care what your profile looked
> like, just that you did a night dive or something like that.
>
> Don't get me wrong. One of the key reasons I use Subsurface is the
> visualization of the dive, but I think only me and my dive partner care
> about that and in that case I use my laptop or handheld to view the
> profile.
>
>> My point of departure with this work is to accommodate divers why
>> frequently print dives. Three points: 1) The biggest limitation is that all
>> dive details (i.e. those shown on the Notes, Equipment and Information tabs
>> in Subsurface) cannot be fitted onto a single sheet of paper. Therefore I
>> assume that those who print dives are more likely to be those who dive in a
>> recreational environment and configuration. Such divers have fewer demands
>> from a printout, compared to technical/sidemount/rebreather divers.
>>
> [HH] agree
>
>> These print layouts are therefore geared towards recreational divers. 2)
>> I used "conventional" recreational dive log sheets available on the
>> Internet to determine what information is more likely to be relevant to a
>> recreational diver. 3) Though I have not been totally consistent, I assumed
>> that the information showed in the multiple-dives-per-page layouts should
>> not show information different from the one-dive-per-page layout. If space
>> is limiting, a subset of information on the one-page layout should be shown
>> on the layouts with less page space for each dive. Any comments on these
>> points of departure?
>>
>> *6 dives:* On the left is the current default layout. Biggest issue is
>> that the notes are mostly not shown or severely truncated. It is futile to
>> include the Notes in the 6-dive layout. A lot of information is shown here,
>> which are not shown in the one-page print layout (e.g. SAC rate, rating,
>> tags). In putting together a 6-dive layout, I decided to split the
>> templates into two: 1) a template that does not show the notes; 2) a
>> template that does not show the dive profile. This gives a diver a choice
>> to print whatever is more important for her/him. In these two derived
>> templates, I re-arranged the layout compared to the current template.
>>
>  [HH] given my comments above, it isn't surprising I prefer the 2nd layout
> for the 6-dive - the one with more space for notes and no profile.
>
>> Note that in all 6-dive layouts, the depth and time labels on the dive
>> profile are for all practical purposes illegible, and I suspect this is a
>> problem that is not easily solved. Note:
>>
>> 1) The gas information on my two templates are truncated if more than one
>> cylinder is used on a dive. The gas information in my templates are rather
>> cryptic, giving cylinder type, gas type and begin/end cylinder pressure. In
>> the existing 6-dive layout (leftmost in image) there is more information
>> given for gas, but this comes with a penalty in other aspects of the page
>> layout.
>>
>> 2) In the proposed 6-dive layout with dive notes (i.e. without dive
>> profile), the dive notes are truncated if there are too many notes. I often
>> write fairly lengthy dive notes, so in the multiple-diives-per-page
>> printouts, my notes are commonly truncated.
>>
>
> [HH] the space you've allocated for notes seems sufficient for my
> purposes.
>
>> *4 dives: *We currently do not have a 4-dive template. My rationale was
>> that if someone wanted a several dives per page and also both the dive
>> profile and the dive notes,  a 4-dive layout is the more viable than the
>> 6-dive layout.  Here also, if the dive notes are long, they are truncated.
>> This layout is a compromise to show more or less all the information
>> originally intended with the 6-dive layout.
>>
>
> [HH]  I no longer print out, but would use the 6-dive, no profile
> template. I just asked my wife and she likes the 4-dive template!  It just
> shows you that it is hard to have a 1 size fits all solution.
>
>> 

Re: Cylinder vs. tank -

[Tim Wootton]

Gas pressure or Gas press. +1
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Davide DB]

Gas bar +1
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Stefan Fuchs]

Hi Joakim,

Am 28.11.2017 um 09:39 schrieb Joakim Bygdell:
>
> "Cylinder bar" +1
> "Tank bar" 0
> "Gas bar" +2
>

> Any other votes? - Yeah, I know - what an important topic! ;-)
>
> Gas bar, since it contains info about  gasmixes and not cylinders.
Wow, that comes unexpected now! ;-)
But I can't say that's wrong. Hey, I didn't vote yet - I also vote for
"Gas bar"
Results updated above...

-- 

Stefan Fuchs
E-Mail: sfu...@gmx.de 

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: lots of activity

[Vincent Cresson]

  subsurface.log


I've joined the log when trying to download from the square.
Vincent.

Le 27 nov. 2017 23:10, "Dirk Hohndel"  a écrit :

Could I get a PR or patch with SOB?

/D

> On Nov 27, 2017, at 1:58 PM, Anton Lundin  wrote:
>
> On 27 November, 2017 - Dirk Hohndel wrote:
>
>>
>>> On Nov 27, 2017, at 12:09 PM, vavincavent  wrote:
>>>
>>> ok Dirk,
>>>
>>> Now i see the aladin square, but not functional.
>>> perhaps problem with usb and my phone.
>>> Divemate start automatiquely whent i connect the square.
>>
>> Which means that Subsurface never gets to see the device.
>> I cannot test this on my phone since OTG fails on mine - but I think
>> there’s a way to reset the setting for “open this app by default if
>> that device gets plugged in”… you’ll have to do that and pick
>> Subsurface-mobile as the app to start when your Square connects.
>
> We probably need to add some vid/pid to the Android manifest.
>
> This should do the trick:
> diff --git i/android-mobile/res/xml/device_filter.xml
w/android-mobile/res/xml/device_filter.xml
> index 83b42ea07..231b9a076 100644
> --- i/android-mobile/res/xml/device_filter.xml
> +++ w/android-mobile/res/xml/device_filter.xml
> @@ -13,4 +13,10 @@
> 
> 
> 
> +
> +
> +
> +
> +
> +
> 
>
>
> //Anton
>
>
> --
> Anton Lundin  +46702-161604
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Joakim Bygdell]

On 28 November 2017 at 09:03, Stefan Fuchs  wrote:

> Am 28.11.2017 um 07:52 schrieb Martin Měřinský:
>
> we really usually use "Cylinder" and only in 6 strings use "Tank".
>
>
> Shall we change EVERYTHING to "cylinder" or sometimes "cyl." (which
> we have already)?
> Would also mean the "Tank bar" becomes the "Cylinder bar"...
>
> In my opinion yes and yes.
>
>
> I already did change every string to "cylinder" or "cyl." save the "Tank
> bar". For the "Tank bar" I still hesitated because this maybe somehow has
> become a fixed phrase in Subsurface.
> So we have these votes up to now:
> "Cylinder bar" +1
> "Tank bar" 0
>
> Any other votes? - Yeah, I know - what an important topic! ;-)
>
Gas bar, since it contains info about  gasmixes and not cylinders.

>
>
> Best regards
> Stefan
>
> --
>
> Stefan Fuchs
> E-Mail: sfu...@gmx.de
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
>


-- 
Jocke
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Cylinder pressure data in samples for multiple cylinders and deleting one cylinder/pressure graph

[Stefan Fuchs]

Hi Everybody, hi Linus,

trying to fix and improve s.th. for a user with such a fancy DC like the
Lynx where you can track the cylinder pressure of your buddies.

The requested feature is simply to be able to delete the combination of
cylinder plus corresponding pressure graph from a dive.

More info, discussion and some first fixes already done are here:
https://github.com/Subsurface-divelog/subsurface/issues/869
https://github.com/Subsurface-divelog/subsurface/pull/870


Looking for comments how to continue. Thanks!


Best regards
Stefan

-- 

Stefan Fuchs
E-Mail: sfu...@gmx.de 

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cylinder vs. tank -

[Stefan Fuchs]

Am 28.11.2017 um 07:52 schrieb Martin Měřinský:
>> we really usually use "Cylinder" and only in 6 strings use "Tank".
>
>> Shall we change EVERYTHING to "cylinder" or sometimes "cyl." (which
>> we have already)?
>> Would also mean the "Tank bar" becomes the "Cylinder bar"...
> In my opinion yes and yes.
>
I already did change every string to "cylinder" or "cyl." save the "Tank
bar". For the "Tank bar" I still hesitated because this maybe somehow
has become a fixed phrase in Subsurface.
So we have these votes up to now:
"Cylinder bar" +1
"Tank bar" 0

Any other votes? - Yeah, I know - what an important topic! ;-)

Best regards
Stefan

-- 

Stefan Fuchs
E-Mail: sfu...@gmx.de 

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

[PATCH] android: Add new usb vid/pid's to manifest

[Anton Lundin]

This adds vid/pid of the recently added usb devices.

* EON Steel core
* Scubapro G2
* Scubapro Aladin Square

Signed-off-by: Anton Lundin 
---
 android-mobile/res/xml/device_filter.xml | 6 ++
 android/res/xml/device_filter.xml| 8 
 2 files changed, 14 insertions(+)

diff --git a/android-mobile/res/xml/device_filter.xml 
b/android-mobile/res/xml/device_filter.xml
index 83b42ea07..231b9a076 100644
--- a/android-mobile/res/xml/device_filter.xml
+++ b/android-mobile/res/xml/device_filter.xml
@@ -13,4 +13,10 @@
 
 
 
+
+
+
+
+
+
 
diff --git a/android/res/xml/device_filter.xml 
b/android/res/xml/device_filter.xml
index fc9333bdb..231b9a076 100644
--- a/android/res/xml/device_filter.xml
+++ b/android/res/xml/device_filter.xml
@@ -11,4 +11,12 @@
 
 
 
+
+
+
+
+
+
+
+
 
-- 
2.14.1

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface