Now Accepting GSoC 2016 Mentor Organization Applications

[Anton Lundin]

On 09 February, 2016 - Dirk Hohndel wrote:

> On Tue, Feb 09, 2016 at 12:53:42PM +0000, JB2Cool wrote:
> > On 9 February 2016 at 12:48, Sebastian Kügler <sebas at kde.org> wrote:
> > > >
> > > > A possible project I could mentor in the summer would be a mobile
> > > version of
> > > > the planner (if nobody vetos it). That would be a separate app from
> > > > subsurface-mobile but of course share a lot of code.
> 
> This is open source. No one can veto what you want to do.
> 
> > > > I would love this!  But why having it as a separate app?
> > >
> > > We only have a fighting chance to create an app that feels high-quality if
> > > we
> > > reduce complexity. Dirk has said it before, and I'm entirely behind this:
> > > dive
> > > planning is not a core feature for the foreseeable future. We need to limit
> > > the featureset to the absolute necessary for quite a while.
> > >
> > > I'd much rather have something small, stable and high quality than a swiss
> > > army knife that falls apart the moment you look at it.
> > >
> > > There are many areas in subsurface which need improvements, implementing a
> > > dive planner is going to distract from making them work really well.
> 
> THIS. There is no way I'd side track Subsurface-mobile for this.
> So yes, go ahead, build a Subsurface-planner app for mobile. Maybe at some
> point that can be merged back. Or maybe it stays separate.
> 
> > So don't implement the dive planning into the subsurface-mobile just yet
> > but does this really justify the creation of another companion app to
> > perform the dive planning? That'll then be 3 mobile subsurface apps we
> > have, surely better to restrict the number of them and eventually (Even if
> > it's a while out) merge the functionality into a single app.
> 
> 
> The companion app goes away. Subsurface-mobile replaces that (even though
> that part of the functionality definitely needs a lot more testing). But
> no, this would get us Subsurface-mobile and Subsurface-planner.
> 

I'd say that the killer feature a Subsurface-mobile app with a planner
can provide is planning based on actual previous dives. None of the
other mobile planning apps can do that, because they can't integrate
with divecomputer data.

I'd go for putting it in the same app. It doesn't even need to be
enabled in the play-store version, or just hidden behind a <here be
dragons> setting.


( I actually did sketch out a planner app to, based on using subsurface
as a jni library and wrote the frontend in Android native java. The
problem was that code never made it of my laptop, and that drive died
last week. Dam you spinning rust )


//Anton


-- 
Anton Lundin	+46702-161604