On 9 February 2016 at 12:48, Sebastian Kügler <se...@kde.org> wrote:
> On Tuesday, February 09, 2016 12:17:50 PM Henrik Brautaset Aronsen wrote: > > On Tue, Feb 9, 2016 at 11:37 AM, Robert Helling <hell...@atdotde.de> > 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. > > > > 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. > -- > sebas > > 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. JB
_______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface