Re: Subsurface-mobile status update

2016-08-14 Thread Dirk Hohndel 
On Sun, Aug 14, 2016 at 09:38:27PM +0200, Thomas Pfeiffer wrote:
> On 14.08.2016 06:29, Dirk Hohndel wrote:
> > I still haven't managed to make the latest Kirigami work. And I don't think 
> > I'll finish that today as I'm jet lagged and about to fall asleep on my 
> > keyboard. But at least our iOS testers should be able to continue to use 
> > Subsurface-mobile.
> > 
> Btw: Kirigami 1.0 has been released four days ago [1] and you can find the
> download link to the release tarball in our wiki [2]. We currently consider
> Kirigami on iOS "experimental" both because we don't have any iOS developers
> and because you guys are still having trouble with it on iOS.
> That said, of course we hope to get to a point where we can make the iOS
> support official, so we hope we can fix these problems together.
> Marco is currently unavailable, but will return sometime next week and will
> hopefully find time to look into this.
> The Kirigami release seems to have sparked quite some interest, so maybe
> some of the people who have offered to help us have experience with iOS
> development.

That would be nice.

Kirigami as is has a few oddities. It compiles neither with cmake nor with
qmake. Hmm.

I have patches for that, but on iOS it still dies at startup with a
BAD_ACCESS to address 0x1 when trying to loop over the
m_stylesFallbackChain in KirigamiPlugin::componentPath (we are building
static).

I have pushed what I have to Subsurface master if someone else wants to
play with this.

/D


>From 816e243f664f43d3d03601372492ff74710cf195 Mon Sep 17 00:00:00 2001
From: Dirk Hohndel 
Date: Sun, 14 Aug 2016 15:45:25 -0700
Subject: [PATCH 1/3] fix qmake .pro file

Signed-off-by: Dirk Hohndel 
---
 kirigami.pro | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/kirigami.pro b/kirigami.pro
index 6181287..f7d6fe6 100644
--- a/kirigami.pro
+++ b/kirigami.pro
@@ -2,8 +2,8 @@ TEMPLATE = lib
 CONFIG += plugin
 
 QT  += qml quick gui svg
-HEADERS += $$PWD/src/kirigamiplugin.h
-SOURCES += $$PWD/src/kirigamiplugin.cpp
+HEADERS += $$PWD/src/kirigamiplugin.h $$PWD/src/enums.h
+SOURCES += $$PWD/src/kirigamiplugin.cpp $$PWD/src/enums.cpp
 
 API_VER=1.0
 
-- 
2.7.4 (Apple Git-66)

>From ac40a529216ce3bee6f3f9d82a8fab190d72bc8f Mon Sep 17 00:00:00 2001
From: Dirk Hohndel 
Date: Sun, 14 Aug 2016 16:29:42 -0700
Subject: [PATCH 2/3] Remove reference to non-existant file

Signed-off-by: Dirk Hohndel 
---
 kirigami.qrc | 1 -
 1 file changed, 1 deletion(-)

diff --git a/kirigami.qrc b/kirigami.qrc
index 994c104..63d64ac 100644
--- a/kirigami.qrc
+++ b/kirigami.qrc
@@ -42,7 +42,6 @@
 src/styles/Plasma/Theme.qml
 src/styles/Plasma/Units.qml
 src/styles/Plasma/Icon.qml
-src/styles/Desktop/ContextDrawer.qml
 src/styles/Desktop/Theme.qml
 src/styles/Desktop/OverlayDrawer.qml
 src/styles/Desktop/Units.qml
-- 
2.7.4 (Apple Git-66)

>From c09a57b35dff4e024147527e7ec8e0a4cd4c45c2 Mon Sep 17 00:00:00 2001
From: Dirk Hohndel 
Date: Sun, 14 Aug 2016 16:31:46 -0700
Subject: [PATCH 3/3] Hide non-existant cmake macro

Signed-off-by: Dirk Hohndel 
---
 src/CMakeLists.txt | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt
index 1866e4e..ace207d 100644
--- a/src/CMakeLists.txt
+++ b/src/CMakeLists.txt
@@ -1,6 +1,8 @@
 project(kirigami)
 
