[APBeta] List columns "Set to Default"

[Jeff Young]

Paul --

While I have a few different plan "configurations", I use one of them for the bulk of my plans, and the rest are generally used only for a single plan each.  So while I can imagine the usefulness of multiple templates, I wouldn't feel overly constrained with a single template.  

Going even further, I only have about 4 user-defined columns, and while I don't use them in all plans, I usually add them to all plans anyway and just leave them empty where I'm not using them.  So I don't have a strong personal bias for a/b/c either.

But... if you were going to spend effort here, then it seems like multiple templates would be more valuable than getting to chose whether or not the user-defined columns formed part of a single template definition.

Cheers,
-- Jeff.


> -----Original Message-----
> From: apbeta-bounces at lists.astroplanner.net [mailto:apbeta-bounces at lists.astroplanner.net] On Behalf Of
> Paul Rodman
> Sent: Thursday, July 02, 2009 9:57 PM
> To: AstroPlanner Beta Testers
> Subject: Re: [APBeta] List columns "Set to Default"
> 
> 
> On Jul 2, 2009, at 1:13 PM, Jeff Young wrote:
> 
> > I'd be inclined to go with (b).  For plans that have different sets
> > of user-defined columns, I expect I'd have different column
> > definition templates as well.
> 
> Well currently there's only one (unnamed) "template".
> 
> > So tying a particular template to a particular set of user-defined
> > columns seems fine.
> 
> Based on me above assertion, does that remain true?
> 
> I could, I suppose, allow different "named" templates to be saved.
> Which one gets used for a new plan? Yeh, I know: "ask the user".
> 
> Paul R.
> 
> >> -----Original Message-----
> >> From: apbeta-bounces at lists.astroplanner.net [mailto:apbeta-bounces at lists.astroplanner.net
> >> ] On Behalf Of
> >> Paul Rodman
> >> Sent: Thursday, July 02, 2009 4:07 PM
> >> To: AstroPlanner Beta Testers
> >> Subject: [APBeta] List columns "Set to Default"
> >>
> >> I have now managed to get this feature working (being able to save a
> >> list column layout as a "template" and automatically applying it to
> >> new plans, or optionally to existing plans)*. However, this does not
> >> include any user-defined fields. These will be ignored (i.e. disabled
> >> until enabled via Edit->List Columns...).
> >>
> >> I am pondering what to do about any user-fields in the "template"
> >> that
> >> are not present in the plan that the template is to act on:
> >>
> >> a. Just ignore them (the current situation).
> >> b. Automatically create those user fields in the plan if they don't
> >> exist.
> >> c. Do (b) but ask the user each time.
> >>
> >> How do you feel about this? (assuming you have any idea what I'm
> >> rambling on about here).
> >>
> >> Paul R.
> >>
> >> * and in doing so I have fixed some bugs with editing list columns.
> 
> _______________________________________________
> APBeta mailing list
> APBeta at lists.astroplanner.net
> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net