tablesmith@groups.io

Re: Producing serial lists of varying length

That's a great way of doing it. I was trying to think of another, but
that's probably the most elegant way at the moment (I thought about trying
to put together a "user-defined function" in a table using a Dataset, but
I'm on my Mac w/o easy access to a copy of TS).

This (or something similar but more generic) might be a good candidate for
a new function in 5.2.


On Tue, Jun 18, 2013 at 9:23 PM, Sablesword <Sablesword@...> wrote:

**


Thanks for the suggestions.

What I ended up doing was to put the optional features into a single
variable, keeping track of the number of optional features used and then
trimming and adding an "and" as appropriate at the end.

# Harem slavegirl facial features
# (work in progress, features still to be refined)
;sgFace
# %NoF% starts at max possible number of optional facial features
1,|NoF=4|[sgFace_shape] with
_|FFeatures=[sgForehead][sgCheekbones][sgNose][sgLips]|
_{If~%NoF%=1?{Left~{Calc~{Length~%FFeatures%}-1},%FFeatures%} and}
_{If~%NoF%>1? %FFeatures% and} [sgEyes] eyes.

[...]

;sgNose
# Reduce %NoF% by 1 each time nothing selected
10,|NoF-1|
1, an aquiline nose,
1, a small, upturned nose,
1, a sharp nose,
1, a broad nose,

... and the other optional-facial-features groups done likewise.

--- In TableSmith@..., "kuseru" <kuseru@...> wrote:

Set all the options as variables, then use If statements to show thosevariables if they come up. I.e.
%n%,0
%l%,0
%e%,0
%nose%,normal
%lips%,normal
%ears%,normal


### somewhere in table for determination

:Nose
1,|n=1||nose=small|
2,
#normal (you should of course leave an option blank (in whatever amountyou desire for "normal" body parts, this is only a location note)
3,|n=1||nose=large|
4,|n=1||nose=bulbous|

:Lips
1,|l=1||lips=small|
2,
#normal
3,|l=1||lips=large|

:Ears
1,|e=1||ears=small|
2,
#normal
3,|e=1||ears=large|


#### wherever your output line is
{If~%e%=1?%ears%, /}{If~%l%=1?%lips%, /}{If~%n%=1?%nose%, /} and [Eyes]
# Note 1: You don't have to make the eyes a variable since you alwayswant them to show up.
# Note 2: You can arrange the output text for additional items any wayyou want beyond just the size or shape descriptor you choose, i.e. "a
%nose% nose, ".
# Note 3: Note the inclusion of a space after the variable (or textualformat you choose), but not between If statements, this makes the output
workable by placing spaces where needed.

--- In TableSmith@..., "Sablesword" <ErolB1@> wrote:

What's the cleanest, most elegant way to set up a group or set ofgroups that outputs a serial list of varying length, so as to properly
include the optional commas and final optional "and"?

E.g. "... with x, y, z, and aa." where the "aa" is always present, butthe x, y, and z are all optional, so that the output will sometimes have
two or more of the optional elements ("with x, y, and aa") sometimes just
one of the optional elements ("with z and aa" - no comma) and sometimes
with none of the optional elements ("with aa" - no "and").

Is the most elegant answer to first determine how many optional itemsare in the list, and then run a group with the three cases (zero optional
item, one optional item, two or more optional items)? Is it to keep track
of how many optional items are generated and to toggle the commas and the
final "and" based on this? Is there another, better answer?

In particular, I'm trying to set up a "face description" table, wherethe eyes are always described at the end, but the various other facial
features are only described if they're unusual in some way: Nose mentioned
if it's big, small, or otherwise special, but not if it's average; mouth
mentioned if it's generous, or thin and bloodless, or permenantly frowning,
or otherwise odd, but not if it's normal; a scar mentioned if it's present,
but not otherwise; and so on.


[Non-text portions of this message have been removed]

Re: Producing serial lists of varying length

Sablesword

#7840

Thanks for the suggestions.

What I ended up doing was to put the optional features into a single variable, keeping track of the number of optional features used and then trimming and adding an "and" as appropriate at the end.

# Harem slavegirl facial features
# (work in progress, features still to be refined)
;sgFace
# %NoF% starts at max possible number of optional facial features
1,|NoF=4|[sgFace_shape] with
_|FFeatures=[sgForehead][sgCheekbones][sgNose][sgLips]|
_{If~%NoF%=1?{Left~{Calc~{Length~%FFeatures%}-1},%FFeatures%} and}
_{If~%NoF%>1? %FFeatures% and} [sgEyes] eyes.

[...]

;sgNose
# Reduce %NoF% by 1 each time nothing selected
10,|NoF-1|
1, an aquiline nose,
1, a small, upturned nose,
1, a sharp nose,
1, a broad nose,

... and the other optional-facial-features groups done likewise.

Show quoted text

--- In TableSmith@..., "kuseru" <kuseru@...> wrote:

Set all the options as variables, then use If statements to show those variables if they come up. I.e.
%n%,0
%l%,0
%e%,0
%nose%,normal
%lips%,normal
%ears%,normal


### somewhere in table for determination

:Nose
1,|n=1||nose=small|
2,
#normal (you should of course leave an option blank (in whatever amount you desire for "normal" body parts, this is only a location note)
3,|n=1||nose=large|
4,|n=1||nose=bulbous|

:Lips
1,|l=1||lips=small|
2,
#normal
3,|l=1||lips=large|

:Ears
1,|e=1||ears=small|
2,
#normal
3,|e=1||ears=large|


#### wherever your output line is
{If~%e%=1?%ears%, /}{If~%l%=1?%lips%, /}{If~%n%=1?%nose%, /} and [Eyes]
# Note 1: You don't have to make the eyes a variable since you always want them to show up.
# Note 2: You can arrange the output text for additional items any way you want beyond just the size or shape descriptor you choose, i.e. "a %nose% nose, ".
# Note 3: Note the inclusion of a space after the variable (or textual format you choose), but not between If statements, this makes the output workable by placing spaces where needed.

--- In TableSmith@..., "Sablesword" <ErolB1@> wrote:

What's the cleanest, most elegant way to set up a group or set of groups that outputs a serial list of varying length, so as to properly include the optional commas and final optional "and"?

E.g. "... with x, y, z, and aa." where the "aa" is always present, but the x, y, and z are all optional, so that the output will sometimes have two or more of the optional elements ("with x, y, and aa") sometimes just one of the optional elements ("with z and aa" - no comma) and sometimes with none of the optional elements ("with aa" - no "and").

Is the most elegant answer to first determine how many optional items are in the list, and then run a group with the three cases (zero optional item, one optional item, two or more optional items)? Is it to keep track of how many optional items are generated and to toggle the commas and the final "and" based on this? Is there another, better answer?

In particular, I'm trying to set up a "face description" table, where the eyes are always described at the end, but the various other facial features are only described if they're unusual in some way: Nose mentioned if it's big, small, or otherwise special, but not if it's average; mouth mentioned if it's generous, or thin and bloodless, or permenantly frowning, or otherwise odd, but not if it's normal; a scar mentioned if it's present, but not otherwise; and so on.

Re: Producing serial lists of varying length

#7839

Set all the options as variables, then use If statements to show those variables if they come up. I.e.
%n%,0
%l%,0
%e%,0
%nose%,normal
%lips%,normal
%ears%,normal


### somewhere in table for determination

:Nose
1,|n=1||nose=small|
2,
#normal (you should of course leave an option blank (in whatever amount you desire for "normal" body parts, this is only a location note)
3,|n=1||nose=large|
4,|n=1||nose=bulbous|

:Lips
1,|l=1||lips=small|
2,
#normal
3,|l=1||lips=large|

:Ears
1,|e=1||ears=small|
2,
#normal
3,|e=1||ears=large|


#### wherever your output line is
{If~%e%=1?%ears%, /}{If~%l%=1?%lips%, /}{If~%n%=1?%nose%, /} and [Eyes]
# Note 1: You don't have to make the eyes a variable since you always want them to show up.
# Note 2: You can arrange the output text for additional items any way you want beyond just the size or shape descriptor you choose, i.e. "a %nose% nose, ".
# Note 3: Note the inclusion of a space after the variable (or textual format you choose), but not between If statements, this makes the output workable by placing spaces where needed.

Show quoted text

--- In TableSmith@..., "Sablesword" <ErolB1@...> wrote:

What's the cleanest, most elegant way to set up a group or set of groups that outputs a serial list of varying length, so as to properly include the optional commas and final optional "and"?

E.g. "... with x, y, z, and aa." where the "aa" is always present, but the x, y, and z are all optional, so that the output will sometimes have two or more of the optional elements ("with x, y, and aa") sometimes just one of the optional elements ("with z and aa" - no comma) and sometimes with none of the optional elements ("with aa" - no "and").

Is the most elegant answer to first determine how many optional items are in the list, and then run a group with the three cases (zero optional item, one optional item, two or more optional items)? Is it to keep track of how many optional items are generated and to toggle the commas and the final "and" based on this? Is there another, better answer?

In particular, I'm trying to set up a "face description" table, where the eyes are always described at the end, but the various other facial features are only described if they're unusual in some way: Nose mentioned if it's big, small, or otherwise special, but not if it's average; mouth mentioned if it's generous, or thin and bloodless, or permenantly frowning, or otherwise odd, but not if it's normal; a scar mentioned if it's present, but not otherwise; and so on.

Re: Producing serial lists of varying length

#7838

Cleanest way to do it?

Two methods:?
If statement. ?Knowing you have aa, you can check if you have x,y or z and do a comma, else period. Then you check x, and see if you have a value in y or z etc etc

Random selection:
:sentence builder
1, [aa], [x], [y], [z].
1, [aa], [x], [y].
1, [aa], [x], [z].
1, [aa], [y], [z].

Etc etc


Sent from my Samsung smartphone on AT&T

Show quoted text

-------- Original message --------
Subject: [TableSmith] Producing serial lists of varying length
From: Sablesword <ErolB1@...>
To: TableSmith@...
CC:

What's the cleanest, most elegant way to set up a group or set of groups that outputs a serial list of varying length, so as to properly include the optional commas and final optional "and"?

E.g. "... with x, y, z, and aa." where the "aa" is always present, but the x, y, and z are all optional, so that the output will sometimes have two or more of the optional elements ("with x, y, and aa") sometimes just one of the optional elements ("with z and aa" - no comma) and sometimes with none of the optional elements ("with aa" - no "and").

Is the most elegant answer to first determine how many optional items are in the list, and then run a group with the three cases (zero optional item, one optional item, two or more optional items)? Is it to keep track of how many optional items are generated and to toggle the commas and the final "and" based on this? Is there another, better answer?

In particular, I'm trying to set up a "face description" table, where the eyes are always described at the end, but the various other facial features are only described if they're unusual in some way: Nose mentioned if it's big, small, or otherwise special, but not if it's average; mouth mentioned if it's generous, or thin and bloodless, or permenantly frowning, or otherwise odd, but not if it's normal; a scar mentioned if it's present, but not otherwise; and so on.

------------------------------------

Yahoo! Groups Links

[Non-text portions of this message have been removed]

Producing serial lists of varying length

#7837

What's the cleanest, most elegant way to set up a group or set of groups that outputs a serial list of varying length, so as to properly include the optional commas and final optional "and"?

E.g. "... with x, y, z, and aa." where the "aa" is always present, but the x, y, and z are all optional, so that the output will sometimes have two or more of the optional elements ("with x, y, and aa") sometimes just one of the optional elements ("with z and aa" - no comma) and sometimes with none of the optional elements ("with aa" - no "and").

Is the most elegant answer to first determine how many optional items are in the list, and then run a group with the three cases (zero optional item, one optional item, two or more optional items)? Is it to keep track of how many optional items are generated and to toggle the commas and the final "and" based on this? Is there another, better answer?

In particular, I'm trying to set up a "face description" table, where the eyes are always described at the end, but the various other facial features are only described if they're unusual in some way: Nose mentioned if it's big, small, or otherwise special, but not if it's average; mouth mentioned if it's generous, or thin and bloodless, or permenantly frowning, or otherwise odd, but not if it's normal; a scar mentioned if it's present, but not otherwise; and so on.

Re: A question regarding parameters

#7836

Vance:
It would be more like Option A - setting up the paramters first (I'm crap at explaining myself so sorry for confusion)

These variables would need to be set before the table runs properly the first time, and can change often, hence why i thought parameters would be ideal (if wrong,please feel free to correct)

Show quoted text

--- In TableSmith@..., "Vance" <clubvance@...> wrote:

The only time you truely need Parameters is:

A) If you want to set variable values prior to running a table
(using the gear looking parameters button) ... it will run the first time
with the default values, then you can select new parameters.
@option1,1,Which class would you like to
roll,Random,Richman,Poorman,Beggerman,Thief
would default to Random unless you chose another prior to running the table.

B) If you are passing variables to another table using the branch
 [table.group (par1,par2,,,par5)]

If you want to affect the output of the table DURING execution, I would use
an InputList~ function
|Var={InputList~1,Select an option,1,2,A,Z,beanpole}|
similar to the parameter (which can only be accessed outside the execution).

Vance

----- Original Message -----
From: "chriskentlea" >

I was just using those as examples, they will be vastly different from the
proper ones (just get a hold of them right now to show you)
--- In TableSmith@..., Joe <please.stop.hate@> wrote:

On Monday-Jun-10-2013 6:11 Morning, chriskentlea wrote:

Am i right in thinking if i have say 4 paramters at the start of the
table, and each has 20 options or so, would use them like this:

@option1,1,Treasure level,Half,Standard,Double,Triple
@option2,1,APL,1,2,3,4,5,6,7,8,9,10
@option3,1,Something else,blah, splerg,nomnomnom

_{If~%option1%=1|variable1=10|}
_{If~%option1%=2|variable1=20|}
_{If~%option1%=3|variable1=30|}

etc for each option, so i would have in the end 3 variables to work
with

or is there a simpler way of doing it?
@option1,1,Treasure level,Half,Standard,Double,Triple
@option2,1,APL,1,2,3,4,5,6,7,8,9,10
@option3,1,Something else,blah, splerg,nomnomnom

#since the first variable seems to need to only be a multiple of ten
#this solution is more elegant.

_|option1*10|

Cheers
Joe

Re: A question regarding parameters

#7835

If I understand what you're doing correctly, that is one way. There are a
couple others as well:

1) If the choices are sequential numbers, you could put the variable
options into a group and then call the group with a forced value, making it
more of a lookup group rather than a "regular" one. Using your example
(which would work for something like the APL variable), you could do this:

_|variable1=[refgroup=%option1%]|
...
:refgroup
1,10
2,20
3,30
...

2) There's also the "Select" function (
), which could work something like
this:

_|treasurelvl={Select~%option1%,Half,0.5,Standard,1.0,Double,2.0,3.0}|

Show quoted text

On Mon, Jun 10, 2013 at 8:11 AM, chriskentlea <chris.kentlea@...>wrote:

**


Am i right in thinking if i have say 4 paramters at the start of the
table, and each has 20 options or so, would use them like this:

@option1,1,Treasure level,Half,Standard,Double,Triple
@option2,1,APL,1,2,3,4,5,6,7,8,9,10
@option3,1,Something else,blah, splerg,nomnomnom

_{If~%option1%=1|variable1=10|}
_{If~%option1%=2|variable1=20|}
_{If~%option1%=3|variable1=30|}

etc for each option, so i would have in the end 3 variables to work with

or is there a simpler way of doing it?

Re: A question regarding parameters

#7834

The only time you truely need Parameters is:

A) If you want to set variable values prior to running a table
(using the gear looking parameters button) ... it will run the first time with the default values, then you can select new parameters.
@option1,1,Which class would you like to roll,Random,Richman,Poorman,Beggerman,Thief
would default to Random unless you chose another prior to running the table.

B) If you are passing variables to another table using the branch
[table.group (par1,par2,,,par5)]

