Character Sheet Phase 2 (Savage) - Revision history

Rob at 23:21, 19 February 2009

2009-02-19T23:21:25Z

← Older revision		Revision as of 23:21, 19 February 2009
Line 14:		Line 14:
	~position the armory layout within the remaining space on the right		~position the armory layout within the remaining space on the right
	layout[oArmory].width = colwidth		layout[oArmory].width = colwidth
	layout[oArmory].top = layout[oRightSide].bottom + ~~global~~[sectiongap]		layout[oArmory].top = layout[oRightSide].bottom + scenevalue[sectiongap]
	layout[oArmory].left = layout[oLogos].left		layout[oArmory].left = layout[oLogos].left
	layout[oArmory].height = extent - ~~global~~[sectiongap] - layout[oArmory].top		layout[oArmory].height = extent - scenevalue[sectiongap] - layout[oArmory].top
	perform layout[oArmory].render		perform layout[oArmory].render
	</pre>		</pre>

Rob: /* Skills */

2009-01-31T07:53:41Z

Skills

← Older revision		Revision as of 07:53, 31 January 2009
Line 118:		Line 118:
	portal[value].left = 405		portal[value].left = 405
	else		else
	portal[name].left = ~~115~~		portal[name].left = 105
	portal[value].left = ~~875~~		portal[value].left = 900
	endif		endif
	perform portal[adjust].alignrel[ltor,value,5]		perform portal[adjust].alignrel[ltor,value,5]

	~limit the name to the value portal edge		~limit the name to the value portal edge
	if (portal[name].right > portal[value].left - 5) then		if (portal[name].right > portal[value].left - 10) then
	portal[name].width = portal[value].left - portal[name].left - 5		portal[name].width = portal[value].left - portal[name].left - 10
	endif		endif

Rob: /* Skills */

2009-01-28T12:35:16Z

Skills

← Older revision		Revision as of 12:35, 28 January 2009
Line 112:		Line 112:
	done		done
	endif		endif

	~~~center everything vertically within the template~~
	~~perform portal[name].centervert~~
	~~perform portal[value].centervert~~
	~~perform portal[adjust].centervert~~
	~~perform portal[dots].centervert~~

	~position everything horizontally		~position everything horizontally
Line 128:		Line 122:
	endif		endif
	perform portal[adjust].alignrel[ltor,value,5]		perform portal[adjust].alignrel[ltor,value,5]

			~limit the name to the value portal edge
			if (portal[name].right > portal[value].left - 5) then
			portal[name].width = portal[value].left - portal[name].left - 5
			endif

			~size the name to fit the available space and limit to one line
			perform portal[name].sizetofit[36]
			portal[name].lineheight = 1

	~extend the dots from the right of the name across to the value on the right		~extend the dots from the right of the name across to the value on the right
	perform portal[dots].alignrel[ltor,name,0]		perform portal[dots].alignrel[ltor,name,0]
	portal[dots].width = portal[value].left - 5 - portal[dots].left		portal[dots].width = portal[value].left - 5 - portal[dots].left

			~center everything vertically within the template
			perform portal[name].centervert
			perform portal[value].centervert
			perform portal[adjust].centervert
			perform portal[dots].centervert
	</pre>		</pre>

Rob: /* Skills */

2009-01-28T00:04:00Z

Skills

