I don't really use this, so I don't mind changes myself.

However, please provide:

1/ when we upgrade from to gramps33/gramps.ini, is it possible to upgrade any stored settings of these reports? That is, I would not want somebody upgrading and having his old hand changed setting causing garbish. So I see options:
a)we can upgrade the ini files of the reports on first run of gramps 3.3
b)we choose new keys for the fields, so for gramps 3.3 they will see the defaults the first time, and have to change it again
c)we recognize the old format, and upgrade in the report when it is run.

Implement one of the above, I would go for b)

2/Make sure that there are sane defaults. Think about this carefully! Most people will _not_ change the defaults the first times they run Gramps. Many open source software sucks because the defaults are not nice (eg the gtk default icon theme).

Benny


2010/9/4 Craig J. Anderson <ander882@hotmail.com>
> Craig,
>
> This has been well thought out and I think we should use it.

thank you


>
> I have a couple of questions:
>
> 1. Can we specify a slash year format in dates? (e.g. 1734/5)

yes.  you can use any character you wish.  You will just have to use a control character if you wish to display 'y', 'm', or 'd'. 
I'll add another example.  done.


> 2. Can groups be nested?

yes.  I do have an example of this in the groups section of the docs.  I'll add another.


> 3. I see that you can leave a group without a closing bracket. Is this
> a good idea?

I don't think I have any way of forcing this.  And when it is used for optionally removing a line it may be trouble if the person accidentally added a space after the last } and can't figure out why it always prints.  But mostly I don't think I can enforce it.


>
> I can also see some possible enhancements such as place formatting or
> substitution variables to include attributes.

Oooh.  please tell me formatting for places.  I could not think of anything.  I will add it for sure!

I will also be adding the $a(attribute) here very soon.  I forgot it.  But I need to see some examples on this.  Because I don't know if I can allow something like:
$a(\(att\ribute\)).  so my question is allow control variables or not.  maybe someone has  a '(' or '\' in the attribute name?  I'm a little leery of this, but I will add it.

  Craig A.


>
> Regards,
>
>
> Nick.
>
>
> Craig J. Anderson wrote:
> >
> > I have been thinking about SubstKeywords.py a lot recently and I do
> > not like the direction that it is heading (Reasons below).
> >
> >
> > So with Peter Landgren's help, we have made a new drop-in replacement
> > for SubstKeywords.py with a lot of new features. The full Docs and
> > download are at:
> >
> > http://ander882.110mb.com/index.php?p=gramps.display3
> >
> >
> > Here are some examples of what you can do:
> >
> > $n -> Displays the name as per Gramps preferences
> >
> > $n(G, f) -> Displays the persons Given (Last) name in CAPS, then the
> > first name
> >
> > $n(f g){ ($n(c))} -> Displays the first and last name then if
> > available the call name in ()
> >
> > $b -> Displays the Birth Date as per Gramps preferences
> >
> > $b(yyyy-mmm-dd) -> the Birthday like '2010-Jan-03'
> >
> > $d(mmm-dd yy) -> Jun-07 85
> >
> > {m. $m(yyyy) {- ($v(yyyy)) -> Optionally display the line if never
> > married. If so display the year married and divorce (in () if devoiced)
> >
> > Date formats were modeled after Microsoft date formatting found at:
> >
> > http://msdn.microsoft.com/en-us/library/8kb3ddd4.aspx
> >
> >
> > Please tell me what you think of this new code. We think it would be a
> > great addition and are submitting it for review and admission into Gramps.
> >
> >
> > Here are the reasons why I don't like the new variables ($f, $p, $dy,
> > $by, $my $nc, $Nc, $fc, $sc, $Sc ) in SubstKeywords.py:
> >
> > 1. these are not new variables, these are formatting of existing
> > variables
> >
> > 2. multi length variables are a big ugly can of worms.
> >
> > 2a is $Sc really $S with a character 'c' after it?
> >
> > 2b squishing everything down to single character variable is ok, but
> > there is a LOT of them
> >
> > 2c making every variable a length of two is still a little messy
> >
> > 2d ending variables with a $ would help multi length variables ie $Sc$
> > or $n$
> >
> > 3e what about a lot of other different formats that people might want.
> >
> > 3. already missing $fc and $pc and a variable for Spouses ID and
> > marriage ID, and divorce date places.
> >
> >
> > Craig A.
> >
> > ------------------------------------------------------------------------
> >
> > ------------------------------------------------------------------------------
> > This SF.net Dev2Dev email is sponsored by:
> >
> > Show off your parallel programming skills.
> > Enter the Intel(R) Threading Challenge 2010.
> > http://p.sf.net/sfu/intel-thread-sfd
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Gramps-devel mailing list
> > Gramps-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/gramps-devel
> >

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Gramps-devel mailing list
Gramps-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gramps-devel