If you want to affect the output of the table DURING execution, I would use an InputList~ function
|Var={InputList~1,Select an option,1,2,A,Z,beanpole}|
similar to the parameter (which can only be accessed outside the execution).

Vance

Show quoted text

----- Original Message ----- 
From: "chriskentlea" >

I was just using those as examples, they will be vastly different from the proper ones (just get a hold of them right now to show you)
--- In TableSmith@..., Joe <please.stop.hate@...> wrote:

On Monday-Jun-10-2013 6:11 Morning, chriskentlea wrote:

Am i right in thinking if i have say 4 paramters at the start of the
table, and each has 20 options or so, would use them like this:

@option1,1,Treasure level,Half,Standard,Double,Triple
@option2,1,APL,1,2,3,4,5,6,7,8,9,10
@option3,1,Something else,blah, splerg,nomnomnom

_{If~%option1%=1|variable1=10|}
_{If~%option1%=2|variable1=20|}
_{If~%option1%=3|variable1=30|}

etc for each option, so i would have in the end 3 variables to work with

or is there a simpler way of doing it?
@option1,1,Treasure level,Half,Standard,Double,Triple
@option2,1,APL,1,2,3,4,5,6,7,8,9,10
@option3,1,Something else,blah, splerg,nomnomnom

#since the first variable seems to need to only be a multiple of ten
#this solution is more elegant.

_|option1*10|

Cheers
Joe

Re: A question regarding parameters

#7833

I was just using those as examples, they will be vastly different from the proper ones (just get a hold of them right now to show you)

Show quoted text

--- In TableSmith@..., Joe <please.stop.hate@...> wrote:

On Monday-Jun-10-2013 6:11 Morning, chriskentlea wrote:

Am i right in thinking if i have say 4 paramters at the start of the
table, and each has 20 options or so, would use them like this:

@option1,1,Treasure level,Half,Standard,Double,Triple
@option2,1,APL,1,2,3,4,5,6,7,8,9,10
@option3,1,Something else,blah, splerg,nomnomnom

_{If~%option1%=1|variable1=10|}
_{If~%option1%=2|variable1=20|}
_{If~%option1%=3|variable1=30|}

etc for each option, so i would have in the end 3 variables to work with

or is there a simpler way of doing it?
@option1,1,Treasure level,Half,Standard,Double,Triple
@option2,1,APL,1,2,3,4,5,6,7,8,9,10
@option3,1,Something else,blah, splerg,nomnomnom

#since the first variable seems to need to only be a multiple of ten
#this solution is more elegant.

_|option1*10|

Cheers
Joe


[Non-text portions of this message have been removed]

Re: A question regarding parameters

#7832

On Monday-Jun-10-2013 6:11 Morning, chriskentlea wrote:

Am i right in thinking if i have say 4 paramters at the start of the 
table, and each has 20 options or so, would use them like this:

@option1,1,Treasure level,Half,Standard,Double,Triple
@option2,1,APL,1,2,3,4,5,6,7,8,9,10
@option3,1,Something else,blah, splerg,nomnomnom

_{If~%option1%=1|variable1=10|}
_{If~%option1%=2|variable1=20|}
_{If~%option1%=3|variable1=30|}

etc for each option, so i would have in the end 3 variables to work with

or is there a simpler way of doing it?
@option1,1,Treasure level,Half,Standard,Double,Triple
@option2,1,APL,1,2,3,4,5,6,7,8,9,10
@option3,1,Something else,blah, splerg,nomnomnom

#since the first variable seems to need to only be a multiple of ten
#this solution is more elegant.

_|option1*10|

Cheers
Joe

A question regarding parameters

#7831

Am i right in thinking if i have say 4 paramters at the start of the table, and each has 20 options or so, would use them like this:

@option1,1,Treasure level,Half,Standard,Double,Triple
@option2,1,APL,1,2,3,4,5,6,7,8,9,10
@option3,1,Something else,blah, splerg,nomnomnom

_{If~%option1%=1|variable1=10|}
_{If~%option1%=2|variable1=20|}
_{If~%option1%=3|variable1=30|}

etc for each option, so i would have in the end 3 variables to work with


or is there a simpler way of doing it?