[PATCH] User-manual: Facebook integration
Subject: [PATCH] User-manual: Add text and images for Facebook integration 5 images are changed and four more are added. Dirk, please read the paragraph marked *Important* to make sure it does not constitute utter rubbish. Signed-off-by: willem ferguson --- This is a patch notification without images, meant for our translators. Patch with images sent to Dirk Kind regards, willem >From 5b46302f35be132e4cedd9e5e6f27cf18b119c99 Mon Sep 17 00:00:00 2001 From: willem ferguson Date: Mon, 2 Feb 2015 09:07:17 +0200 Subject: [PATCH] User-manual: Add text and images for Facebook intergration 5 images are changed and four more are added. Dirk, please read the paragraph marked *Important* to make sure it does not constitute utter rubbish. Signed-off-by: willem ferguson --- Documentation/images/Pref1_f20.jpg | Bin 32729 -> 29611 bytes Documentation/images/Pref2_f20.jpg | Bin 24401 -> 21279 bytes Documentation/images/Pref3_f20.jpg | Bin 29302 -> 31237 bytes Documentation/images/Pref4_f20.jpg | Bin 58713 -> 23956 bytes Documentation/images/Pref5_f20.jpg | Bin 20942 -> 16381 bytes Documentation/images/Pref6_f20.jpg | Bin 0 -> 19033 bytes Documentation/images/Preferences1.jpg | Bin 22094 -> 0 bytes Documentation/images/Preferences2.jpg | Bin 19653 -> 0 bytes Documentation/images/Preferences3.jpg | Bin 25880 -> 0 bytes Documentation/images/facebook1_f20.jpg | Bin 0 -> 30069 bytes Documentation/images/facebook2_f20.jpg | Bin 0 -> 42302 bytes Documentation/user-manual.txt | 61 +++-- 12 files changed, 58 insertions(+), 3 deletions(-) create mode 100644 Documentation/images/Pref6_f20.jpg delete mode 100644 Documentation/images/Preferences1.jpg delete mode 100644 Documentation/images/Preferences2.jpg delete mode 100644 Documentation/images/Preferences3.jpg create mode 100644 Documentation/images/facebook1_f20.jpg create mode 100644 Documentation/images/facebook2_f20.jpg diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt index b57e2b9..d0c274e 100644 --- a/Documentation/user-manual.txt +++ b/Documentation/user-manual.txt @@ -2341,10 +2341,8 @@ The panel can be maximised by clicking the icon that minimised the panel. The fi reset and closed by selecting the button with the flag. An example of the _Filter Panel_ is shown in the figure below. - image::images/Filterpanel.jpg["Figure: Filter panel",align="center"] - Four filter criteria may be used to filter the dive list: dive tags, person (buddy / dive master), dive site and dive suit, each of which is represented by a check list with check boxes. Above each check list is a second-level filter tool, allowing the listing of only some of @@ -2364,7 +2362,52 @@ shows those dives that have either one or both of these tags. [[S_ExportLog]] == Exporting the dive log or parts of the dive log -The export function can be reached by selecting _File -> Export_, which brings up +There are two routes for the export of dive information from Subsurface: + +- Export dive information to _Facebook_ + +- xref:S_Export_other[Export dive information to other destinations or formats] + +[[S_facebook]] +=== Exporting dive information to _Facebook_ + +Export of dives to _Facebook_ is handled differently from other types of export. This is because +export to _Facebook_ needs a connection to _Facebook_, requiring a _Facebook_ userID and password. +If, from the Main Menu, one selects _File -> Preferences -> Facebook_, a login screen is presented +(see image *A* to the left, below). Ensure that there is not another active _Facebook_ session +using an Internet browser outside of _Subsurface_. Provide a _Facebook_ userID and password. +Once successful login to _Facebook_ has been achieved, the panel +in image *B*, below is presented. This panel has a button that needs to be selected in order to close the +_Facebook_ connection. + +image::images/facebook1_f20.jpg["Figure: Facebook login",align="center"] + +*Important:* By default the login to _Facebook_ is terminated when _Subsurface_ is closed. However, +the checkbox labelled "Keep me logged in to Subsurface" in image *A*, above allows one to keep the +connection even after _Subsurface_ has been closed. This allows one to launch _Subsurface_ at a later +stage and transfer more dive profiles to _Facebook_ without first having to log into _Facebook_. Keeping the +_Facebook_ connection open has two penalties: a) a security risk for the open connection to be exploited by +unwanted outside parties; b) the Internet bandwith required can be increased when a _Facebook_ connection +is kept open. + +Having established a login to _Facebook_, transfer of a dive profile to one's _Facebook_ timeline is easy. +A _Facebook_ icon appears in the *Dive Notes* panel of _Subsurface_ (See image *A* below). Ensure that the dive +that needs to be transferred to the timeline is depicted in the _Subsurface_ *Dive Profile* panel. Select the +_Faceboo
Re: creating an FAQ
On Mon, Feb 2, 2015 at 8:28 AM, Dirk Hohndel wrote: > Miika, > > excellent, excellent input. > > I have added most of your questions. I rephrased some of them (so all the > questions are actually, you know, questions) and also changed some of the > answers. Please double check what I just posted… > \ > > On Feb 1, 2015, at 9:56 PM, Miika Turkia wrote: > > > > Q: Editing dive sites > > What would you want there as response? > All I know, we get this question a lot. The working way of adding dive-sites manually should be described and we should also describe how this works with the companion app (unless this is answered when talking about the companion app on its own). > > Insufficient privileges to open device > > Again, what would be a good response? I am thinking about the dialout group and udev rules on Linux. miika ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: creating an FAQ
On 2 Feb 2015 08:28, "Dirk Hohndel" wrote: > > Miika, > > excellent, excellent input. > > I have added most of your questions. I rephrased some of them (so all the questions are actually, you know, questions) and also changed some of the answers. Please double check what I just posted… > \ > > On Feb 1, 2015, at 9:56 PM, Miika Turkia wrote: > > > > Q: Editing dive sites > > What would you want there as response? > > > Insufficient privileges to open device > > Again, what would be a good response? > > /D > ___ > subsurface mailing list > subsurface@subsurface-divelog.org > http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface Maybe say what is done with the user input from the survey? For the privacy fanatics out there... :) Benjamin ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: creating an FAQ
Miika, excellent, excellent input. I have added most of your questions. I rephrased some of them (so all the questions are actually, you know, questions) and also changed some of the answers. Please double check what I just posted… \ > On Feb 1, 2015, at 9:56 PM, Miika Turkia wrote: > > Q: Editing dive sites What would you want there as response? > Insufficient privileges to open device Again, what would be a good response? /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: creating an FAQ
On Mon, Feb 2, 2015 at 12:49 AM, Davide DB wrote:
> On Sun, Feb 1, 2015 at 10:45 PM, Dirk Hohndel wrote:
> >
> >
> > Thanks for the ZERO contributions. That really makes me excited to spend
> > my time on Subsurface.
> >
> > In the meantime I put up an initial FAQ on the website. If you have ideas
> > what should be added, or would like to propose a better answer, please
> let
> > me know.
>
Q: Why is Subsurface not able to download my dives?
Clean the contacts! Clean the contacts again! Check with other software
that the download works in general. Try another cable. See our user manual
for pairing with BT and the general use case.
Q: Why Subsurface freezes on import/export?
Depending on the amount of data, converting the log to the desired
output/input might take a looong time. Unfortunately the import currently
seems to freeze the UI for this duration. The export is done on a different
thread and it is most likely running in the back ground with no hint on
when it is complete :(
Q: Why is the CSV import failing
The CSV import has a couple of caveats. You should avoid some special
characters
like ampersand (&), less than (<), greater than (>) and double quotes ("),
the latter if quoting text cells. The
file should use UTF-8 character set, if having non-ASCII characters. Also
the
size of the CSV file might cause problems. Importing 100 dives at a time
(without dive profile) has worked previously, but larger files might exceed
limits of the parser used. When having problems with CSV imports, try first
with
a smaller sample to make sure everything works.
Q: Editing dive sites
Q: Multiuser usage
Store logs of different users to separate log files. From Subsurface, you
can open individual files for different divers and multiple users is
supported quite well.
Loading pictures
We are currently looking for fields named DateTimeOriginal and DateTime
from the Exif header and use those to detect if the image was shot
during the dive or not. If the picture is edited, you should store the
original Exif information on the new/edited image for it to be loaded
properly.
Insufficient privileges to open device
My old log software is not supported for import
If your old log software supports exporting the log book, we might well be
able to import that. However, usually a native support for importing that
format will give more complete information into Subsurface.To implement
support for the log format, we will need a sample log file. It would be
great to have also a screenshot from the original log software or
description of the dive that is shown on the sample log. Preferably we
would like to have a reasonably simple dive to get basic support and
another dive that has as many features enabled as possible (e.g. gas
changes during the dive). This information should be sent to the developer
mailing list subsurface@subsurface-divelog.org (but e.g. user forum can be
used as well). Unfortunately some of the log formats we have not been able
to decipher, so there are no guarantees that this will bring support for
your old log software, but it is worth a try.
My dive computer is not supported
miika
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Import problems with Cobalt 2 on Fedora 21
> On Feb 1, 2015, at 8:33 PM, Linus Torvalds
> wrote:
>
> On Sun, Feb 1, 2015 at 7:36 PM, Matt Thompson wrote:
>>
>> I recently switched to Fedora 21 from Sabayon. I added my user to the
>> dialout group as that is the group for /dev/ttyS*. All of the
>> /dev/ttyS* devices have permissions 660.
>
> The cobalt isn't a serial device, so the usual "dialout" thing won't
> help. You need to make the USB device accessible so that libusb can
> access it.
>
> Generally that means a udev rule.
>
> I don't know what the device ID's for Cobalt are, but for the Suunto
> EON Steel I have something like this:
>
>[torvalds@i7 subsurface]$ cat /lib/udev/rules.d/91-suunto-eonsteel.rules
>SUBSYSTEM=="usb",ATTR{idVendor}=="1493",ATTR{idProduct}=="0030",
> MODE="0666"
>SUBSYSTEM=="usb",ATTR{idVendor}=="1493",ATTR{idProduct}=="0031",
> MODE="0666"
>
> which just makes the dang thing world read-write. It would probably
> be a better idea to make it do GROUP="dialout" and make it only group
> read-write, but I couldn't be bothered.
> […]
> Maybe we should try to gather those kinds of rules in the Linux
> packages? I have no idea how to do udev rule packaging, though, so
> somebody else would have to do it.
We should at least at them to the FAQ.
For the Cobalt case I think what we need to document is
a) the device doesn’t matter, it’s not used (and so its permissions don’t
matter, either)
b) you may need a udev rule on Linux… but what’s that rule?
Try
SUBSYSTEM=="usb",ATTR{idVendor}==“0471",ATTR{idProduct}==“0888", MODE="0666"
Can you confirm that, Matt?
/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Import problems with Cobalt 2 on Fedora 21
On Sun, Feb 1, 2015 at 7:36 PM, Matt Thompson wrote:
>
> I recently switched to Fedora 21 from Sabayon. I added my user to the
> dialout group as that is the group for /dev/ttyS*. All of the
> /dev/ttyS* devices have permissions 660.
The cobalt isn't a serial device, so the usual "dialout" thing won't
help. You need to make the USB device accessible so that libusb can
access it.
Generally that means a udev rule.
I don't know what the device ID's for Cobalt are, but for the Suunto
EON Steel I have something like this:
[torvalds@i7 subsurface]$ cat /lib/udev/rules.d/91-suunto-eonsteel.rules
SUBSYSTEM=="usb",ATTR{idVendor}=="1493",ATTR{idProduct}=="0030", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="1493",ATTR{idProduct}=="0031",
MODE="0666"
which just makes the dang thing world read-write. It would probably
be a better idea to make it do GROUP="dialout" and make it only group
read-write, but I couldn't be bothered.
(The reason for the two different product IDs? The EON Steel actually
goes into a magical "firmware update mode" where it has that 0031
product ID, while the 0030 ID is the normal USB ID for it)
I *think* udevd will just automatically notice new rules, but maybe I
remember incorrectly and you may have to do something like "udevadm
control --reload" after adding the new rule file. No need to reboot
or anything quite that drastic.
Maybe we should try to gather those kinds of rules in the Linux
packages? I have no idea how to do udev rule packaging, though, so
somebody else would have to do it.
Linus
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Import problems with Cobalt 2 on Fedora 21
I know this is probably more of a distro specific question but I'm hoping that someone here has seen this and can point me in the right direction. I recently switched to Fedora 21 from Sabayon. I added my user to the dialout group as that is the group for /dev/ttyS*. All of the /dev/ttyS* devices have permissions 660. I made sure to log out and back in and tried to download dives from my Cobalt2 connected to /dev/ttyS3 and it failed. I checked the log file and it contains only 1 line: ERROR: Failed to open the usb device. [in atomics_cobalt.c:114 (atomics_cobalt_device_open)] If I run Subsurface as root I can successfully download my dives. Also I can successfully download my dives from my Suunto D4i as my normal user. I tried temporarily disabling SELinux with setenforce 0 but that makes no difference. Any ideas? ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
FYI. Email to UDDF specification owners.
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 distribution of this email. I want it to reach the correct person responsible for the maintenance of the UDDF specification and XSD schema files. I have been working with the developers of the Subsurface application on bringing the UDDF export in line with the UDDF 3.2.0 specification. During this process I've come across a number of inconsistencies between the UDDF specification as laid out on the site, and the XSD schema files provided. There have been a number of cases where we have had to make a decision in order to complete the work, however, these patches are fairly new, so we can reverse them. I have detailed the discrepancies below. xsd line 1147: "equipmentused" is part of the "informationafterdive" element. However, in the spec it appears as part of the "informationbeforedive". (see: http://www.streit.cc/extern/uddf_v320/en/sections_profiledata.html) xsd line 1554: rating is not optional (no minOccurs=0) in specifiction it reads as "optional, multiple" (see: http://www.streit.cc/extern/uddf_v320/en/rating.html) xsd line 1571: choice of accomodation or operator & vessel. All are optional in the spec, but the choice isn't marked as "minOccurs=0" in the XSD. This means that one or the other must be provided. That data may not be available. xsd line 989: "tripmembership" is a type "linkType". To meet this requirement it needs to be specified as whereas in the documentation it is give as Dive Trip Red Sea 2006 (note also that this does not meet the IDREF requirements as it contains spaces). (see: www.streit.cc/extern/uddf_v320/en/tripmembership.html) xsd line 596: "link" is not markes as "minOccurs=0". It is not clear from the spec if this should be mandatory. However, examples generally do not include this reference. The reference tends to be from the site to the base only. If I have misunderstood the documentation in some way, please let me know. Otherwise, please let me know if I can do anything or provide any further info. I'd appreciate guidance in which is correct, the xsd or the documentation. Best regards Martin Long (Subsurface project) ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Facebook testing
> On Feb 1, 2015, at 3:43 PM, Davide DB wrote: > > Dirk, > > out of curiosity: FB developers have some tool to see how their apps > are being used? > In other words, could you check how many people publish their dive profiles? I can see how many times the API is called - but I cannot see the data for the current day. And I don’t think it filters out my own use when testing (and I logged in so many times today, it’s not even funny). So yesterday we had 8 people (besides me) using the API. And about 150 calls to the API, 25 of which were errors (no idea what that means, though). /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Facebook testing
Dirk, out of curiosity: FB developers have some tool to see how their apps are being used? In other words, could you check how many people publish their dive profiles? ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: I.possible saving Olold PSCR dives
I changed dive mode to all my pSCR dives. I realized that calculated ceiling changes (increase) when switching to pSCR. I guess the Buhlmann algorithm is fed with the pO2 calculated values. This is a good teaching tool indeed. Good job indeed guys. Thank you for your wondeful work! Bye -- Davide https://vimeo.com/bocio/videos ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Facebook testing
On Sun, Feb 01, 2015 at 04:44:25PM -0600, Matt Thompson wrote: > I just played with this a little bit and it pretty much just worked > for me as far as basic pasting to FB goes. Nice job! Great. > > I just pushed another very ugly commit - I'll clean this up once we agree > > that this is the behavior we want. > > > > With this change Subsurface forgets Facebook credentials once you quit. > > You can still log out manually, but that's almost obsolete now. The > > credentials only stay valid while this Subsurface process is running. > > This quite honestly annoys me. I use ridiculous, unique passwords > that I don't memorize for every different site so having to go grab > the password from LastPass every time I want to post a dive is a large > pain. I understand that some folks don't want to stay logged in > permanently so until things can be made to work following the checkbox > on the FB login page I suppose this is not unreasonable but I look > forward to the day when things are fully functional. I spent an hour trying to figure out how to tell if that checkbox was checked or not. I must have logged in and out 50 times today. There is absolutely no way I can see to tell if the user checked that. It's driving me nuts. Yes, I have some sneaky ideas how to store the connection token in a reasonably safe way without requiring a pin or anything. It's all of course just obfuscation (given that we're an open source project), but I think it would work reasonably well. /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: iPhone companion app
In addition to #2 I've thought of 2 more while working, 3_ give some verification on the ID entered is it wrong or right or what. 4_ Make adding a new view manually in a separate view instead of alertview We can discuss #4 further If it was because something that you had in mind that I didn't see ~Yousef On Mon Feb 02 2015 at 12:12:59 AM Andrey Zhdanov wrote: > Hi Yosef, > > > There's some bugs I wanted to fix but totally forgot I will work on them > tomorrow “hopefully" > > Thanks for your pull request on github! I left some comments there. > > > Last but no least I was wondering If you are interested in more features > in that app than it's current functionality > > > Currently this app is same as Android one. I had ideas about new features > previously, but I don’t have spare time until April-May. > If you know how app can be improved, then feel free to write here and we > will discuss your ideas all together. > > -- > Andrey Zhdanov ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: iPhone companion app
On Sun, Feb 1, 2015 at 11:13 PM, Andrey Zhdanov wrote: > My buddy is a Mac man and recently bought an iPhone after having android for > years. > He told me that the iOS companion app works perfectly. He use it every dive. > > I'm really glad that app is used in a real "field" and works perfectly! > He is an hard core user of this app and he told me that is better than the "original" Android version. I hadn't a chance to see it. I can ask him some feedback on new features -- Davide https://vimeo.com/bocio/videos ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: creating an FAQ
On Sun, Feb 1, 2015 at 10:45 PM, Dirk Hohndel wrote: > > > Thanks for the ZERO contributions. That really makes me excited to spend > my time on Subsurface. > > In the meantime I put up an initial FAQ on the website. If you have ideas > what should be added, or would like to propose a better answer, please let > me know. > Life comes first :) Q1: How much does it cost my passion? (do not let see this feature to your partner) With to the gas consumption stats I discovered I saved 1000 EURO of gas in less of one year (66 dives) with my pSCR. Thanks to Anton and Thanks to Subsurface! Q2: Can I log dives with multiple tanks with the same gas in subsurface? In other words can I use Subsurface for serious cave or tech diving? Description on how to add tanks, mix and gas switches... (Actually I thought I would write a Subsurface survival guide for tech divers) Q3: Logging dives is boring and life is short; how Subsurface could help me? Bye -- Davide https://vimeo.com/bocio/videos ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Facebook testing
I just played with this a little bit and it pretty much just worked for me as far as basic pasting to FB goes. Nice job! On Sat, Jan 31, 2015 at 2:04 PM, Dirk Hohndel wrote: > I just pushed another very ugly commit - I'll clean this up once we agree > that this is the behavior we want. > > With this change Subsurface forgets Facebook credentials once you quit. > You can still log out manually, but that's almost obsolete now. The > credentials only stay valid while this Subsurface process is running. This quite honestly annoys me. I use ridiculous, unique passwords that I don't memorize for every different site so having to go grab the password from LastPass every time I want to post a dive is a large pain. I understand that some folks don't want to stay logged in permanently so until things can be made to work following the checkbox on the FB login page I suppose this is not unreasonable but I look forward to the day when things are fully functional. > > I'll retrigger dailies. > > /D > ___ > 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: iPhone companion app
> My buddy is a Mac man and recently bought an iPhone after having android for > years. > He told me that the iOS companion app works perfectly. He use it every dive. > I'm really glad that app is used in a real “field” and works perfectly! -- Andrey Zhdanov ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: [PATCH] User manual: refine images and text for using iphone
> On 31 Jan 2015, at 12:40, Willem Ferguson > wrote: > On 31/01/2015 11:17, Miika Turkia wrote: >> If the app is recording the path continuously, I suppose this mention is >> slightly misleading. (I do not really know how this thing works, so I added >> this comment as I noticed that only the manual option was available..but now >> I guess that the automatic dive location recording is running at this stage) >> > Who was the tutor/supervisor when Muhammad did this coding last year? Maybe > that person has more information or understands the underlying code? In the > Android app, waypoint storing and GPS streaming are quite different > activities. While the location service is running dives are added automatically based on distance + you can add dive manually while location service is working. -- Andrey Zhdanov ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: iPhone companion app
Hi Yosef, > There's some bugs I wanted to fix but totally forgot I will work on them > tomorrow “hopefully" Thanks for your pull request on github! I left some comments there. > Last but no least I was wondering If you are interested in more features in > that app than it's current functionality Currently this app is same as Android one. I had ideas about new features previously, but I don’t have spare time until April-May. If you know how app can be improved, then feel free to write here and we will discuss your ideas all together. -- Andrey Zhdanov ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
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, but very interactive, and not close to being usable for a printed log, nor does it have any customisable options over and above the few checkboxes for what to include. ie - while it is a great feature, and very well done, it doesn't come close to solving the 'printed logbook' problem. HOWEVER, what it does is provide the bare building blocks - eg profile rendered as an image/canvas. It does perhaps make it an easier option to do a XSLT transform on this data. Perhaps an option to do a more 'basic' export, as it looks as thought the current export is not a simple webpage but built up with javascript, and so it wouldn't be possible to transform it. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: creating an FAQ
> On Jan 30, 2015, at 10:03 AM, Dirk Hohndel wrote: > > We need a user focused FAQ. In addition to the manual. > > Questions like "I added a dive on the companion app but don't see it in > Subsurface". I'll add this to the website but need help collecting some of > the questions. > > If you have a question you think should be added, please send as reply to > this email. Don't worry about phrasing, don't worry if you don't know the > full answer. It's easy to clean this up. It's quite hard to collect the > questions (I kinda know how all this works - it's the people who aren't as > deeply inside of the code that have the questions...) > > So this is a great opportunity for the 150 or so non-developers on this > list to contribute! Thanks for the ZERO contributions. That really makes me excited to spend my time on Subsurface. In the meantime I put up an initial FAQ on the website. If you have ideas what should be added, or would like to propose a better answer, please let me know. /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: GSoC 2015
> On Feb 1, 2015, at 1:31 PM, Long, Martin wrote: > > 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, detailed account, of some of my dives. This > doesn't come out well in printouts. In all layouts it seems to overlay > the profile. I'd really like to be able to change the layout to > display logs in a better way, that works for me. Yes - that has been an often requested feature. The problem is that it appears to be really really hard to do. I’ll be happy to add it as a GSoC idea but I wonder if this is something a student will be successful with. > OR provide an export that can easily be used by something like Jasper, > or easily translated into a web page (it currently very difficult to > do the profile in HTML from the raw data). 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… Thanks /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: GSoC 2015
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, detailed account, of some of my dives. This doesn't come out well in printouts. In all layouts it seems to overlay the profile. I'd really like to be able to change the layout to display logs in a better way, that works for me. OR provide an export that can easily be used by something like Jasper, or easily translated into a web page (it currently very difficult to do the profile in HTML from the raw data). (both of my ideas are something that I'd hoped to get my teeth into, but work and family commitments are taking their toll at the moment). ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: GSoC 2015
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" set: - Single 15l cylinder - Apeks DS4 + XTX40 - 5kg - O'Niel 3:2 suit - Mares full foot fins - Buddy Pioneer BCD - Suunto Viper Air "UK water" - Twin 7l cylinders - Apex DS4 + XTX40 - 12kg - NDiver Vortex drysuit - Jet fins - Buddy Pioneer BCD - Suunto Viper Air Individual items could then be changed on a per-dive basis, but it would allow quick entry of these details, as well as normalising more data about the dive. On 1 February 2015 at 20:26, Robert C. Helling wrote: > > On 01 Feb 2015, at 21:14, Dirk Hohndel wrote: > > If you have ideas we should propose for students, please post. > > > I would love to see better support for images beyond local files. I would > like to have pictures from he net (cloud, web pages, flickr, you name it). > And associating those to dives should be easier. Also the clock sync it > terrible from a user perspective (no feedback what gets matched to what). > > The other big thing is of course a UI for git load/save. > > These are just the things that are in the back of my head of „what needs to > be done“. > > Best > Robert > > ___ > 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: [PATCH] Update spanish translation of user manual to english 47c5a28f
Thanks Dirk. I'll take a look on your fixes when pushed, as this patch gave no problem to me while trying on master. There's still another patch, but it won't be completed until tomorrow evening (Spain time). Regards. Salva. 2015-02-01 18:11 GMT+01:00 Dirk Hohndel : > Thanks... > There were a couple of issues with incorrect IDs in the Spanish > translation that I fixed. > > /D > ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
[PATCH] Fix Ubuntu glitch with completer popup
On Ubuntu, the completer often prevents applying/discarding the changes
on the dive info pane and disrupts editing of other fields as well. This
patch prevents the completer popup from appearing when not in edit mode
(apply or discard is pressed) or when the string is still empty.
Fixes #818
Signed-off-by: Miika Turkia
---
qt-ui/tagwidget.cpp | 8
1 file changed, 8 insertions(+)
diff --git a/qt-ui/tagwidget.cpp b/qt-ui/tagwidget.cpp
index bfe5354..8365a2e 100644
--- a/qt-ui/tagwidget.cpp
+++ b/qt-ui/tagwidget.cpp
@@ -85,6 +85,14 @@ void TagWidget::reparse()
if (pos.first >= 0 && pos.second > 0)
currentText = text().mid(pos.first, pos.second -
pos.first).trimmed();
+ /*
+* Do not show the completer when not in edit mode - basically
+* this returns when we are accepting or discarding the changes.
+*/
+ if (MainWindow::instance()->information()->isEditing() == false ||
currentText.length() == 0) {
+ return;
+ }
+
if (m_completer) {
m_completer->setCompletionPrefix(currentText);
if (m_completer->completionCount() == 1) {
--
1.9.1
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: GSoC 2015
> On 01 Feb 2015, at 21:14, Dirk Hohndel wrote: > > If you have ideas we should propose for students, please post. I would love to see better support for images beyond local files. I would like to have pictures from he net (cloud, web pages, flickr, you name it). And associating those to dives should be easier. Also the clock sync it terrible from a user perspective (no feedback what gets matched to what). The other big thing is of course a UI for git load/save. These are just the things that are in the back of my head of „what needs to be done“. Best Robert signature.asc Description: Message signed with OpenPGP using GPGMail ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
GSoC 2015
I'd like to participate again. I think we got some really great result last time and gained a few new developers, too! If you have ideas we should propose for students, please post. /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: User Manual: Facebook tests
> On Feb 1, 2015, at 11:08 AM, Willem Ferguson > wrote: > > The Facebook-related panels all have the standard OK/Apply/Discard buttons > near the bottom right. > Discard = cancel = close without saving > Apply = assign the values to the completed fields > OK = Close panel without saving > What are the semantic differences among the three options? These are the buttons for the preferences. They have NO EFFECT AT ALL when it comes to the FB login. This may be a bug, but that’s how it is right now. /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
[PATCH] Do not go to edit mode if nothing changed
Fixes #804
Signed-off-by: Miika Turkia
---
qt-ui/maintab.cpp | 15 +++
1 file changed, 15 insertions(+)
diff --git a/qt-ui/maintab.cpp b/qt-ui/maintab.cpp
index 7335711..00aae5f 100644
--- a/qt-ui/maintab.cpp
+++ b/qt-ui/maintab.cpp
@@ -980,6 +980,10 @@ void MainTab::on_buddy_textChanged()
{
if (editMode == IGNORE || acceptingEdit == true)
return;
+
+ if (same_string(displayed_dive.buddy,
ui.buddy->toPlainText().toUtf8().data()))
+ return;
+
QStringList text_list = ui.buddy->toPlainText().split(",",
QString::SkipEmptyParts);
for (int i = 0; i < text_list.size(); i++)
text_list[i] = text_list[i].trimmed();
@@ -993,6 +997,10 @@ void MainTab::on_divemaster_textChanged()
{
if (editMode == IGNORE || acceptingEdit == true)
return;
+
+ if (same_string(displayed_dive.divemaster,
ui.divemaster->toPlainText().toUtf8().data()))
+ return;
+
QStringList text_list = ui.divemaster->toPlainText().split(",",
QString::SkipEmptyParts);
for (int i = 0; i < text_list.size(); i++)
text_list[i] = text_list[i].trimmed();
@@ -1102,8 +1110,15 @@ void MainTab::saveTags()
void MainTab::on_tagWidget_textChanged()
{
+ char buf[1024];
+
if (editMode == IGNORE || acceptingEdit == true)
return;
+
+ taglist_get_tagstring(displayed_dive.tag_list, buf, 1024);
+ if (same_string(buf, ui.tagWidget->toPlainText().toUtf8().data()))
+ return;
+
markChangedWidget(ui.tagWidget);
}
--
1.9.1
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
User Manual: Facebook tests
The Facebook-related panels all have the standard OK/Apply/Discard buttons near the bottom right. Discard = cancel = close without saving Apply = assign the values to the completed fields OK = Close panel without saving What are the semantic differences among the three options? Kind regards, willem ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: [PATCH] Update spanish translation of user manual to english 47c5a28f
Thanks... There were a couple of issues with incorrect IDs in the Spanish translation that I fixed. /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Beta 3 and what's missing for 4.4
On Sun, Feb 01, 2015 at 07:16:39AM -0800, Dirk Hohndel wrote: > I will release Beta 3 today. Binaries are up for Windows and Mac and being built for the Linux flavors. Users checking for updates from within Subsurface will be informed that the new beta is up, but I haven't announced it, yet. It would be nice if a few people could test this. I gave the Mac beta a bit of a workout, that one seems OK. I haven't looked at the Windows one, yet. And I haven't had a chance to play with any of the Linux packages, either. I'll be busy with real life for the next hour or two, after that I'm hoping to announce the beta. /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Beta 3 and what's missing for 4.4
I will release Beta 3 today. My expectation is that this is functionally very similar to what I'll release as 4.4 hopefully in just a few days. Willem, could you add a quick chapter about Facebook support? I think that's the only new thing compared to Beta 2 (plus of course lots of bug fixes and minor improvements). That change to the user manual and any further translation work is all that I think is left to do. If the people working on the French, Spanish, and Russian translations of the manual could give me an idea if they could have their updates to me by, say, next Wednesday, that would be very helpful. Also, I sent out an email a few days ago but no one responded. I really think we need an FAQ on the website. Please send any questions (or questions and answers) that you think a new user might have and that we should point out there... Thanks everyone! /D PS: to the non-US-Americans... most of the people over here will be distracted today by the lower-48-states championship game in American carry egg (that title apparently was too long so it's usually just called "Superball" - even though no balls are involved). I'm planning to do the beta today, anyway, as most of our users / testers are outside the US :-) ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
[PATCH] Fix crash if one selects incorrectly Seabear CSV
Signed-off-by: Miika Turkia
---
file.c| 7 +++
qt-ui/divelogimportdialog.cpp | 5 +++--
2 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/file.c b/file.c
index eacd875..e03edaf 100644
--- a/file.c
+++ b/file.c
@@ -932,6 +932,13 @@ int parse_seabear_csv_file(const char *filename, int
timef, int depthf, int temp
NL = "\r\n";
}
+ /*
+* If file does not contain empty lines, it is not a valid
+* Seabear CSV file.
+*/
+ if (!ptr)
+ return -1;
+
if (!ptr_old) {
while ((ptr = strstr(ptr, "\n\n")) != NULL) {
ptr_old = ptr;
diff --git a/qt-ui/divelogimportdialog.cpp b/qt-ui/divelogimportdialog.cpp
index c79b9df..ca3a2be 100644
--- a/qt-ui/divelogimportdialog.cpp
+++ b/qt-ui/divelogimportdialog.cpp
@@ -526,7 +526,7 @@ void DiveLogImportDialog::on_buttonBox_accepted()
if (ui->knownImports->currentText() != "Manual import") {
for (int i = 0; i < fileNames.size(); ++i) {
if (ui->knownImports->currentText() == "Seabear CSV") {
-
parse_seabear_csv_file(fileNames[i].toUtf8().data(),
+ if
(parse_seabear_csv_file(fileNames[i].toUtf8().data(),
r.indexOf(tr("Sample
time")),
r.indexOf(tr("Sample
depth")),
r.indexOf(tr("Sample
temperature")),
@@ -539,7 +539,8 @@ void DiveLogImportDialog::on_buttonBox_accepted()
ui->CSVSeparator->currentIndex(),
specialCSV.contains(ui->knownImports->currentIndex()) ?
CSVApps[ui->knownImports->currentIndex()].name.toUtf8().data() : "csv",
ui->CSVUnits->currentIndex()
- );
+ ) < 0)
+ return;
// Seabear CSV stores NDL and TTS in Minutes,
not seconds
struct dive *dive =
dive_table.dives[dive_table.nr - 1];
--
1.9.1
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Compilation error with latest master
On Fri, 30 Jan 2015, Cristian Ionescu-Idbohrn wrote: > On Fri, 30 Jan 2015, Dirk Hohndel wrote: > > On Fri, Jan 30, 2015 at 06:21:45PM +, Pedro Neves wrote: > > > Hi all: > > > > > > I'm trying to compile the latest subsurface master on my system > > > (Debian/Sid) and I'm getting the following error. > > > I've just recently installed my OS on this PC and I'm not sure > > > if I'm missing any package: > > > > > > > > > compiling qt-ui/completionmodels.cpp > > > In file included from /usr/include/libxml2/libxml/parser.h:810:0, > > > from /usr/include/libxml2/libxml/globals.h:18, > > > from /usr/include/libxml2/libxml/threads.h:35, > > > from /usr/include/libxml2/libxml/xmlmemory.h:218, > > > from /usr/include/libxml2/libxml/tree.h:1306, > > > from dive.h:37, > > > from qt-gui.cpp:12: > > > /usr/include/libxml2/libxml/encoding.h:31:26: fatal error: unicode/ucnv.h: > > > No such file or directory > > > #include > > > > $ dpkg -S /usr/include/x86_64-linux-gnu/unicode/ucnv.h > > libicu-dev:amd64: /usr/include/x86_64-linux-gnu/unicode/ucnv.h > > > > I didn't install this explicitly, so this is implicitly pulled in > > by one of the dependencies of the packages that I DO explicitly > > require for a build on Debian / Ubuntu... > > And that may very well be a package dependency problem, as AFAICT: > > Package: libxml2-dev > Depends: libxml2 > > only. See bug: https://bugs.debian.org/776694 now resolved in version 2.9.2+dfsg1-3. Cheers, -- Cristian ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
