Show deco stops in planner table

[Dirk Hohndel]

On Mon, Jun 02, 2014 at 11:02:13AM -0400, William Perry wrote:
> On Jun 2, 2014, at 10:34 AM, Robert Helling <helling at atdotde.de> wrote:
> 
> > On 01.06.2014, at 20:19, Dirk Hohndel <dirk at hohndel.org> wrote:
> > 
> >> On Sun, Jun 01, 2014 at 08:11:26PM +0200, Robert C. Helling wrote:
> >>> 
> >>> On 01 Jun 2014, at 18:47, Martin Gysel <me at bearsh.org> wrote:
> >>> 
> >>>> what about a template based output? where everyone can easily change the
> >>>> template like
> >>>> "\D \T \G \R" for "Depth Time Gas Runtime"
> >>> 
> >>> I am sure that is too complex for Joe Average User. My plan is to go for checkboxes in the preferences (or the planner options besides others where we currently display the marble.
> >>> 
> >>> [ ] Show runtime
> >>> [ ] Show duration for stops
> >>> [ ] Show transitions
> >> 
> >> Works for me. Just make sure you do this based on the latest master as I
> >> did a few changes to the code that added the plan to the notes (as that
> >> was rather wrong)
> >> 
> >> /D
> > 
> > Here you go. Arrangement of checkboxes is not perfect but subject to change when we reorganize the planner preferences anyway.
> 
> Are there plans to be able to print the planned dive in a simple format
> that can just be cut & pasted onto slates?  One of the first things I
> did once I got beyond the basic deco training was write a
> parser/formatter for the mess that V-Planner spit out.  Writing out the
> deco schedule for a 100 meter dive onto a 2”x4” flip-slate was …
> primitive to say the least.  I know a lot of tech divers (and probably
> one agency) that would be really excited to see a planner where you
> could just print out the plan, with automatic contingency plans (too
> deep, too long, lost deco, etc).  The basic one I wrote for
> V-Planner/MultiDeco allows you to specify the depth at which you want to
> blow the bag (leaving the bottom, specific depths, or first stop of at
> least N minutes), the size of the slates you plan on putting them on, as
> well as color coding gas change events.

The problem is once again: how do you make it configurable so that it
meets all these different needs that people have.
Add to that the fact that printing support always adds more issues.

All that said, there's nothing stopping us from getting this implemented
and added - but it takes someone to at least start it.

> Even a way to export this as an XML document or easily parsed text file
> would be a huge win.  And if exporting is the way to go can we please
> keep ALL the information in any contingencies that are automatically
> generated?  The automatic contingency output in V-Planner leaves out a
> ton of information so it is very difficult to keep things like the gas
> switches on the contingencies.

We are not even trying to do contingency planning.
You'll have to go back and modify the plan, modify the available gas, etc.


/D