-ecm_create_qm_loader(kirigami_QM_LOADER libkirigamiplugin_qt)
+if (! STATIC_LIBRARY)
+ecm_create_qm_loader(kirigami_QM_LOADER libkirigamiplugin_qt)
+endif()
 
 set(kirigami_SRCS
 kirigamiplugin.cpp
-- 
2.7.4 (Apple Git-66)

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

Re: Subsurface-mobile status update

2016-08-14 Thread Thomas Pfeiffer 

On 14.08.2016 06:29, Dirk Hohndel wrote:

I still haven't managed to make the latest Kirigami work. And I don't think 
I'll finish that today as I'm jet lagged and about to fall asleep on my 
keyboard. But at least our iOS testers should be able to continue to use 
Subsurface-mobile.

Btw: Kirigami 1.0 has been released four days ago [1] and you can find the 
download link to the release tarball in our wiki [2]. We currently consider 
Kirigami on iOS "experimental" both because we don't have any iOS developers and 
because you guys are still having trouble with it on iOS.
That said, of course we hope to get to a point where we can make the iOS support 
official, so we hope we can fix these problems together.
Marco is currently unavailable, but will return sometime next week and will 
hopefully find time to look into this.
The Kirigami release seems to have sparked quite some interest, so maybe some of 
the people who have offered to help us have experience with iOS development.


Cheers,
Thomas

[1] 
https://dot.kde.org/2016/08/10/kdes-kirigami-ui-framework-gets-its-first-public-release

[2] https://techbase.kde.org/Kirigami
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

[PATCH] Fill in divecomputer serial number and firmware version on loading

2016-08-14 Thread Linus Torvalds 

From: Linus Torvalds 
Date: Mon, 20 Jun 2016 21:07:36 -0700
Subject: [PATCH] Fill in divecomputer serial number and firmware version on 
loading

We have the serial number and firmware version fields in "struct
divecomputer", but we don't actually fill them in when loading the data
from git or xml, because we save all that information in the separate
device table instead.

But in order to always have the serial number associated with a device,
let's make sure to fill those fields in.  It won't hurt, and this way we
have the information available whether we just loaded the dive from a
file, or imported it from the dive computer.  One less semantic
difference to worry about.

Signed-off-by: Linus Torvalds 
---

I've had this patch in my tree for a while - it doesn't actually matter 
the way things are now, but it fixes an internal inconsistency that 
confused me some time ago.

Apply or not, I'm just sending this because I just sent a _real_ patch to 
fix an actual real bug, and I had this hanging around.

 core/device.c| 28 
 core/device.h|  1 +
 core/load-git.c  |  2 +-
 core/parse-xml.c |  6 +-
 4 files changed, 35 insertions(+), 2 deletions(-)

diff --git a/core/device.c b/core/device.c
index 6c4452f7813b..afd52b8ef19b 100644
--- a/core/device.c
+++ b/core/device.c
@@ -182,3 +182,31 @@ struct divecomputer *fake_dc(struct divecomputer *dc, bool 
alloc)
/* Even that didn't work? Give up, there's something wrong */
return 
 }
+
+static void match_id(void *_dc, const char *model, uint32_t deviceid,
+const char *nickname, const char *serial, const char 
*firmware)
+{
+   struct divecomputer *dc = _dc;
+
+   if (dc->deviceid != deviceid)
+   return;
+   if (strcmp(dc->model, model))
+   return;
+
+   if (serial && !dc->serial)
+   dc->serial = strdup(serial);
+   if (firmware && !dc->fw_version)
+   dc->fw_version = strdup(firmware);
+}
+
+/*
+ * When setting the device ID, we also fill in the
+ * serial number and firmware version data
+ */
+void set_dc_deviceid(struct divecomputer *dc, unsigned int deviceid)
+{
+   if (deviceid) {
+   dc->deviceid = deviceid;
+   call_for_each_dc(dc, match_id, false);
+   }
+}
diff --git a/core/device.h b/core/device.h
index 8a00b96d31cb..264ea8db5dfc 100644
--- a/core/device.h
+++ b/core/device.h
@@ -7,6 +7,7 @@ extern "C" {
 #endif
 
 extern struct divecomputer *fake_dc(struct divecomputer *dc, bool alloc);
+extern void set_dc_deviceid(struct divecomputer *dc, unsigned int deviceid);
 extern void create_device_node(const char *model, uint32_t deviceid, const 
char *serial, const char *firmware, const char *nickname);
 extern void call_for_each_dc(void *f, void (*callback)(void *, const char *, 
uint32_t,
   const char *, const char 
*, const char *), bool select_only);
diff --git a/core/load-git.c b/core/load-git.c
index 0fe2c6353a87..670658d1b50b 100644
--- a/core/load-git.c
+++ b/core/load-git.c
@@ -643,7 +643,7 @@ static void parse_dc_date(char *line, struct membuffer 
*str, void *_dc)
 { (void) str; struct divecomputer *dc = _dc; update_date(>when, line); }
 
 static void parse_dc_deviceid(char *line, struct membuffer *str, void *_dc)
-{ (void) str; struct divecomputer *dc = _dc; dc->deviceid = get_hex(line); }
+{ (void) str; struct divecomputer *dc = _dc; set_dc_deviceid(dc, 
get_hex(line)); }
 
 static void parse_dc_diveid(char *line, struct membuffer *str, void *_dc)
 { (void) str; struct divecomputer *dc = _dc; dc->diveid = get_hex(line); }
diff --git a/core/parse-xml.c b/core/parse-xml.c
index 3b5a2d79476e..052cb124c36b 100644
--- a/core/parse-xml.c
+++ b/core/parse-xml.c
@@ -892,6 +892,8 @@ static int match_dc_data_fields(struct divecomputer *dc, 
const char *name, char
 /* We're in the top-level dive xml. Try to convert whatever value to a dive 
value */
 static void try_to_fill_dc(struct divecomputer *dc, const char *name, char 
*buf)
 {
+   unsigned int deviceid;
+
start_match("divecomputer", name, buf);
 
if (MATCH("date", divedate, >when))
@@ -900,8 +902,10 @@ static void try_to_fill_dc(struct divecomputer *dc, const 
char *name, char *buf)
return;
if (MATCH("model", utf8_string, >model))
return;
-   if (MATCH("deviceid", hex_value, >deviceid))
+   if (MATCH("deviceid", hex_value, )) {
+   set_dc_deviceid(dc, deviceid);
return;
+   }
if (MATCH("diveid", hex_value, >diveid))
return;
if (MATCH("dctype", get_dc_type, >divemode))
-- 
2.9.2.729.ga42d7b6

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

[PATCH] Fix cloud storage authentication attempt counting

2016-08-14 Thread Linus Torvalds 

From: Linus Torvalds 
Date: Sun, 14 Aug 2016 09:39:40 -0700
Subject: [PATCH] Fix cloud storage authentication attempt counting

The authentication count was a static counter in the authentication
callback, which gets incremented until we consider the authentication to
have failed.

The problem with that is that it doesn't get incremented for just _one_
authentication operation, it gets incremented each time you try to load
or save, so eventually the code considers authentication to have failed
even if nothing ever went wrong.

This fixes it by making it static to the whole git-access file, and have
each operation clear it before starting a new remote access.

Signed-off-by: Linus Torvalds 
---

So I mainly use the subsurface cloud storage while traveling, and then the 
network tends to be so bad that I've dismissed the cloud storage failures 
as "real". But people continue to complain, and I just tested at home, and 
if you do multiple "Save to cloud storage", it *will* fail after a couple 
of attempts without this patch.

There may be other things triggering problems too, but this was at least 
one obvious bug in the code.

 core/git-access.c | 14 --
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/core/git-access.c b/core/git-access.c
index 6fe90b0a97fb..458a7dd9a2f3 100644
--- a/core/git-access.c
+++ b/core/git-access.c
@@ -185,6 +185,8 @@ static int reset_to_remote(git_repository *repo, 
git_reference *local, const git
return 0;
 }
 
+static int auth_attempt = 0;
+
 int credential_ssh_cb(git_cred **out,
  const char *url,
  const char *username_from_url,
@@ -194,7 +196,6 @@ int credential_ssh_cb(git_cred **out,
(void) url;
(void) allowed_types;
(void) payload;
-   static int attempt = 0;
 
const char *priv_key = format_string("%s/%s", 
system_default_directory(), "ssrf_remote.key");
const char *passphrase = prefs.cloud_storage_password ? 
strdup(prefs.cloud_storage_password) : strdup("");
@@ -202,9 +203,8 @@ int credential_ssh_cb(git_cred **out,
/* Bail out from libgit authentication loop when credentials are
 * incorrect */
 
-   if (attempt++ > 2) {
+   if (auth_attempt++ > 2) {
report_error("Authentication to cloud storage failed.");
-   attempt = 0;
return GIT_EUSER;
}
 
@@ -221,16 +221,14 @@ int credential_https_cb(git_cred **out,
(void) username_from_url;
(void) payload;
(void) allowed_types;
-   static int attempt = 0;
const char *username = prefs.cloud_storage_email_encoded;
const char *password = prefs.cloud_storage_password ? 
strdup(prefs.cloud_storage_password) : strdup("");
 
/* Bail out from libgit authentication loop when credentials are
 * incorrect */
 
-   if (attempt++ > 2) {
+   if (auth_attempt++ > 2) {
report_error("Authentication to cloud storage failed.");
-   attempt = 0;
return GIT_EUSER;
}
return git_cred_userpass_plaintext_new(out, username, password);
@@ -273,6 +271,7 @@ static int update_remote(git_repository *repo, git_remote 
*origin, git_reference
refspec.count = 1;
refspec.strings = (char **)
 
+   auth_attempt = 0;
opts.callbacks.push_transfer_progress = _transfer_progress_cb;
if (rt == RT_SSH)
opts.callbacks.credentials = credential_ssh_cb;
@@ -529,6 +528,7 @@ static int check_remote_status(git_repository *repo, 
git_remote *origin, const c
git_reference_list(, repo);
git_push_options opts = GIT_PUSH_OPTIONS_INIT;
opts.callbacks.transfer_progress = _progress_cb;
+   auth_attempt = 0;
if (rt == RT_SSH)
opts.callbacks.credentials = credential_ssh_cb;
else if (rt == RT_HTTPS)
@@ -592,6 +592,7 @@ int sync_with_remote(git_repository *repo, const char 
*remote, const char *branc
fprintf(stderr, "git storage: fetch remote\n");
git_fetch_options opts = GIT_FETCH_OPTIONS_INIT;
opts.callbacks.transfer_progress = _progress_cb;
+   auth_attempt = 0;
if (rt == RT_SSH)
opts.callbacks.credentials = credential_ssh_cb;
else if (rt == RT_HTTPS)
@@ -710,6 +711,7 @@ static git_repository *create_local_repo(const char 
*localdir, const char *remot
if (verbose)
fprintf(stderr, "git storage: create_local_repo\n");
 
+   auth_attempt = 0;
opts.fetch_opts.callbacks.transfer_progress = _progress_cb;
if (rt == RT_SSH)
opts.fetch_opts.callbacks.credentials = credential_ssh_cb;
-- 
2.9.2.729.ga42d7b6

___
subsurface mailing list
subsurface@subsurface-divelog.org

Re: Frequent cloud storage authentication errors with Subsurface 4.5.6 (desktop)

2016-08-14 Thread Martin de Weger 
That was helpful, thanks.

I’m seeing one error in the log: qt.network.ssl: QSslSocket: cannot call 
unresolved function SSL_get0_next_proto_negotiated

I did enclose all the output in the enclosed file.

Martin


> Op 14 aug. 2016, om 17:50 heeft Dirk Hohndel  het volgende 
> geschreven:
> 
> On Sun, Aug 14, 2016 at 05:18:08PM +0200, Martin de Weger wrote:
>> I haven’t build the app, I installed the app from the dmg file provided on 
>> the subsurface website. My software programming skills are close to 
>> non-existent, I can do testing and I’m a happy user of the software. 
> 
> You can still use the same trick :-)
> 
> Open a terminal (Terminal.app)
> /Applications/Subsurface.app/Contents/MacOS/Subsurface -v
> 
> /D
can't find Qt localization for locale "nl" searching in 
"/Applications/Subsurface.app/Contents/translations"
cloud URL set as 
"https://cloud.subsurface-divelog.org//git/martin@duikschool.amsterdam[martin@duikschool.amsterdam];
git storage: update local repo
sync with remote 
https://cloud.subsurface-divelog.org//git/martin@duikschool.amsterdam[martin@duikschool.amsterdam]
delete proxy setting
Cloud storage: checking connection to cloud server
qt.network.ssl: QSslSocket: cannot resolve SSL_set_psk_client_callback
qt.network.ssl: QSslSocket: cannot resolve TLSv1_1_client_method
qt.network.ssl: QSslSocket: cannot resolve TLSv1_2_client_method
qt.network.ssl: QSslSocket: cannot resolve TLSv1_1_server_method
qt.network.ssl: QSslSocket: cannot resolve TLSv1_2_server_method
qt.network.ssl: QSslSocket: cannot resolve SSL_select_next_proto
qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_set_next_proto_select_cb
qt.network.ssl: QSslSocket: cannot resolve SSL_get0_next_proto_negotiated
qt.network.ssl: QSslSocket: cannot call unresolved function 
SSL_get0_next_proto_negotiated
qt.network.ssl: QSslSocket: cannot call unresolved function 
SSL_get0_next_proto_negotiated
git storage: fetch remote
git storage: check remote status
git storage: try to update
Set the current dive site: 2241907379
cloud URL set as 
"https://cloud.subsurface-divelog.org//git/martin@duikschool.amsterdam[martin@duikschool.amsterdam];
cloud URL set as 
"https://cloud.subsurface-divelog.org//git/martin@duikschool.amsterdam[martin@duikschool.amsterdam];
Completed connection with cloud storage backend, response "[OK]"
git storage: update local repo
sync with remote 
https://cloud.subsurface-divelog.org//git/martin@duikschool.amsterdam[martin@duikschool.amsterdam]
delete proxy setting
Cloud storage: checking connection to cloud server
qt.network.ssl: QSslSocket: cannot call unresolved function 
SSL_get0_next_proto_negotiated
qt.network.ssl: QSslSocket: cannot call unresolved function 
SSL_get0_next_proto_negotiated
Completed connection with cloud storage backend, response "[OK]"
git storage: fetch remote
git storage: check remote status
git storage: try to update
git storage: do git save
existing filename 
https://cloud.subsurface-divelog.org//git/martin@duikschool.amsterdam[martin@duikschool.amsterdam]
sync with remote 
https://cloud.subsurface-divelog.org//git/martin@duikschool.amsterdam[martin@duikschool.amsterdam]
delete proxy setting
Cloud storage: checking connection to cloud server
Completed connection with cloud storage backend, response "[OK]"
qt.network.ssl: QSslSocket: cannot call unresolved function 
SSL_get0_next_proto_negotiated
git storage: fetch remote
git storage: check remote status
git storage: try to update
git storage: update remote___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Subsurface-mobile status update

2016-08-14 Thread Dirk Hohndel 
On Sun, Aug 14, 2016 at 05:56:14PM +0200, Robert Helling wrote:
> Dirk,
> 
> > Am 14.08.2016 um 17:52 schrieb Dirk Hohndel :
> > 
> >> At which stage did you fail? I have to change one item in Info.plist.in
> >> to say I am me and not you, though. Is there anything I should try
> >> first?
> > 
> > When I ran the .ipa on device, it fails to create a RootObject (I posted
> > about this several weeks ago)
> 
> 
> I have never met anything called .ipa. I deploy by pressing the „play“ button 
> in Creator.

Ah, so you're not (yet) creating archives that can be deployed to devices.
I need to check if everything that you need to do that is in tree or if
there are pieces that I still need to check in.

I'll look into that, soon.

First I'll try to get the latest Kirigami figured out.

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

Re: Subsurface-mobile status update

2016-08-14 Thread Robert Helling 
Dirk,

> Am 14.08.2016 um 17:52 schrieb Dirk Hohndel :
> 
>> At which stage did you fail? I have to change one item in Info.plist.in
>> to say I am me and not you, though. Is there anything I should try
>> first?
> 
> When I ran the .ipa on device, it fails to create a RootObject (I posted
> about this several weeks ago)


I have never met anything called .ipa. I deploy by pressing the „play“ button 
in Creator.

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

Re: Subsurface-mobile status update

2016-08-14 Thread Dirk Hohndel 
On Sun, Aug 14, 2016 at 05:42:02PM +0200, Robert Helling wrote:
> Hi Dirk,
> 
> > Am 14.08.2016 um 17:17 schrieb Dirk Hohndel :
> > 
> > OK, that's good. Thanks, Robert.
> > 
> > Now the question is "do you want to pay the extortion fee to Apple to
> > become a developer?" if yes, I think I should be able to somehow add you
> > to the Subsurface team and hopefully we can both create working signed
> > binaries…
> 
> I have already paid the fee (not realizing you don’t need it if you only
> want to deploy to your own device). My appleID is hell...@atdotde.de

Now I need to figure out how to add you to the team and how all that
works. But having a second person who can create these builds would be so
totally worth it!

> > What I find interesting, though, is that for me on my new laptop I wasn't
> > able to create working binaries. The fact that you were able to do so
> > means that maybe I should just blow away the whole development tree there
> > and start from scratch and maybe things will work.
> > 
> > Which version of Qt are you working with?
> 
> I am still on Qt 5.5 (which also means that may of the QWebEngine things
> are not there, yet. But that’s another story. I had 5.6 installed at
> some point but for some reason I cannot remember moved it away). I
> should probably soon go to 5.7.

So 5.7 is completely broken for me when trying to build for iOS. I filed a
bug that was closed (without fixing the problem), I re-opened it but I
haven't seen activity on it. So I'd recommend 5.6

> At which stage did you fail? I have to change one item in Info.plist.in
> to say I am me and not you, though. Is there anything I should try
> first?

When I ran the .ipa on device, it fails to create a RootObject (I posted
about this several weeks ago)

/D


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

Re: Frequent cloud storage authentication errors with Subsurface 4.5.6 (desktop)

2016-08-14 Thread Dirk Hohndel 
On Sun, Aug 14, 2016 at 05:18:08PM +0200, Martin de Weger wrote:
> I haven’t build the app, I installed the app from the dmg file provided on 
> the subsurface website. My software programming skills are close to 
> non-existent, I can do testing and I’m a happy user of the software. 

You can still use the same trick :-)

Open a terminal (Terminal.app)
/Applications/Subsurface.app/Contents/MacOS/Subsurface -v

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

Re: Subsurface-mobile status update

2016-08-14 Thread Robert Helling 
Hi Dirk,

> Am 14.08.2016 um 17:17 schrieb Dirk Hohndel :
> 
> OK, that's good. Thanks, Robert.
> 
> Now the question is "do you want to pay the extortion fee to Apple to
> become a developer?" if yes, I think I should be able to somehow add you
> to the Subsurface team and hopefully we can both create working signed
> binaries…

I have already paid the fee (not realizing you don’t need it if you only want 
to deploy to your own device). My appleID is hell...@atdotde.de

> 
> What I find interesting, though, is that for me on my new laptop I wasn't
> able to create working binaries. The fact that you were able to do so
> means that maybe I should just blow away the whole development tree there
> and start from scratch and maybe things will work.
> 
> Which version of Qt are you working with?

I am still on Qt 5.5 (which also means that may of the QWebEngine things are 
not there, yet. But that’s another story. I had 5.6 installed at some point but 
for some reason I cannot remember moved it away). I should probably soon go to 
5.7.

At which stage did you fail? I have to change one item in Info.plist.in to say 
I am me and not you, though. Is there anything I should try first?

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

Re: Latest iOS release

2016-08-14 Thread Dirk Hohndel 
On Sun, Aug 14, 2016 at 05:13:04PM +0200, Martin de Weger wrote:
> 
> 
> > Op 14 aug. 2016, om 17:08 heeft Dirk Hohndel  het 
> > volgende geschreven:
> > 
> > On Sun, Aug 14, 2016 at 03:40:21PM +0200, Martin de Weger wrote:
> >> Hi Guys,
> >> 
> >> I just downloaded an tested the latest version of the iOS app. The divest 
> >> is shown correctly again (the last entry is no longer hidden under the top 
> >> bar).
> >> 
> >> I did notice the function “slide down to refresh” doesn’t work any more. 
> >> If you want to refresh, you have to go to the menu and select the manual 
> >> refresh.
> > 
> > Hmm. Obviously I haven't played with this in a while. Can you remind me
> > what exactly you mean here?
> > 
> 
> In iOS there is a default option to refresh the current app. all it
> takes is a down “swipe” and the app is refreshed. I was able to do the
> same in the mobile version of Subsurface. now I have to go to the menu
> (3 bars on the left bottom), select manage dives and manual refresh.

At the risk of saying something stupid... I do not think that this has
every worked. I certainly never implemented this...
Are you 100% sure about this?

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

Re: Frequent cloud storage authentication errors with Subsurface 4.5.6 (desktop)

2016-08-14 Thread Martin de Weger 
I haven’t build the app, I installed the app from the dmg file provided on the 
subsurface website. My software programming skills are close to non-existent, I 
can do testing and I’m a happy user of the software. 

> Op 14 aug. 2016, om 17:13 heeft Dirk Hohndel  het volgende 
> geschreven:
> 
> On Sun, Aug 14, 2016 at 03:48:38PM +0200, Martin de Weger wrote:
>> I did some testing for the latest release for the iOS app and had to edit 
>> multiple dives. Every time I tried to save to the cloud, I’m getting the 
>> attached error.
>> 
>> It takes me 3 to 4 times to save the log to the cloud. Is there anyway I can 
>> enable (or find) a log file on my Mac to help you to determine what might be 
>> causing this issue? My internet connection is fast (200 down, 20 up) and 
>> stable.
> 
> Once I have the iOS app building with the latest Kirigami (and updated for
> testers), this is the next thing I want to tackle.
> 
> You can see more debugging output on your Mac by running things from a
> terminal
> 
> After building run
> 
> ./Subsurface.app/Contents/MacOS/Subsurface -v
> 
> Then you get the debug output on the console. But I don't think this will
> help as in my tests it didn't show anything overly intersting in the case
> where (usually incorrectly) the error is shown.
> 
> /D

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

Re: Subsurface-mobile status update

2016-08-14 Thread Dirk Hohndel 
On Sun, Aug 14, 2016 at 05:06:09PM +0200, Robert Helling wrote:
> Hi,
> 
> > Am 14.08.2016 um 08:53 schrieb Robert C. Helling 
> > :
> > 
> >  Will try again these days.
> 
> I can confirm that I am able to build operational iOS binaries from latest 
> master. I have not tried to update kirigami, yet.

OK, that's good. Thanks, Robert.

Now the question is "do you want to pay the extortion fee to Apple to
become a developer?" if yes, I think I should be able to somehow add you
to the Subsurface team and hopefully we can both create working signed
binaries...

What I find interesting, though, is that for me on my new laptop I wasn't
able to create working binaries. The fact that you were able to do so
means that maybe I should just blow away the whole development tree there
and start from scratch and maybe things will work.

Which version of Qt are you working with?

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

Re: Frequent cloud storage authentication errors with Subsurface 4.5.6 (desktop)

2016-08-14 Thread Dirk Hohndel 
On Sun, Aug 14, 2016 at 03:48:38PM +0200, Martin de Weger wrote:
> I did some testing for the latest release for the iOS app and had to edit 
> multiple dives. Every time I tried to save to the cloud, I’m getting the 
> attached error.
> 
> It takes me 3 to 4 times to save the log to the cloud. Is there anyway I can 
> enable (or find) a log file on my Mac to help you to determine what might be 
> causing this issue? My internet connection is fast (200 down, 20 up) and 
> stable.

Once I have the iOS app building with the latest Kirigami (and updated for
testers), this is the next thing I want to tackle.

You can see more debugging output on your Mac by running things from a
terminal

After building run

./Subsurface.app/Contents/MacOS/Subsurface -v

Then you get the debug output on the console. But I don't think this will
help as in my tests it didn't show anything overly intersting in the case
where (usually incorrectly) the error is shown.

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

Re: Latest iOS release

2016-08-14 Thread Martin de Weger 


> Op 14 aug. 2016, om 17:08 heeft Dirk Hohndel  het volgende 
> geschreven:
> 
> On Sun, Aug 14, 2016 at 03:40:21PM +0200, Martin de Weger wrote:
>> Hi Guys,
>> 
>> I just downloaded an tested the latest version of the iOS app. The divest is 
>> shown correctly again (the last entry is no longer hidden under the top bar).
>> 
>> I did notice the function “slide down to refresh” doesn’t work any more. If 
>> you want to refresh, you have to go to the menu and select the manual 
>> refresh.
> 
> Hmm. Obviously I haven't played with this in a while. Can you remind me
> what exactly you mean here?
> 

In iOS there is a default option to refresh the current app. all it takes is a 
down “swipe” and the app is refreshed. I was able to do the same in the mobile 
version of Subsurface. now I have to go to the menu (3 bars on the left 
bottom), select manage dives and manual refresh.

>> Thanks again for all your hard work!
> 
> I'm trying to manage this weekend to at least catch up with all that
> happened... I'm quite frustrated that I wasn't able to stay on top of
> things more.
> 
> /D

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

Re: Latest iOS release

2016-08-14 Thread Dirk Hohndel 
On Sun, Aug 14, 2016 at 03:40:21PM +0200, Martin de Weger wrote:
> Hi Guys,
> 
> I just downloaded an tested the latest version of the iOS app. The divest is 
> shown correctly again (the last entry is no longer hidden under the top bar).
> 
> I did notice the function “slide down to refresh” doesn’t work any more. If 
> you want to refresh, you have to go to the menu and select the manual refresh.

Hmm. Obviously I haven't played with this in a while. Can you remind me
what exactly you mean here?

> Thanks again for all your hard work!

I'm trying to manage this weekend to at least catch up with all that
happened... I'm quite frustrated that I wasn't able to stay on top of
things more.

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

Re: Subsurface-mobile status update

2016-08-14 Thread Robert Helling 
Hi,

> Am 14.08.2016 um 08:53 schrieb Robert C. Helling 
> :
> 
>  Will try again these days.

I can confirm that I am able to build operational iOS binaries from latest 
master. I have not tried to update kirigami, yet.

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

Re: Frequent cloud storage authentication errors with Subsurface 4.5.6 (desktop)

2016-08-14 Thread Martin de Weger 
I did some testing for the latest release for the iOS app and had to edit 
multiple dives. Every time I tried to save to the cloud, I’m getting the 
attached error.



It takes me 3 to 4 times to save the log to the cloud. Is there anyway I can 
enable (or find) a log file on my Mac to help you to determine what might be 
causing this issue? My internet connection is fast (200 down, 20 up) and stable.

Martin

> Op 29 jul. 2016, om 16:22 heeft Adric Norris  het 
> volgende geschreven:
>
> [To the list this time]
>
> I almost always hit this on the initial save, but if I followup with either 
> Save or Save to cloud storage it usually completes without error 
> eventually... this often requires 3 or 4 tries.
>
> On Fri, Jul 29, 2016 at 9:18 AM, Adric Norris  > wrote:
> I almost always hit this on the initial save, but if I followup with either 
> Save or Save to cloud storage it usually completes without error 
> eventually... this often requires 3 or 4 tries.
>
> On Fri, Jul 29, 2016 at 8:54 AM, Martin de Weger  > wrote:
> Actually, I have this issue as well. It looks to me there are issues if you 
> press save multiple times. I haven’t reported it myself since I’m not diving 
> a lot at the moment (unfortunately) and I can upload my dives if I either am 
> patient and wait for the sync to complete or press safe multiple times.
>
> My connection is working fine with all other applications, it looks like the 
> problem is isolated to Subsurface.
>
> Regards,
>
> Martin de Weger
>
>> Op 29 jul. 2016, om 15:49 heeft Adric Norris > > het volgende geschreven:
>>
>> Recently took a cross-country dive trip, and had a chance to test a bit 
>> more. Sadly, I seem to be able to reproduce the issue very reliably... 
>> multiple Subsurface cloud accounts, multiple platforms (Linux, Mac, and 
>> Windows), and several different home networks and underlying ISPs (none of 
>> which exhibit any problems with other applications). Nothing makes any 
>> difference... the problem occurs effectively every time.
>>
>> I'm honestly surprised that no one else seems to be encountering this 
>> behaviour. From what I can see it occurs with virtually any attempt to save 
>> when using cloud storage, regardless of network quality and latency.
>>
>> On Tue, Jul 12, 2016 at 8:25 PM, Adric Norris > > wrote:
>> Is anyone else frequently seeing the following error when saving changes?
>>
>> Authentication to cloud storage failed.
>> Cannot sync with cloud server, working with offline copy.
>>
>> While this sometimes seems to be legitimate, often the error is displayed 
>> even though the changes appear to have been saved successfully. For example 
>> I'll change the Notes text for a recent dive and save (File -> Save), which 
>> triggers the error. I then look it up my dives on 
>> https://cloud.subsurface-divelog.org 
>> , and (frequently, but not always) 
>> find that the changed text is indeed present. Attempting to save multiple 
>> times in a row or choosing "Save to cloud storage" will sometimes complete 
>> without error, but it's very inconsistent.
>>
>> This has been going on for awhile but I'd been assuming it was an issue with 
>> my home network, or notebook installation... I'm running Ubuntu 16.04 
>> (Xenial), with Subsurface installed from the PPA. However I recently 
>> upgraded Subsurface (from either 4.5.2 or 4.5.3, IIRC) on my sister's 
>> macbook while we were visiting family, and she encountered the same stream 
>> of errors when saving her first new dive... we ended up trying to save about 
>> 4 times, before being confident all was well. Since the notebook, OS, and 
>> network were all different, I now believe this to be a more general issue.
>>
>> Any idea how I can help to troubleshooting the issue? I'm happy to do 
>> whatever I can, but am not really sure where to begin.
>>
>> Thanx!
>>
>> --
>> "In the beginning the Universe was created. This has made a lot of people 
>> very angry and been widely regarded as a bad move." -Douglas Adams
>>
>>
>>
>> --
>> "In the beginning the Universe was created. This has made a lot of people 
>> very angry and been widely regarded as a bad move." -Douglas Adams
>> ___
>> subsurface mailing list
>> subsurface@subsurface-divelog.org 
>> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface 
>> 
>
>
>
>
> --
> "In the beginning the Universe was created. This has made a lot of people 
> very angry and been widely regarded as a bad move." -Douglas Adams
>
>
>
> --
> "In the beginning the Universe was created. This has

Re: Subsurface-mobile status update

2016-08-14 Thread Joakim Bygdell 

> On 14 Aug 2016, at 06:29, Dirk Hohndel  wrote:
> 
> 
> I still haven't managed to make the latest Kirigami work. And I don't think 
> I'll finish that today as I'm jet lagged and about to fall asleep on my 
> keyboard. But at least our iOS testers should be able to continue to use 
> Subsurface-mobile.

When you add Marcos patch "use-kirigami-built-in-static-mode” and work out some 
of the missing parts it builds properly.
But the app crashes on launch due to not being able to find the Kirigami 
components.

> 
> I think I asked this before - is there anyone else who is even able to build 
> on iOS? Tomaz no longer has his Mac. Anyone else?

Once the Kirigami issue has been solved I should be able to build and test the 
iOS version as well.
> 
> /D
> ___
> 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

Re: Subsurface-mobile status update

2016-08-14 Thread Robert C. Helling 
Hi dirk,

> Am 14.08.2016 um 06:29 schrieb Dirk Hohndel :
> 
> I think I asked this before - is there anyone else who is even able to build 
> on iOS? Tomaz no longer has his Mac. Anyone else?

I have in the past built successfully for iOS but haven't tried in a while. In 
particular, after you said it broke for you, I didn't dare to update. Will try 
again these days. 

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