← Older revision		Revision as of 00:04, 28 January 2009
Line 104:		Line 104:
	Now we can look at the "oSkillPick" template that is used to display each skill. Since we want our skills to look and behave basically the same as how we've already got attributes working, it's actually easiest to delete the current template, copy the attribute template, and adapt the attributes template slightly for skills. So that's how we'll proceed.		Now we can look at the "oSkillPick" template that is used to display each skill. Since we want our skills to look and behave basically the same as how we've already got attributes working, it's actually easiest to delete the current template, copy the attribute template, and adapt the attributes template slightly for skills. So that's how we'll proceed.

	Once the attribute template is cloned, we can revise it. First, we need to give it the appropriate id of "oSkillPick". The four portals are the same for skills, ~~with one exception~~. ~~The "name" portal needs to be changed to use a script. In the label script~~, ~~we always start with the name~~, ~~but~~ we ~~must also append the domain if one exists~~. Within the Position script, we need to change the horizontal positions assigned to the "name" and "value" portals. Since the template is being used in both of the table portals, we actually want different positions based on whether the skill has a domain or not. Putting this all together results in the ~~template~~ shown below.		Once the attribute template is cloned, we can revise it. First, we need to give it the appropriate id of "oSkillPick". The four portals are the same for skills, so no changes are needed there. However, skills possess domains, so we need to handle that properly within our spacing. Within the Position script, we need to change the horizontal positions assigned to the "name" and "value" portals. Since the template is being used in both of the table portals, we actually want different positions based on whether the skill has a domain or not. Putting this all together results in the revised Position script shown below.

	<pre>		<pre>
	~~<template~~		~our height is driven by the tallest portal
	id=~~"oSkillPick"~~		height = portal[value].height
	~~name="Output Skills Table"~~		if (issizing <> 0) then
	~~compset="Trait"~~		done
	~~marginvert="0">~~		endif

	<portal		~center everything vertically within the template
	~~id="name"~~		perform portal[name].centervert
	~~style="outNameLg">~~		perform portal[value].centervert
	~~<output_label>~~		perform portal[adjust].centervert
	~~<labeltext><![CDATA[~~		perform portal[dots].centervert
	~~@text = field~~[name].~~text~~
	~~if (tagis~~[~~User~~.~~NeedDomain] <> 0) then~~
	~~@text &= ": " & field~~[~~domDomain~~].~~text~~
	~~endif~~
	]~~]></labeltext>~~
	~~</output_label>~~
	~~</portal>~~

	~~<portal~~		~position everything horizontally
	id=~~"value"~~		if (tagis[User.NeedDomain] = 0) then
	~~style~~=~~"outValueLg">~~		portal[name].left = 40
	~~<output_label>~~		portal[value].left = 405
	~~<labeltext><![CDATA~~[		else
	~~var dietype as number~~		portal[name].left = 115
	~~var dietext as string~~		portal[value].left = 875
	~~dietype = field~~[~~trtFinal~~].~~value~~		endif
	~~call OutputDie~~		perform portal[adjust].alignrel[ltor,value,5]
	~~@text~~ = ~~dietext~~
	]~~]></labeltext>~~
	~~</output_label>~~
	</portal>

	~~<portal~~		~extend the dots from the right of the name across to the value on the right
	~~id="adjust"~~		perform portal[dots].alignrel[ltor,name,0]
	~~style="outNameLg">~~		portal[dots].width = portal[value].left - 5 - portal[dots].left
	~~<output_label>~~
	~~<labeltext><![CDATA[~~
	~~if (field[trtNetRoll].value = 0) then~~
	~~@text = ""~~
	~~else~~
	~~@text = signed(field[trtNetRoll].value)~~
	~~endif~~
	~~]]></labeltext>~~
	~~</output_label>~~
	~~</portal>~~

	~~<portal~~
	~~id="dots"~~
	~~style="outDots">~~
	~~<output_dots>~~
	~~</output_dots>~~
	~~</portal>~~

	~~<position><![CDATA[~~
	~~~our height is driven by the tallest portal~~
	~~height = portal[value].height~~
	~~if (issizing <> 0) then~~
	~~done~~
	~~endif~~

	~~~center everything vertically within the template~~
	~~perform portal[name].centervert~~
	~~perform portal[value].centervert~~
	~~perform portal[adjust].centervert~~
	~~perform portal[dots].centervert~~

	~~~position everything horizontally~~
	~~if (tagis[User.NeedDomain] = 0) then~~
	~~portal[name].left = 40~~
	~~portal[value].left = 405~~
	~~else~~
	~~portal[name].left = 115~~
	~~portal[value].left = 875~~
	~~endif~~
	~~perform portal[adjust].alignrel[ltor,value,5]~~

	~extend the dots from the right of the name across to the value on the right
	perform portal[dots].alignrel[ltor,name,0]
	portal[dots].width = portal[value].left - 5 - portal[dots].left
	~~]]></position>~~

	~~</template>~~
	</pre>		</pre>

