> On Nov 12, 2015, at 3:12 PM, Lubomir I. Ivanov <neolit...@gmail.com> wrote: > alright... > > so here is the visual of the working POC: > https://dl.dropboxusercontent.com/u/1627980/subsurface/mobile_dive_details_concept2.gif > > <https://dl.dropboxusercontent.com/u/1627980/subsurface/mobile_dive_details_concept2.gif>
This is really cool - I especially like the beautiful rendering of the dive profile :-) > i restructured the classes a little and now it works the following way: > - one DiveContainer that defines a navigation callback (i.e. > left/right) and includes 2 Dives > - each Dive contains a SwipeArea inside a Flickable. the actual dive > details are inside the SwipeArea itself. > > this is a workaround as i would have preferred to have one SwipeArea > over the whole DiveContainer and not for each Dive; the solution is > tolerable as long as we don't have thousands of Dive instances. one > Flickable per Dive is desired though, like seen in the visual/GIF. > > attached is the updated source (with comments this time). > hope that helps, Sebastian. I'll have to admit that the amount of activity on Subsurface-mobile makes me smile. I really hoped that a few people here would get into the idea of making a mobile app happen and would collaborate. We need more people working on our UIs (both DT and mobile). > P.S.: QML+ JS is fun! I'll admit that I'm still in the "struggling" phase. But I'm sure I'll get the hang of it. Right now I'm making fast progress on allowing us to drop the companion apps and the web service. Instead of telling people to collect GPS fixes on their phone, pushing them to a server, downloading them from the server to the desktop and then merging them there, we'll simply tell people to use Subsurface-mobile on their phone. They can turn on the location server and after a day of diving they open their cloud storage on their mobile device (hopefully download their dives on their mobile device - or if they have dive computers we can't support on their phone, do the download on the computer), trigger the location merge and then save back their updated data to the cloud storage. Much simpler, one fewer account needed, etc. AND I get to retire the python code running on my server :-) /D
_______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface