08-25-2007, 03:43 PM | #1 |
Join Date: Feb 2006
Location: Krotz Springs, LA US
|
Phoenix 1.18 Status (no, not a release)
I thought I'd give a head's up on what's going on with the next release of Phoenix (1.18). In case anyone had any comments, questions, or requests before I started buttoning this release up. Here's a snippet from the change log.
[IN PROGRESS]
__________________
Thomas M. EDWARDS <tmedwards@motoslave.net> GCA4 resources: GCA Repository, Phoenix (r66), GMCS (2.17), Bookish (r12) |
08-28-2007, 10:57 AM | #2 |
Join Date: Feb 2006
Location: Krotz Springs, LA US
|
Re: Phoenix 1.18 Status (no, not a release)
Here are two examples of the, optional, footnotes in action on the primary statistics block:
__________________
Thomas M. EDWARDS <tmedwards@motoslave.net> GCA4 resources: GCA Repository, Phoenix (r66), GMCS (2.17), Bookish (r12) |
08-28-2007, 01:22 PM | #3 |
Join Date: Sep 2004
Location: Canada
|
Re: Phoenix 1.18 Status (no, not a release)
Looks very good. My only comment is the order that you use the various footnote marks in:
You appear to be going "asterix" "dagger" "double-dagger" "squiggly thing which I used to know the name of" "two asterixes" "two daggers" (and presumably thence to "two double-daggers" etc.) That's so incredibly logical that it hurts me to point out that I think conventional usage is "asterix", "two asterixes", and thence into the exotic symbols. I personally find your ordering method so wonderfully logical (and appealing to my coding brain) that I vote for yours. But I figured I'd mention it.
__________________
All about Size Modifier; Unified Hit Location Table A Wiki for my F2F Group A neglected GURPS blog |
08-28-2007, 02:22 PM | #4 | ||
Join Date: Feb 2006
Location: Krotz Springs, LA US
|
Re: Phoenix 1.18 Status (no, not a release)
While I probably would have done exactly the same thing, I can't take credit for the symbols used, I'm just using the footnote code that's built into GCA to generate the symbols.
As far as I know, that code based upon what was the official SJG guidelines for GURPS 4e at the time in which it was written (found on the page Steve Jackson Games: Authors' Guidelines under the link Formatting Guides for GURPS Fourth Edition). The specific quote is: Quote:
Quote:
__________________
Thomas M. EDWARDS <tmedwards@motoslave.net> GCA4 resources: GCA Repository, Phoenix (r66), GMCS (2.17), Bookish (r12) |
||
08-28-2007, 03:14 PM | #5 | |
Join Date: Feb 2006
Location: Krotz Springs, LA US
|
Re: Phoenix 1.18 Status (no, not a release)
Keeping in mind the above post about the footnote guidelines that Phoenix is using, I should point out that Phoenix does not follow those exactly.
Specifically the guidelines: Quote:
Additionally, a symbol will be reused if the footnote matches a previously registered footnote, so two different traits receiving the same bonuses/conditionals would get the same symbol. However, it's possible that a given bonus/conditional could be duplicated across multiple footnotes, and thus multiple symbols, if the combined footnotes don't match (e.g. "+4 from 'TraitA'" does not match "+4 from 'TraitA', +2 from 'TraitB'" even though they both contain "+4 from 'TraitA'", the entire footnote has to match for the symbol to be reused). Doing it the 100% correct way would require either GCA or sheets to create all symbols/footnotes by processing the entire trait list, so they could insure that the above guidelines were met. GCA's simple footnote code doesn't currently do this and every sheet that I've seen, even Phoenix, processes the trait list on-the-fly as it's being printed. Armin has recently made it easier for sheet authors to preprocess all bonuses/conditionals if they were inclined to do so, but that's still a lot of work for very little gain -- unless the sheet preprocessed everything, rather than doing it on-the-fly, but no sheet does that yet.
__________________
Thomas M. EDWARDS <tmedwards@motoslave.net> GCA4 resources: GCA Repository, Phoenix (r66), GMCS (2.17), Bookish (r12) |
|
08-28-2007, 03:17 PM | #6 |
Join Date: Feb 2006
Location: Krotz Springs, LA US
|
Re: Phoenix 1.18 Status (no, not a release)
Here's an example of the Blank Line Options. Does the text not parse well for anyone?
__________________
Thomas M. EDWARDS <tmedwards@motoslave.net> GCA4 resources: GCA Repository, Phoenix (r66), GMCS (2.17), Bookish (r12) |
08-28-2007, 05:05 PM | #7 | |
Join Date: Sep 2004
Location: Canada
|
Re: Phoenix 1.18 Status (no, not a release)
Quote:
__________________
All about Size Modifier; Unified Hit Location Table A Wiki for my F2F Group A neglected GURPS blog |
|
08-29-2007, 08:07 AM | #8 |
Join Date: Feb 2006
Location: Krotz Springs, LA US
|
Re: Phoenix 1.18 Status (no, not a release)
As part of the overhaul of the trait bonuses/conditionals code I'm reworking the trait bonuses options. To that end, the options have been moved from each of the trait-type option sections to their own Trait Bonuses Options section and I'm updating the list of blocks that will be part of the system.
The old list of blocks was this:
Beyond that, the other major trait bonuses option will be the print style, which will have two choices: (actual names, as of this posting)
__________________
Thomas M. EDWARDS <tmedwards@motoslave.net> GCA4 resources: GCA Repository, Phoenix (r66), GMCS (2.17), Bookish (r12) |
08-29-2007, 08:31 AM | #9 | |
Join Date: Jan 2005
Location: Stuttgart, Germany
|
Re: Phoenix 1.18 Status (no, not a release)
Quote:
In other words, have it look like: IQ 12 [ 40 ] | Instead of the current: IQ 12 [ 40 ]| (The bracket and the line tend to merge together and don't display as neatly).
__________________
Violence, naked force, has settled more issues in history than has any other factor, and the contrary opinion is wishful thinking at its worst. -RAH |
|
08-29-2007, 10:25 AM | #10 | |
Join Date: Feb 2006
Location: Krotz Springs, LA US
|
Re: Phoenix 1.18 Status (no, not a release)
Quote:
__________________
Thomas M. EDWARDS <tmedwards@motoslave.net> GCA4 resources: GCA Repository, Phoenix (r66), GMCS (2.17), Bookish (r12) |
|
|
|