In the voting sheets, there is one column per name (example on right). This arrangement was chosen partly because, happily, we typically have more wines than people. This is the same arrangement as Mike’s spreadsheet.
But the Accounting page has only a few fields per name, so it seems more natural to have one name per row rather than one name per column, which is the transpose of Mike’s spreadsheet.
Objections?
Draft parameters:
Code: Select all
/AccountingNumCopies 1 def
/AccountingTopText (Accounting) def
/AccountingColumnTitles [ % Array of even length, alternately header for group of columns, and array of those columns' headers
[
(Bestowals) [ (Wine) ]
(Costs) [ (Food &c) (Wines) ]
(Settlement) [ (Owes) (Is owed) [(P) /quoteright {-0.08 Kern} (d?)] ]
] def
/AccountingColumnRelativeWidths [ 4 4 4 4 4 1 ] def
/AccountingExtraRows [ () (Total) () ] def
Comment welcomed. Notes follow.
AccountingNumCopies: Inserted following Flash’s suggestion three posts below.
AccountingTopText: must be a parameter to allow non-English possibilities.
AccountingColumnTitles: In the instance in which a group of columns has only one column, the group’s column title should be short: hence “Bestowals” rather than “Contributions”. Do suggest better. Also, should there be a few columns with blank titles? If so, within the groups already present, or in a new blank group?
AccountingColumnRelativeWidths: allows “P’d?” column to ne narrow, holding no more than a tick.
AccountingExtraRows: extra rows under those of the names, to cope with extra people, sub-calculations, changes of mind, &c.
Is this wanted? Is this what is wanted?