Re: Developing and Deploying devices

2016-04-12 Thread Robert Helling
Hi everybody, > On 12.04.2016, at 16:35, Dirk Hohndel wrote: > > As for the development process, right now I consider this the "storming" phase A quick report from my side: Since that was easiest, I got hold of a RPi3 (which has both wifi and BT on board) to get started with

Re: Developing and Deploying devices

2016-04-12 Thread Dirk Hohndel
On Tue, Apr 12, 2016 at 06:36:37PM +0100, JB2Cool wrote: > > > > Did I miss something but why the need for this box at all? (Sorry if this > > has been covered previously) > > DiveMate (http://www.divemate.de/) seem to do exactly what I think you are > trying to with either a USB or IR dongle,

Re: Developing and Deploying devices

2016-04-12 Thread JB2Cool
And now I have read the notes about iRDA computers on OS X and Win10. Ignore me, late to the party as always. JB On 12 April 2016 at 18:36, JB2Cool wrote: > Did I miss something but why the need for this box at all? (Sorry if this >> has been covered previously) > > >

Re: Developing and Deploying devices

2016-04-12 Thread Dirk Hohndel
On Tue, Apr 12, 2016 at 06:55:54PM +0200, Jeroen Massar wrote: > >> > >> A Poll would be the proper way to select this. > > > > You must be new here :-) > > Absolutely ;) There will be no poll for the name :-) > Lets first select if we want to do BT or WiFi. I am partially leaning to > BT, but

Re: Developing and Deploying devices

2016-04-12 Thread Jeroen Massar
On 2016-04-12 18:42, Dirk Hohndel wrote: > On Tue, Apr 12, 2016 at 05:39:54PM +0200, Jeroen Massar wrote: The device: * a name ("OnSurface" ? :) >>> >>> Subsurface Box >>> >>> But of course this is open to discussion :-) >> >> I am not one to do a long bikeshed. >> >> A Poll would be the

Re: Developing and Deploying devices

2016-04-12 Thread Dirk Hohndel
On Tue, Apr 12, 2016 at 05:35:54PM +0200, Thomas Pfeiffer wrote: > On Dienstag, 12. April 2016 07:58:04 CEST Dirk Hohndel wrote: > > > What I suggested to them is that CHIP should ship with an open > > WiFi access point running and a web server to connect to and > > then a simple web interface

Re: Developing and Deploying devices

2016-04-12 Thread Dirk Hohndel
On Tue, Apr 12, 2016 at 06:20:28PM +0300, Miika Turkia wrote: > > * Dive Computer connectivity > > - USB Host to Dive Computer > > - USB<->IRDA connector support > > - others? > > Likely USB is the minimum, and that then things can plug > > into it that actually connect to the DC. > > >

Re: Developing and Deploying devices

2016-04-12 Thread Miika Turkia
On Tue, Apr 12, 2016 at 6:39 PM, Jeroen Massar wrote: > (google is not very friendly for searching for "chip" btw...) https://www.google.com/search?q=c.h.i.p.+computer ___ subsurface mailing list subsurface@subsurface-divelog.org

Re: Developing and Deploying devices

2016-04-12 Thread Jeroen Massar
On 2016-04-12 16:58, Dirk Hohndel wrote: [..] >> Hence the best way to go is to just use the packaging system of the >> distro that gets chosen. > > So the CHIP uses a Debian based system. But as I said in my last two > emails, exposing that to end users is already declaring defeat. Indeed,

Re: Developing and Deploying devices

2016-04-12 Thread Thomas Pfeiffer
On Dienstag, 12. April 2016 07:58:04 CEST Dirk Hohndel wrote: > What I suggested to them is that CHIP should ship with an open > WiFi access point running and a web server to connect to and > then a simple web interface where you enter a URL from which > a package is then installed. Super easy

Re: [PATCH 1/2] Fix initial build of APK