Rob: /* Long Names */

2009-01-18T06:13:36Z

Long Names

← Older revision		Revision as of 06:13, 18 January 2009
Line 307:		Line 307:
	If we reload the data files and preview the character sheet, we'll now see the new sections for hindrances and edges. At this point, the left side of our character sheet is complete.		If we reload the data files and preview the character sheet, we'll now see the new sections for hindrances and edges. At this point, the left side of our character sheet is complete.

	===~~Long~~ Names===		===Shorter Names for Output===

	At this point, you'll probably have noticed that some of the various edges, hindrances, and racial abilities have reasonably long names. The longer names severely limit the amount of description text that can be included in the character sheet. It would be ideal to utilize shorter names for some of these items.		At this point, you'll probably have noticed that some of the various edges, hindrances, and racial abilities have reasonably long names. The longer names severely limit the amount of description text that can be included in the character sheet. It would be ideal to utilize shorter names for some of these items.

Rob: /* Omitting Items from Character Sheet */

2009-01-18T06:12:47Z

Omitting Items from Character Sheet

← Older revision		Revision as of 06:12, 18 January 2009
Line 320:		Line 320:

	===Omitting Items from Character Sheet===		===Omitting Items from Character Sheet===

			As we've been doing our testing and experimenting with the character sheet, you may have noticed that there are a few items that really don't need to be included on the sheet. For example, the "Free Edge" ability for humans really doesn't need to be listed on the character sheet. Similarly, the "Power Points" edge is included in the total power points listed for the character and doesn't really need to take up space on the sheet.

			We can omit selected items from inclusion on the character sheet very quickly. The Skeleton files provide a pre-defined "Print.NoPrint" tag. You can assign this tag to any thing that you don't want to have appear in the character sheet. Once assigned, you can then preclude all things possessing that tag from a given table via the List tag expression. For example, since the "oEdge" table portal currently has no List tag expression, you could define one comprising of "!Print.NoPrint" and skip all edges that possess the tag. The revised portal would like the following.

			<pre>
			<portal
			id="oEdge"
			style="outNormal">
			<output_table
			component="Edge"
			showtemplate="oAbilPick">
			<list>!Print.NoPrint</list>
			<headertitle><![CDATA[
			@text = "Edges"
			]]></headertitle>
			</output_table>
			</portal>
			</pre>

Rob: /* Hindrances and Edges */

2009-01-18T06:01:42Z

Hindrances and Edges

← Older revision		Revision as of 06:01, 18 January 2009
Line 306:		Line 306:

	If we reload the data files and preview the character sheet, we'll now see the new sections for hindrances and edges. At this point, the left side of our character sheet is complete.		If we reload the data files and preview the character sheet, we'll now see the new sections for hindrances and edges. At this point, the left side of our character sheet is complete.

			===Long Names===

			At this point, you'll probably have noticed that some of the various edges, hindrances, and racial abilities have reasonably long names. The longer names severely limit the amount of description text that can be included in the character sheet. It would be ideal to utilize shorter names for some of these items.

			The Kit makes it easy to add support for shorter names to a group of items in situations like this. If you identify a component where short names would be beneficial, you can set the "hasshortnames" attribute on the component to "yes". Doing so ensures that every thing derived from the component possesses a field with the id of "shortname". You can then specify this field within the definition of things derived from the component. If a particular thing has no "shortname" field, then the field automatically defaults to the contents of the basic name for the thing.

			We use the same template for edges, hindrances, and racial abilities. As such, we need to add support for short names to all three. Conveniently, all three share the "Ability" component, so we only need to assign the new behavior to this one component.

			Once that's done, we can go back through the various things and define "fieldval" elements to properly assign a "shortname" to those that require one. For example, the "Arcane Background: Super Powers" edge is extremely long and can be readily shorted to "Arcane Super Powers", or something along those lines.

			With short names in place, our last step is to make use of the new field. This simply requires that we reference the "shortname" field instead of the "name" field within the template that outputs the abilities. Once that change is in place, our character sheet will begin showing the shorter names whenever they are defined.

			===Omitting Items from Character Sheet===

Rob: /* Hindrances and Edges */

2009-01-17T01:20:18Z

Hindrances and Edges

← Older revision		Revision as of 01:20, 17 January 2009
Line 270:		Line 270:
	</portal>		</portal>
	</pre>		</pre>

			Once the two portals are defined, we then need to integrate them into the "oLeftSide" layout. This entails adding "portalref" elements for each and then positioning them beneath the racial abilities. The revised layout is shown below.

			<pre>
			<layout
			id="oLeftSide">
			<portalref portal="oHeroName"/>
			<portalref portal="oHeroInfo"/>
			<portalref portal="oAttribute"/>
			<portalref portal="oDerived"/>
			<portalref portal="oSkills"/>
			<portalref portal="oSkillsDom"/>
			<portalref portal="oAbility"/>
			<portalref portal="oHindrance"/>
			<portalref portal="oEdge"/>
			<position><![CDATA[
			~position the hero name at the top with the hero details beneath the name
			perform portal[oHeroName].autoplace[0]
			perform portal[oHeroInfo].autoplace[15]

			~position the tables next
			perform portal[oAttribute].autoplace
			perform portal[oDerived].autoplace
			perform portal[oSkills].autoplace
			perform portal[oSkillsDom].autoplace[0]
			perform portal[oAbility].autoplace
			perform portal[oHindrance].autoplace
			perform portal[oEdge].autoplace

			~our layout height is the extent of the elements within
			height = autotop
			]]></position>
			</layout>
			</pre>

			If we reload the data files and preview the character sheet, we'll now see the new sections for hindrances and edges. At this point, the left side of our character sheet is complete.

Rob: /* Racial Abilities */

2009-01-17T01:17:35Z

Racial Abilities

← Older revision		Revision as of 01:17, 17 January 2009
Line 215:		Line 215:
	component="RaceAbil"		component="RaceAbil"
	showtemplate="oAbilPick">		showtemplate="oAbilPick">
	~~<list><![CDATA[~~
	~~]]></list>~~
	<headertitle><![CDATA[		<headertitle><![CDATA[
	@text = "Racial Abilities"		@text = "Racial Abilities"

Rob: /* Hindrances and Edges */

2009-01-17T01:17:21Z

Hindrances and Edges

← Older revision		Revision as of 01:17, 17 January 2009
Line 243:		Line 243:
	===Hindrances and Edges===		===Hindrances and Edges===

	Both hindrances and edges are grouped together because they are ~~both~~ extremely simple.		Both hindrances and edges are grouped together because they are extremely simple and work virtually the same. Both of these facets of the character are built upon the "Ability" component. Since all we're showing is the name and summary on the character sheet, we can readily re-use the same template that we setup for showing racial abilities.

			This means that all we need to do is create two new table portals, both of which can be cloned and adapted from the portal used for racial abilities. We simply need to change the unique id, the component being filtered, and the header text. This results in the two new portals below.

			<pre>
			<portal
			id="oHindrance"
			style="outNormal">
			<output_table
			component="Hindrance"
			showtemplate="oAbilPick">
			<headertitle><![CDATA[
			@text = "Hindrances"
			]]></headertitle>
			</output_table>
			</portal>

			<portal
			id="oEdge"
			style="outNormal">
			<output_table
			component="Edge"
			showtemplate="oAbilPick">
			<headertitle><![CDATA[
			@text = "Edges"
			]]></headertitle>
			</output_table>
			</portal>
			</pre>