gramps

2010/3/15 lcc <lcc@...>:
> I like it. I'm not sure why you need extra semantics in your final question. Isn't it
> already covered?
>
> {and married to $s}

Yes, it looks nice.
I suppose your design question comes from wanting to avoid nesting of groups?
If you define the syntax as:

A { can contain one of the following
 *  one or more variables with $
 *  one or more groups.
The entire group with { will be printed if one of the $ variables
inside of it contains information.

With this definition, you can build up a structure in the code, and
give a warning to user when he created a wrong substition text.

Then you will end up with a structure of eg
top
 - var
 - group
     -var
 - group
     - group
        - var
     - group
        - var
        - var

If you do not want to make groups in groups, then use the - at the
start of the line to avoid confusion with the use of { for groups.

Benny

> --lcc
>
> On Mon, 03/15/2010 at 1:28am, "Craig J. Anderson" <ander882@...> wrote:
>
>> I am currently working on the Graphical Ancestor and Descendant reports.  I
>> have updated them and along with it, I have also updated the Substitution
>> Values that can used:
>> The old:  http://www.gramps-project.org/wiki/index.php?title=Gramps_3.
>> 2_Wiki_Manual_-_Reports_-_part_2
>> Proposed:http://ander882.110mb.com/index.php?p=gramps.display
>> I have removed the % variables and added {} groupings to remove parts that
>> are not wanted.
>> Example:  'Was born {on $b }{at $B' will print 'Was born at over there' if
>> the date is not known and 'Was born on 2010-0101 ' if the place is not know.
>>  If neither is known, 'Was born ' will print.
>> So please take a look and tell me what you think/like/dislike.
>> And for those that read through to the end, there is a design question at
>> the bottom.
>> thanks.
>>   Craig A.
>
>> ----------
>> Hotmail is redefining busy with tools for the New Busy. Get more from your
>> inbox.
>> Sign up now.
>
> Powered by the 6zap. Sign up at http://www.6zap.com for an account that provides advanced e-mail, calendar and contacts capabilities.
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Gramps-devel mailing list
> Gramps-devel@...
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>

Sorry that has not been stated...  Nested groups are possible.  I just don't have a good example.  

Maybe '{Was born {on $b }{at $B'

I need the extra semantic '-' because the person may prefer a blank line instead of the entire line being removed...

> With this definition, you can build up a structure in the code, and
> give a warning to user when he created a wrong substition text.

Hmm.  I not sure about how to do this or even if it is desired...  If a person were to use 'Was born } .. }'  the ending brackets would just be displayed because they don't have an opening bracket...  And how would you show a line is incorrect in the GUI?

thanks.

  Craig A.

> Date: Mon, 15 Mar 2010 13:23:06 +0100
> Subject: Re: [Gramps-devel] Substitution Values updates for your review.
> From: benny.malengier@...
> To: ander882@...
> CC: gramps-devel@...
> 
> 2010/3/15 lcc <lcc@...>:
> > I like it. I'm not sure why you need extra semantics in your final question. Isn't it
> > already covered?
> >
> > {and married to $s}
> 
> Yes, it looks nice.
> I suppose your design question comes from wanting to avoid nesting of groups?
> If you define the syntax as:
> 
> A { can contain one of the following
>  *  one or more variables with $
>  *  one or more groups.
> The entire group with { will be printed if one of the $ variables
> inside of it contains information.
> 
> With this definition, you can build up a structure in the code, and
> give a warning to user when he created a wrong substition text.
> 
> Then you will end up with a structure of eg
> top
>  - var
>  - group
>      -var
>  - group
>      - group
>         - var
>      - group
>         - var
>         - var
> 
> If you do not want to make groups in groups, then use the - at the
> start of the line to avoid confusion with the use of { for groups.
> 
> Benny
> 
> > --lcc
> >
> > On Mon, 03/15/2010 at 1:28am, "Craig J. Anderson" <ander882@...> wrote:
> >
> >> I am currently working on the Graphical Ancestor and Descendant reports.  I
> >> have updated them and along with it, I have also updated the Substitution
> >> Values that can used:
> >> The old:  http://www.gramps-project.org/wiki/index.php?title=Gramps_3.
> >> 2_Wiki_Manual_-_Reports_-_part_2
> >> Proposed:http://ander882.110mb.com/index.php?p=gramps.display
> >> I have removed the % variables and added {} groupings to remove parts that
> >> are not wanted.
> >> Example:  'Was born {on $b }{at $B' will print 'Was born at over there' if
> >> the date is not known and 'Was born on 2010-0101 ' if the place is not know.
> >>  If neither is known, 'Was born ' will print.
> >> So please take a look and tell me what you think/like/dislike.
> >> And for those that read through to the end, there is a design question at
> >> the bottom.
> >> thanks.
> >>   Craig A.
> >
> >> ----------
> >> Hotmail is redefining busy with tools for the New Busy. Get more from your
> >> inbox.
> >> Sign up now.
> >
> > Powered by the 6zap. Sign up at http://www.6zap.com for an account that provides advanced e-mail, calendar and contacts capabilities.
> >
> > ------------------------------------------------------------------------------
> > Download Intel&#174; Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > _______________________________________________
> > Gramps-devel mailing list
> > Gramps-devel@...
> > https://lists.sourceforge.net/lists/listinfo/gramps-devel
> >
 		 	   		  
_________________________________________________________________
Hotmail is redefining busy with tools for the New Busy. Get more from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID27925::T:WLMTAGL:ON:WL:en-US:WM_HMP:032010_2

Yes, I like it as well.

Benny's suggestions are a good answer to your design question.

How difficult would it be to add substitution variables to handle 
attributes?  For example:

Occupation:  $[Occupation]

if the person has an attribute called "Occupation" containing the 
occupation.

Nick.

Benny Malengier wrote:
> 2010/3/15 lcc <lcc@...>:
>   
>> I like it. I'm not sure why you need extra semantics in your final question. Isn't it
>> already covered?
>>
>> {and married to $s}
>>     
>
> Yes, it looks nice.
> I suppose your design question comes from wanting to avoid nesting of groups?
> If you define the syntax as:
>
> A { can contain one of the following
>  *  one or more variables with $
>  *  one or more groups.
> The entire group with { will be printed if one of the $ variables
> inside of it contains information.
>
> With this definition, you can build up a structure in the code, and
> give a warning to user when he created a wrong substition text.
>
> Then you will end up with a structure of eg
> top
>  - var
>  - group
>      -var
>  - group
>      - group
>         - var
>      - group
>         - var
>         - var
>
> If you do not want to make groups in groups, then use the - at the
> start of the line to avoid confusion with the use of { for groups.
>
> Benny
>
>   
>> --lcc
>>
>> On Mon, 03/15/2010 at 1:28am, "Craig J. Anderson" <ander882@...> wrote:
>>
>>     
>>> I am currently working on the Graphical Ancestor and Descendant reports.  I
>>> have updated them and along with it, I have also updated the Substitution
>>> Values that can used:
>>> The old:  http://www.gramps-project.org/wiki/index.php?title=Gramps_3.
>>> 2_Wiki_Manual_-_Reports_-_part_2
>>> Proposed:http://ander882.110mb.com/index.php?p=gramps.display
>>> I have removed the % variables and added {} groupings to remove parts that
>>> are not wanted.
>>> Example:  'Was born {on $b }{at $B' will print 'Was born at over there' if
>>> the date is not known and 'Was born on 2010-0101 ' if the place is not know.
>>>  If neither is known, 'Was born ' will print.
>>> So please take a look and tell me what you think/like/dislike.
>>> And for those that read through to the end, there is a design question at
>>> the bottom.
>>> thanks.
>>>   Craig A.
>>>       
>>> ----------
>>> Hotmail is redefining busy with tools for the New Busy. Get more from your
>>> inbox.
>>> Sign up now.
>>>       
>> Powered by the 6zap. Sign up at http://www.6zap.com for an account that provides advanced e-mail, calendar and contacts capabilities.
>>
>> ------------------------------------------------------------------------------
>> Download Intel&#174; Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Gramps-devel mailing list
>> Gramps-devel@...
>> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>>
>>     
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Gramps-devel mailing list
> Gramps-devel@...
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>

Not an entire line.  a { at the start of a line could mean a blank line or remove the line.  since the { is for removing text.  I decided it would be for making a blank line (removing all text).  That is why I needed another semantic '-'.  

But I can make it remove the line and if a person wants a blank line, start the line with ' {'

Which do you prefer?
1. using '-' at the start to remove a line
2. using '{' at the start to remove a line (if all variables are blank)
2a. using ' {' at the start to have a blank line

----

Ok, I have not heard of attributes so far.  Ok, I see that these are key/value pairs.  This would be easy to add.  The only question I have is:  There is an option to replace missing information with '' or '_____'.  Would that rule apply to attributes also?

thanks.

  Craig A.

> Date: Mon, 15 Mar 2010 15:24:48 +0000
> From: nick__hall@...
> To: benny.malengier@...
> CC: ander882@...; gramps-devel@...
> Subject: Re: [Gramps-devel] Substitution Values updates for your review.
> 
> Yes, I like it as well.
> 
> Benny's suggestions are a good answer to your design question.
> 
> How difficult would it be to add substitution variables to handle 
> attributes?  For example:
> 
> Occupation:  $[Occupation]
> 
> if the person has an attribute called "Occupation" containing the 
> occupation.
> 
> Nick.
> 
> Benny Malengier wrote:
> > 2010/3/15 lcc <lcc@...>:
> >   
> >> I like it. I'm not sure why you need extra semantics in your final question. Isn't it
> >> already covered?
> >>
> >> {and married to $s}
> >>     
> >
> > Yes, it looks nice.
> > I suppose your design question comes from wanting to avoid nesting of groups?
> > If you define the syntax as:
> >
> > A { can contain one of the following
> >  *  one or more variables with $
> >  *  one or more groups.
> > The entire group with { will be printed if one of the $ variables
> > inside of it contains information.
> >
> > With this definition, you can build up a structure in the code, and
> > give a warning to user when he created a wrong substition text.
> >
> > Then you will end up with a structure of eg
> > top
> >  - var
> >  - group
> >      -var
> >  - group
> >      - group
> >         - var
> >      - group
> >         - var
> >         - var
> >
> > If you do not want to make groups in groups, then use the - at the
> > start of the line to avoid confusion with the use of { for groups.
> >
> > Benny
> >
> >   
> >> --lcc
> >>
> >> On Mon, 03/15/2010 at 1:28am, "Craig J. Anderson" <ander882@...> wrote:
> >>
> >>     
> >>> I am currently working on the Graphical Ancestor and Descendant reports.  I
> >>> have updated them and along with it, I have also updated the Substitution
> >>> Values that can used:
> >>> The old:  http://www.gramps-project.org/wiki/index.php?title=Gramps_3.
> >>> 2_Wiki_Manual_-_Reports_-_part_2
> >>> Proposed:http://ander882.110mb.com/index.php?p=gramps.display
> >>> I have removed the % variables and added {} groupings to remove parts that
> >>> are not wanted.
> >>> Example:  'Was born {on $b }{at $B' will print 'Was born at over there' if
> >>> the date is not known and 'Was born on 2010-0101 ' if the place is not know.
> >>>  If neither is known, 'Was born ' will print.
> >>> So please take a look and tell me what you think/like/dislike.
> >>> And for those that read through to the end, there is a design question at
> >>> the bottom.
> >>> thanks.
> >>>   Craig A.
> >>>       
> >>> ----------
> >>> Hotmail is redefining busy with tools for the New Busy. Get more from your
> >>> inbox.
> >>> Sign up now.
> >>>       
> >> Powered by the 6zap. Sign up at http://www.6zap.com for an account that provides advanced e-mail, calendar and contacts capabilities.
> >>
> >> ------------------------------------------------------------------------------
> >> Download Intel&#174; Parallel Studio Eval
> >> Try the new software tools for yourself. Speed compiling, find bugs
> >> proactively, and fine-tune applications for parallel performance.
> >> See why Intel Parallel Studio got high marks during beta.
> >> http://p.sf.net/sfu/intel-sw-dev
> >> _______________________________________________
> >> Gramps-devel mailing list
> >> Gramps-devel@...
> >> https://lists.sourceforge.net/lists/listinfo/gramps-devel
> >>
> >>     
> >
> > ------------------------------------------------------------------------------
> > Download Intel&#174; Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > _______________________________________________
> > Gramps-devel mailing list
> > Gramps-devel@...
> > https://lists.sourceforge.net/lists/listinfo/gramps-devel
> >   
 		 	   		  
_________________________________________________________________
Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID27925::T:WLMTAGL:ON:WL:en-US:WM_HMP:032010_1

Craig J. Anderson wrote:
> Not an entire line.  a { at the start of a line could mean a blank 
> line or remove the line.  since the { is for removing text.  I decided 
> it would be for making a blank line (removing all text).  That is why 
> I needed another semantic '-'. 
>
> But I can make it remove the line and if a person wants a blank line, 
> start the line with ' {'
>
> Which do you prefer?
> 1. using '-' at the start to remove a line
> 2. using '{' at the start to remove a line (if all variables are blank)
> 2a. using ' {' at the start to have a blank line
>
> ----
>
> Ok, I have not heard of attributes so far.  Ok, I see that these are 
> key/value pairs.  This would be easy to add.  The only question I have 
> is:  There is an option to replace missing information with '' or 
> '_____'.  Would that rule apply to attributes also?
>

I don't use the functionality for missing information.

I was thing of the substitution variables for the graphical ancestor and 
descendant reoprts - it would be nice to include more information in the 
box.

> thanks.
>
>   Craig A.
>
> > Date: Mon, 15 Mar 2010 15:24:48 +0000
> > From: nick__hall@...
> > To: benny.malengier@...
> > CC: ander882@...; gramps-devel@...
> > Subject: Re: [Gramps-devel] Substitution Values updates for your review.
> >
> > Yes, I like it as well.
> >
> > Benny's suggestions are a good answer to your design question.
> >
> > How difficult would it be to add substitution variables to handle
> > attributes? For example:
> >
> > Occupation: $[Occupation]
> >
> > if the person has an attribute called "Occupation" containing the
> > occupation.
> >
> > Nick.
> >
> > Benny Malengier wrote:
> > > 2010/3/15 lcc <lcc@...>:
> > >
> > >> I like it. I'm not sure why you need extra semantics in your 
> final question. Isn't it
> > >> already covered?
> > >>
> > >> {and married to $s}
> > >>
> > >
> > > Yes, it looks nice.
> > > I suppose your design question comes from wanting to avoid nesting 
> of groups?
> > > If you define the syntax as:
> > >
> > > A { can contain one of the following
> > > * one or more variables with $
> > > * one or more groups.
> > > The entire group with { will be printed if one of the $ variables
> > > inside of it contains information.
> > >
> > > With this definition, you can build up a structure in the code, and
> > > give a warning to user when he created a wrong substition text.
> > >
> > > Then you will end up with a structure of eg
> > > top
> > > - var
> > > - group
> > > -var
> > > - group
> > > - group
> > > - var
> > > - group
> > > - var
> > > - var
> > >
> > > If you do not want to make groups in groups, then use the - at the
> > > start of the line to avoid confusion with the use of { for groups.
> > >
> > > Benny
> > >
> > >
> > >> --lcc
> > >>
> > >> On Mon, 03/15/2010 at 1:28am, "Craig J. Anderson" 
> <ander882@...> wrote:
> > >>
> > >>
> > >>> I am currently working on the Graphical Ancestor and Descendant 
> reports. I
> > >>> have updated them and along with it, I have also updated the 
> Substitution
> > >>> Values that can used:
> > >>> The old: 
> http://www.gramps-project.org/wiki/index.php?title=Gramps_3.
> > >>> 2_Wiki_Manual_-_Reports_-_part_2
> > >>> Proposed:http://ander882.110mb.com/index.php?p=gramps.display
> > >>> I have removed the % variables and added {} groupings to remove 
> parts that
> > >>> are not wanted.
> > >>> Example: 'Was born {on $b }{at $B' will print 'Was born at over 
> there' if
> > >>> the date is not known and 'Was born on 2010-0101 ' if the place 
> is not know.
> > >>> If neither is known, 'Was born ' will print.
> > >>> So please take a look and tell me what you think/like/dislike.
> > >>> And for those that read through to the end, there is a design 
> question at
> > >>> the bottom.
> > >>> thanks.
> > >>> Craig A.
> > >>>
> > >>> ----------
> > >>> Hotmail is redefining busy with tools for the New Busy. Get more 
> from your
> > >>> inbox.
> > >>> Sign up now.
> > >>>
> > >> Powered by the 6zap. Sign up at http://www.6zap.com for an 
> account that provides advanced e-mail, calendar and contacts capabilities.
> > >>
> > >> 
> ------------------------------------------------------------------------------
> > >> Download Intel&#174; Parallel Studio Eval
> > >> Try the new software tools for yourself. Speed compiling, find bugs
> > >> proactively, and fine-tune applications for parallel performance.
> > >> See why Intel Parallel Studio got high marks during beta.
> > >> http://p.sf.net/sfu/intel-sw-dev
> > >> _______________________________________________
> > >> Gramps-devel mailing list
> > >> Gramps-devel@...
> > >> https://lists.sourceforge.net/lists/listinfo/gramps-devel
> > >>
> > >>
> > >
> > > 
> ------------------------------------------------------------------------------
> > > Download Intel&#174; Parallel Studio Eval
> > > Try the new software tools for yourself. Speed compiling, find bugs
> > > proactively, and fine-tune applications for parallel performance.
> > > See why Intel Parallel Studio got high marks during beta.
> > > http://p.sf.net/sfu/intel-sw-dev
> > > _______________________________________________
> > > Gramps-devel mailing list
> > > Gramps-devel@...
> > > https://lists.sourceforge.net/lists/listinfo/gramps-devel
> > >
>
> ------------------------------------------------------------------------
> Hotmail has tools for the New Busy. Search, chat and e-mail from your 
> inbox. Learn More. 
> <http://www.windowslive.com/campaign/thenewbusy?ocid=PID27925::T:WLMTAGL:ON:WL:en-US:WM_HMP:032010_1>

2010/3/15 Craig J. Anderson <ander882@...>:
> Not an entire line.  a { at the start of a line could mean a blank line or
> remove the line.  since the { is for removing text.  I decided it would be
> for making a blank line (removing all text).  That is why I needed another
> semantic '-'.
>
> But I can make it remove the line and if a person wants a blank line, start
> the line with ' {'
>
> Which do you prefer?
> 1. using '-' at the start to remove a line
> 2. using '{' at the start to remove a line (if all variables are blank)
> 2a. using ' {' at the start to have a blank line

2a seems the most logical thing concerning the way to handle it in my
mind. Only one syntax element to remember, the {.
It should simplify code also I would think (eg - would require a -- too).

I am not a big fan of your lazy bracketing (not needing to close
brackets), but that is probably because I teach mathematics :-)
I would drop the {{ means to write a {, as that would make nesting
more difficult (you would add spaces to the text that are perhaps not
needed, no>). Just don't allow { or } in text, why would people need
that anyway? Otherwise you can do it as tex does: \{ is the real
bracket, so \ as an escaping symbol, \\ meaning \, \{ meaning { and \$
meaning a literal $, instead of the doubles.

Benny

> ----
>
> Ok, I have not heard of attributes so far.  Ok, I see that these are
> key/value pairs.  This would be easy to add.  The only question I have is:
> There is an option to replace missing information with '' or '_____'.  Would
> that rule apply to attributes also?
>
> thanks.
>
>   Craig A.
>
>> Date: Mon, 15 Mar 2010 15:24:48 +0000
>> From: nick__hall@...
>> To: benny.malengier@...
>> CC: ander882@...; gramps-devel@...
>> Subject: Re: [Gramps-devel] Substitution Values updates for your review.
>>
>> Yes, I like it as well.
>>
>> Benny's suggestions are a good answer to your design question.
>>
>> How difficult would it be to add substitution variables to handle
>> attributes? For example:
>>
>> Occupation: $[Occupation]
>>
>> if the person has an attribute called "Occupation" containing the
>> occupation.
>>
>> Nick.
>>
>> Benny Malengier wrote:
>> > 2010/3/15 lcc <lcc@...>:
>> >
>> >> I like it. I'm not sure why you need extra semantics in your final
>> >> question. Isn't it
>> >> already covered?
>> >>
>> >> {and married to $s}
>> >>
>> >
>> > Yes, it looks nice.
>> > I suppose your design question comes from wanting to avoid nesting of
>> > groups?
>> > If you define the syntax as:
>> >
>> > A { can contain one of the following
>> > * one or more variables with $
>> > * one or more groups.
>> > The entire group with { will be printed if one of the $ variables
>> > inside of it contains information.
>> >
>> > With this definition, you can build up a structure in the code, and
>> > give a warning to user when he created a wrong substition text.
>> >
>> > Then you will end up with a structure of eg
>> > top
>> > - var
>> > - group
>> > -var
>> > - group
>> > - group
>> > - var
>> > - group
>> > - var
>> > - var
>> >
>> > If you do not want to make groups in groups, then use the - at the
>> > start of the line to avoid confusion with the use of { for groups.
>> >
>> > Benny
>> >
>> >
>> >> --lcc
>> >>
>> >> On Mon, 03/15/2010 at 1:28am, "Craig J. Anderson"
>> >> <ander882@...> wrote:
>> >>
>> >>
>> >>> I am currently working on the Graphical Ancestor and Descendant
>> >>> reports. I
>> >>> have updated them and along with it, I have also updated the
>> >>> Substitution
>> >>> Values that can used:
>> >>> The old: http://www.gramps-project.org/wiki/index.php?title=Gramps_3.
>> >>> 2_Wiki_Manual_-_Reports_-_part_2
>> >>> Proposed:http://ander882.110mb.com/index.php?p=gramps.display
>> >>> I have removed the % variables and added {} groupings to remove parts
>> >>> that
>> >>> are not wanted.
>> >>> Example: 'Was born {on $b }{at $B' will print 'Was born at over there'
>> >>> if
>> >>> the date is not known and 'Was born on 2010-0101 ' if the place is not
>> >>> know.
>> >>> If neither is known, 'Was born ' will print.
>> >>> So please take a look and tell me what you think/like/dislike.
>> >>> And for those that read through to the end, there is a design question
>> >>> at
>> >>> the bottom.
>> >>> thanks.
>> >>> Craig A.
>> >>>
>> >>> ----------
>> >>> Hotmail is redefining busy with tools for the New Busy. Get more from
>> >>> your
>> >>> inbox.
>> >>> Sign up now.
>> >>>
>> >> Powered by the 6zap. Sign up at http://www.6zap.com for an account that
>> >> provides advanced e-mail, calendar and contacts capabilities.
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> Download Intel&#174; Parallel Studio Eval
>> >> Try the new software tools for yourself. Speed compiling, find bugs
>> >> proactively, and fine-tune applications for parallel performance.
>> >> See why Intel Parallel Studio got high marks during beta.
>> >> http://p.sf.net/sfu/intel-sw-dev
>> >> _______________________________________________
>> >> Gramps-devel mailing list
>> >> Gramps-devel@...
>> >> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>> >>
>> >>
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Download Intel&#174; Parallel Studio Eval
>> > Try the new software tools for yourself. Speed compiling, find bugs
>> > proactively, and fine-tune applications for parallel performance.
>> > See why Intel Parallel Studio got high marks during beta.
>> > http://p.sf.net/sfu/intel-sw-dev
>> > _______________________________________________
>> > Gramps-devel mailing list
>> > Gramps-devel@...
>> > https://lists.sourceforge.net/lists/listinfo/gramps-devel
>> >
>
> ________________________________
> Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox.
> Learn More.

Nick:
Which do you prefer?
1. using '-' at the start to remove a line
2. using '{' at the start to remove a line (if all variables are blank)
2a. using ' {' at the start to have a blank line

> Date: Mon, 15 Mar 2010 16:34:09 +0000
> From: nick__hall@...
> To: ander882@...
> CC: benny.malengier@...; gramps-devel@...
> Subject: Re: [Gramps-devel] Substitution Values updates for your review.
> 
> > > How difficult would it be to add substitution variables to handle
> > > attributes? For example:
> > >
> > > Occupation: $[Occupation]
> > >
> > > if the person has an attribute called "Occupation" containing the
> > > occupation.

I can do that and think it would be a good addition.

> I was thing of the substitution variables for the graphical ancestor and 
> descendant reports - it would be nice to include more information in the 
> box.
> > > Nick.

great.  care to share what you would like?

  Craig A.

 		 	   		  
_________________________________________________________________
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
http://clk.atdmt.com/GBL/go/210850552/direct/01/

2010/3/15 Craig J. Anderson <ander882@...>:
> Nick:
> Which do you prefer?
> 1. using '-' at the start to remove a line
> 2. using '{' at the start to remove a line (if all variables are blank)
> 2a. using ' {' at the start to have a blank line
>
>> Date: Mon, 15 Mar 2010 16:34:09 +0000
>> From: nick__hall@...
>> To: ander882@...
>> CC: benny.malengier@...; gramps-devel@...
>> Subject: Re: [Gramps-devel] Substitution Values updates for your review.
>>
>> > > How difficult would it be to add substitution variables to handle
>> > > attributes? For example:
>> > >
>> > > Occupation: $[Occupation]
>> > >
>> > > if the person has an attribute called "Occupation" containing the
>> > > occupation.
>
> I can do that and think it would be a good addition.

Hey, but I use the occupation as an event !!! :-D
Kidding aside, was this not one of the weak points: occupation as
attribute or as event. Don't we have it predefined for both at the
moment?
Gedcom is also strange in this respect

Benny
>
>> I was thing of the substitution variables for the graphical ancestor and
>> descendant reports - it would be nice to include more information in the
>> box.
>> > > Nick.
>
> great.  care to share what you would like?
>
>   Craig A.
>
>
> ________________________________
> Hotmail: Trusted email with Microsoft’s powerful SPAM protection. Sign up
> now.

This may still be useful as my father used attributes for lots of things.  Ethnicity, religion are a couple.  But then again, it might be too much.  I'll let everyone help me decide.  :)

  Craig A.

> Date: Mon, 15 Mar 2010 21:15:02 +0100
> Subject: Re: [Gramps-devel] Substitution Values updates for your review.
> From: benny.malengier@...
> To: ander882@...
> CC: nick__hall@...; gramps-devel@...
> 
> 2010/3/15 Craig J. Anderson <ander882@...>:
> > Nick:
> > Which do you prefer?
> > 1. using '-' at the start to remove a line
> > 2. using '{' at the start to remove a line (if all variables are blank)
> > 2a. using ' {' at the start to have a blank line
> >
> >> Date: Mon, 15 Mar 2010 16:34:09 +0000
> >> From: nick__hall@...
> >> To: ander882@...
> >> CC: benny.malengier@...; gramps-devel@...
> >> Subject: Re: [Gramps-devel] Substitution Values updates for your review.
> >>
> >> > > How difficult would it be to add substitution variables to handle
> >> > > attributes? For example:
> >> > >
> >> > > Occupation: $[Occupation]
> >> > >
> >> > > if the person has an attribute called "Occupation" containing the
> >> > > occupation.
> >
> > I can do that and think it would be a good addition.
> 
> Hey, but I use the occupation as an event !!! :-D

Hmm.  Full contact programming?  

> Kidding aside, was this not one of the weak points: occupation as
> attribute or as event. Don't we have it predefined for both at the
> moment?
> Gedcom is also strange in this respect
> 
> Benny
> >
> >> I was thing of the substitution variables for the graphical ancestor and
> >> descendant reports - it would be nice to include more information in the
> >> box.
> >> > > Nick.
> >
> > great.  care to share what you would like?
> >
> >   Craig A.
> >
> >
> > ________________________________
> > Hotmail: Trusted email with Microsoft’s powerful SPAM protection. Sign up
> > now.
 		 	   		  
_________________________________________________________________
The New Busy is not the old busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID27925::T:WLMTAGL:ON:WL:en-US:WM_HMP:032010_3

Very good in my opinion. Furthermore, I think this concept could also be applied to
the (Indented List) Descendant Report! Occupation and other attributes. It took me
some time to comprehend attributes but they're very good design imo. By the way, there
are some things in the standard event list that should probably be attributes as the first
message linked below states.

To Gramps attributes in general:
http://old.nabble.com/Events---Attributes%2C-and-column-widths.-td5991633.html
http://old.nabble.com/Proposal-for-a-GEDCOM-change-td24312547.html

Regards, --lcc

On Mon, 03/15/2010 at 5:21pm, "Craig J. Anderson" <ander882@...> wrote:

> This may still be useful as my father used attributes for lots of things.  
> Ethnicity, religion are a couple.  But then again, it might be too much.  I'
> ll let everyone help me decide.  :)
>   Craig A.
>> Date: Mon, 15 Mar 2010 21:15:02 +0100
>> Subject: Re: [Gramps-devel] Substitution Values updates for your review.
>> From: benny.malengier@...
>> To: ander882@...
>> CC: nick__hall@...; gramps-devel@...

>> 2010/3/15 Craig J. Anderson :
>>> Nick:
>>> Which do you prefer?
>>> 1. using '-' at the start to remove a line
>>> 2. using '{' at the start to remove a line (if all variables are blank)
>>> 2a. using ' {' at the start to have a blank line

>>>> Date: Mon, 15 Mar 2010 16:34:09 +0000
>>>> From: nick__hall@...
>>>> To: ander882@...
>>>> CC: benny.malengier@...; gramps-devel@...
>>>> Subject: Re: [Gramps-devel] Substitution Values updates for your review.

>>>>>> How difficult would it be to add substitution variables to handle
>>>>>> attributes? For example:

>>>>>> Occupation: $[Occupation]

>>>>>> if the person has an attribute called "Occupation" containing the
>>>>>> occupation.

>>> I can do that and think it would be a good addition.

>> Hey, but I use the occupation as an event !!! :-D
> Hmm.  Full contact programming?  
>> Kidding aside, was this not one of the weak points: occupation as
>> attribute or as event. Don't we have it predefined for both at the
>> moment?
>> Gedcom is also strange in this respect

>> Benny

>>>> I was thing of the substitution variables for the graphical ancestor and
>>>> descendant reports - it would be nice to include more information in the
>>>> box.
>>>>>> Nick.

>>> great.  care to share what you would like?

>>>   Craig A.

>>> ________________________________
>>> Hotmail: Trusted email with Microsoft’s powerful SPAM protection. Sign up
>>> now.

> ----------
> The New Busy is not the old busy. Search, chat and e-mail from your inbox. 
> Get started.

Powered by the 6zap. Sign up at http://www.6zap.com for an account that provides advanced e-mail, calendar and contacts capabilities.

I use events for occupation as well.  If I have evidence of employment I 
will create an event.  If I have evidence of the ownership of a shop 
then I will create an event - a property event in this case.

It can still be useful to summarise an occupation or profession as an 
attribute.

Nick.


Benny Malengier wrote:
> 2010/3/15 Craig J. Anderson <ander882@...>:
>   
>> Nick:
>> Which do you prefer?
>> 1. using '-' at the start to remove a line
>> 2. using '{' at the start to remove a line (if all variables are blank)
>> 2a. using ' {' at the start to have a blank line
>>
>>     
>>> Date: Mon, 15 Mar 2010 16:34:09 +0000
>>> From: nick__hall@...
>>> To: ander882@...
>>> CC: benny.malengier@...; gramps-devel@...
>>> Subject: Re: [Gramps-devel] Substitution Values updates for your review.
>>>
>>>       
>>>>> How difficult would it be to add substitution variables to handle
>>>>> attributes? For example:
>>>>>
>>>>> Occupation: $[Occupation]
>>>>>
>>>>> if the person has an attribute called "Occupation" containing the
>>>>> occupation.
>>>>>           
>> I can do that and think it would be a good addition.
>>     
>
> Hey, but I use the occupation as an event !!! :-D
> Kidding aside, was this not one of the weak points: occupation as
> attribute or as event. Don't we have it predefined for both at the
> moment?
> Gedcom is also strange in this respect
>
> Benny
>   
>>> I was thing of the substitution variables for the graphical ancestor and
>>> descendant reports - it would be nice to include more information in the
>>> box.
>>>       
>>>>> Nick.
>>>>>           
>> great.  care to share what you would like?
>>
>>   Craig A.
>>
>>
>> ________________________________
>> Hotmail: Trusted email with Microsoft’s powerful SPAM protection. Sign up
>> now.
>>     
>
>
>

2010/3/15 Benny Malengier <benny.malengier@...>

>
> Hey, but I use the occupation as an event !!! :-D
> Kidding aside, was this not one of the weak points: occupation as
> attribute or as event. Don't we have it predefined for both at the
> moment?
> Gedcom is also strange in this respect
>

I think Gedcom has it right here, it is Gramps not believing that dates and
places pertain to attributes that creates the confusion.  From Gedcom 5.5:

Some attributes of individuals such as their EDUCation, OCCUpation,
RESIdence, or nobilityTITLe need to be described using a date and place.
Therefore, the structure to describe the attributes was formatted to be the
same as for describing events. That is, these attributes are further defined
using a date, place, and other values used to describe events.

Since Gramps only wants dates in events, these things have to be coerced
into events.  Then people complaint that they are not "events".  Of course
they aren't.  They're attributes.

The following paragraph from the never approved 5.5.1 makes this much
clearer:

As a general rule, events are things that happen on a specific date. Use the
date form ‘BET date
AND date’ to indicate that an event took place at some time between two
dates. Resist the
temptation to use a ‘FROM date TO date’ form in an event structure. If the
subject of your
recording occurred over a period of time, then it is probably not an event,
but rather an attribute or
fact.

I cannot agree more with the above.

Julio

Well,

If we were to decide that attributes should have a place and a date, that wouldn't
conflict with the current implementation. Gramps should only assume attributes
from older versions have an empty place and date.

--lcc

On Wed, 03/17/2010 at 3:44pm, "Benny Malengier" <benny.malengier@...> wrote:
> 2010/3/17 Julio Sánchez <julio.sanchez@...>:

>> 2010/3/15 Benny Malengier <benny.malengier@...>

>>> Hey, but I use the occupation as an event !!! :-D
>>> Kidding aside, was this not one of the weak points: occupation as
>>> attribute or as event. Don't we have it predefined for both at the
>>> moment?
>>> Gedcom is also strange in this respect

>> I think Gedcom has it right here, it is Gramps not believing that dates and
>> places pertain to attributes that creates the confusion.  From Gedcom 5.5:

>> Some attributes of individuals such as their EDUCation, OCCUpation,
>> RESIdence, or nobilityTITLe need to be described using a date and place.
>> Therefore, the structure to describe the attributes was formatted to be the
>> same as for describing events. That is, these attributes are further defined
>> using a date, place, and other values used to describe events.

>> Since Gramps only wants dates in events, these things have to be coerced
>> into events.  Then people complaint that they are not "events".  Of course
>> they aren't.  They're attributes.

>> The following paragraph from the never approved 5.5.1 makes this much
>> clearer:

>> As a general rule, events are things that happen on a specific date. Use the
>> date form ‘BET date
>> AND date’ to indicate that an event took place at some time between two
>> dates. Resist the
>> temptation to use a ‘FROM date TO date’ form in an event structure. If the
>> subject of your
>> recording occurred over a period of time, then it is probably not an event,
>> but rather an attribute or
>> fact.

>> I cannot agree more with the above.

> I agree somewhat too, but is it worthwile in Gramps to add place/date
> to attributes as a non-shared object, like event was before they
> became sharable objects?
> In other words, in the past some design decisions where made, and now
> we are stuck with them. How do we move forward with this issue that
> keeps coming back? Do we aim at making attributes like events, or do
> we aim at making attributes like non-sharable events (so nothing like
> eventref), or is there another way to migrate to something different?
> And if we change, will users not find it strange that something like
> 'eye color' can have a date and place?

> Benny

>> Julio

> -----------------------------------------------------------------------------
> -
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Gramps-devel mailing list
> Gramps-devel@...
> https://lists.sourceforge.net/lists/listinfo/gramps-devel


Powered by the 6zap. Sign up at http://www.6zap.com for an account that provides advanced e-mail, calendar and contacts capabilities.