2016-04-12 Thread Henrik Brautaset Aronsen
"rm -f" is a bit shorter :) Cheers, Henrik -- Sent from my phone 12. apr. 2016 16.57 skrev "Miika Turkia" : > Running subsurface/packaging/android/build.sh after deleting > subsurface-mobile-build-arm directory fails for me due to missing > ssrf-version.h file. Thus we

Re: Developing and Deploying devices

2016-04-12 Thread Martin Gysel
Am 12.04.2016 um 16:36 schrieb Dirk Hohndel: > >> On Apr 12, 2016, at 4:53 AM, Martin Gysel wrote: >>> The other thing is deployment. Initially, that’s simple, we provide disk >>> images. But then, what is the upgrade path? Connect to wifi and do git >>> pull? apt-get

Re: Developing and Deploying devices

2016-04-12 Thread Dirk Hohndel
> On Apr 12, 2016, at 5:16 AM, Jeroen Massar wrote: > > On 2016-04-12 11:53, Robert Helling wrote: >> Hi, >> >> I have been thinking a bit more about setting up a small device >> (C.H.I.P. or similar) to do the dive computer read out and communication >> with the mobile

[PATCH 2/2] Set default build number for apk building

2016-04-12 Thread Miika Turkia
Having build number as mandatory parameter seems unnecessary, thus setting default value (used for andoird:versionCode) to 0. Signed-off-by: Miika Turkia --- packaging/android/build.sh | 2 ++ 1 file changed, 2 insertions(+) diff --git a/packaging/android/build.sh

[PATCH 1/2] Fix initial build of APK

2016-04-12 Thread Miika Turkia
Running subsurface/packaging/android/build.sh after deleting subsurface-mobile-build-arm directory fails for me due to missing ssrf-version.h file. Thus we should only delete it if it actually exists. Signed-off-by: Miika Turkia --- packaging/android/build.sh | 5 -

Re: Developing and Deploying devices

2016-04-12 Thread Dirk Hohndel
> On Apr 12, 2016, at 4:53 AM, Martin Gysel wrote: >> The other thing is deployment. Initially, that’s simple, we provide disk >> images. But then, what is the upgrade path? Connect to wifi and do git >> pull? apt-get upgrade/update? Get a new disk image? That needs to be >>

Re: Developing and Deploying devices

2016-04-12 Thread Dirk Hohndel
> On Apr 12, 2016, at 2:53 AM, Robert Helling wrote: > > Hi, > > I have been thinking a bit more about setting up a small device (C.H.I.P. or > similar) to do the dive computer read out and communication with the mobile > device. > > One thing I am worried about is how to

Fwd: Re: Developing and Deploying devices

2016-04-12 Thread Willem Ferguson
On 12/04/2016 13:53, Martin Gysel wrote: I think it depends on the used base. if it's a debian based system (and I would start with such a system), then providing a apt-get urls seems to be the easiest solution. if using a leaner base (e.g. to reduce startup time as much as possible) then

Re: Developing and Deploying devices

2016-04-12 Thread Jeroen Massar
On 2016-04-12 11:53, Robert Helling wrote: > Hi, > > I have been thinking a bit more about setting up a small device > (C.H.I.P. or similar) to do the dive computer read out and communication > with the mobile device. > > One thing I am worried about is how to collaboratively develop for such >

Re: Subsurface not updated to 4.5.5 on Open Build Service (openSUSE and Fedora builds)

2016-04-12 Thread Guillaume Gardet
It is deployed and working fine. Thanks! Guillaume Le 11/04/2016 15:10, Dirk Hohndel a écrit : sorry, script fell over its feet. It's building now /D On Apr 11, 2016, at 1:41 AM, Guillaume Gardet wrote: Hi Dirk, Subsurface is still at 4.5.4 on OBS. Could you

Re: Developing and Deploying devices

2016-04-12 Thread Martin Gysel
Am 12.04.2016 um 11:53 schrieb Robert Helling: > Hi, > > I have been thinking a bit more about setting up a small device > (C.H.I.P. or similar) to do the dive computer read out and communication > with the mobile device. > > One thing I am worried about is how to collaboratively develop for