Revise Journal Tab (Savage) - Revision history

Rob: /* Revise the Header */

2009-01-30T03:11:12Z

Revise the Header

← Older revision		Revision as of 03:11, 30 January 2009
Line 92:		Line 92:
	call RankName		call RankName
	@text = "{text a0a0a0}Total $: " & herofield[acCashNet].value		@text = "{text a0a0a0}Total $: " & herofield[acCashNet].value
	@text &= "{horz 40} Total XP: " & ~~hero.usagepool~~[~~TotalXP~~]~~.value~~		@text &= "{horz 40} Total XP: " & #resmax[resXP]
	@text &= "{horz 40} Rank: " & ranktext		@text &= "{horz 40} Rank: " & ranktext
	</pre>		</pre>

Rob at 10:46, 18 December 2008

2008-12-18T10:46:38Z

← Older revision		Revision as of 10:46, 18 December 2008
Line 3:		Line 3:
	===Overview===		===Overview===

	We've got advancements in place, but advancements are dependent upon the accumulation of experience points (XP). The Skeleton files provide a reasonable starting point for tracking XP and finances, along with a suitable tab where the user can manage these details. However, we can probably tailor it better for ~~our game system~~. So the next thing we'll tackle is the Journal tab.		We've got advancements in place, but advancements are dependent upon the accumulation of experience points (XP). The Skeleton files provide a reasonable starting point for tracking XP and finances, along with a suitable tab where the user can manage these details. However, we can probably tailor it better for Savage Worlds. So the next thing we'll tackle is the Journal tab.

	===Assess Each Journal Entry===		===Assess Each Journal Entry===
Line 11:		Line 11:
	===Assess the Header===		===Assess the Header===

	While the individual journal entries are fine as they are, the header information at the top only shows the total cash on hand and total accrued XP. It would probably helpful to the user to also show the character's current rank, since that has implications on the various edges and arcane powers that can be selected. We could even include the number of XP needed to reach the next rank, but each rank is an even 20 XP, so it's something a user can instantly determine and therefore makes little sense for us to add.		While the individual journal entries are fine as they are, the header information at the top only shows the total cash on hand and total accrued XP. It would probably be helpful to the user to also show the character's current rank, since that has implications on the various edges and arcane powers that can be selected. We could even include the number of XP needed to reach the next rank, but each rank is an even 20 XP, so it's something a user can instantly determine and therefore makes little sense for us to add.

	This will be the third time we need to convert the character rank from a numeric value to the corresponding name. So we really need to resolve this before we proceed with our changes to the header.		This will be the third time we need to convert the character rank from a numeric value to the corresponding name. So we really need to resolve this before we proceed with our changes to the header.
Line 17:		Line 17:
	===Converting Rank from Value to Text===		===Converting Rank from Value to Text===

	We need to convert the character rank from the numeric value ~~that~~ it ~~is tracked~~ internally to a string for display. Typically, when a field is involved, this can be done by simply defining a Finalize script that performs the conversion. However, we also need to convert the rank requirement used within the pre-requisite test for minimum character rank, and the Finalize script won't work for that, so we need to devise a different approach. The technique we'll use is to write a procedure that will receive the rank value to be converted in one variable and place the result in a separate variable for use by the caller.		We need to convert the character rank from the numeric value used to track it internally to a string for display. Typically, when a field is involved, this can be done by simply defining a Finalize script that performs the conversion. However, we also need to convert the rank requirement used within the pre-requisite test for minimum character rank, and the Finalize script won't work for that, so we need to devise a different approach. The technique we'll use is to write a procedure that will receive the rank value to be converted in one variable and place the result in a separate variable for use by the caller.

	This procedure has an interesting wrinkle to it, though. This procedure needs to be able to be called from within both a Label script and a ~~PreReq~~ script. The Label script starts with an initial context of a pick/thing, while the ~~PreReq~~ script starts with an initial context of a container. As such, the two script types have nothing in common, so there is no procedure context we can use that the two can share. The solution is to define a procedure with a script type of "none". This results in a procedure that has no context whatsoever, which means there is no ~~"this"~~ context for the procedure (implied or otherwise). Since we only need to convert a numeric value to a string, there is no context required, so we can use this technique.		This procedure has an interesting wrinkle to it, though. This procedure needs to be able to be called from within both a Label script and a Validate script. The Label script starts with an initial context of a pick/thing, while the Validate script starts with an initial context of a container. As such, the two script types have nothing in common, so there is no procedure context we can use that the two can share. The solution is to define a procedure with a script type of "none". This results in a procedure that has no context whatsoever, which means there is no initial script context for the procedure (implied or otherwise). Since we only need to convert a numeric value to a string, there is no context required, so we can use this technique.

	Open the file "procedures.dat", where we can now add the new procedure that we'll call "RankName". We can steal the logic out of the file "tab_basics.dat" for use within our procedure. The net result is something that should look like the definition below.		Open the file "procedures.dat", where we can now add the new procedure that we'll call "RankName". We can steal the logic out of the file "tab_basics.dat" for use within our procedure. The net result is something that should look like the definition below.
Line 55:		Line 55:
	</pre>		</pre>

	Next, we'll revise the logic within the "MinRank" component. Open up the file "components.core" and locate the "MinRank" component, then find its ~~PreReq~~ element. We replace the if/then/else block with a suitable call to the "RankName" procedure, resulting in a new ~~PreReq element~~ that looks like the one below.		Next, we'll revise the logic within the "MinRank" component. Open up the file "components.core" and locate the "MinRank" component, then find its "prereq" element. We replace the if/then/else block with a suitable call to the "RankName" procedure, resulting in a new Validate script that looks like the one below.

	<pre>		<pre>
Line 62:		Line 62:
	var rankvalue as number		var rankvalue as number
	var ranktext as string		var ranktext as string

	~get the minimum rank required for the thing to be valid		~get the minimum rank required for the thing to be valid
	rankvalue = altthing.field[rnkMinRank].value		rankvalue = altthing.field[rnkMinRank].value

	~if the minimum rank is satisfied, we're good to go		~if the minimum rank is satisfied, we're good to go
	if (herofield[acRank].value >= rankvalue) then		if (herofield[acRank].value >= rankvalue) then
Line 69:		Line 71:
	done		done
	endif		endif

	~mark the panel as invalid		~mark the panel as invalid
	altthing.linkvalid = 0		altthing.linkvalid = 0

	~synthesize an appropriate validation error message		~synthesize an appropriate validation error message
	call RankName		call RankName

Rob: Revise Journal Tab (Skeleton) moved to Revise Journal Tab (Savage)

2008-12-18T07:53:56Z

Revise Journal Tab (Skeleton) moved to Revise Journal Tab (Savage)

← Older revision	Revision as of 07:53, 18 December 2008
(No difference)

Rob: New page: {{context|Authoring Examples|Savage Worlds Walk-Through}} ===Overview=== We've got advancements in place, but advancements are dependent upon the accumulation of experience points (XP). ...

2008-12-17T07:35:28Z

New page: {{context|Authoring Examples|Savage Worlds Walk-Through}} ===Overview=== We've got advancements in place, but advancements are dependent upon the accumulation of experience points (XP). ...

New page

{{context|Authoring Examples|Savage Worlds Walk-Through}}

===Overview===

We've got advancements in place, but advancements are dependent upon the accumulation of experience points (XP). The Skeleton files provide a reasonable starting point for tracking XP and finances, along with a suitable tab where the user can manage these details. However, we can probably tailor it better for our game system. So the next thing we'll tackle is the Journal tab.

===Assess Each Journal Entry===

The first thing we need to do is look at the individual journal entries provided by the Skeleton files and assess what needs to be added, deleted, or changed. Savage Worlds uses a rather common approach for handling money and XP, so we don't really need to track anything additional for each journal entry. Some games employ complex currencies with multiple types of coins that must be tracked independently, and those games will require some re-work of each journal entry to allow the user to properly manage those currencies. Fortunately, Savage Worlds isn't such a game, so we can avoid that work.

===Assess the Header===

While the individual journal entries are fine as they are, the header information at the top only shows the total cash on hand and total accrued XP. It would probably helpful to the user to also show the character's current rank, since that has implications on the various edges and arcane powers that can be selected. We could even include the number of XP needed to reach the next rank, but each rank is an even 20 XP, so it's something a user can instantly determine and therefore makes little sense for us to add.

This will be the third time we need to convert the character rank from a numeric value to the corresponding name. So we really need to resolve this before we proceed with our changes to the header.

===Converting Rank from Value to Text===

We need to convert the character rank from the numeric value that it is tracked internally to a string for display. Typically, when a field is involved, this can be done by simply defining a Finalize script that performs the conversion. However, we also need to convert the rank requirement used within the pre-requisite test for minimum character rank, and the Finalize script won't work for that, so we need to devise a different approach. The technique we'll use is to write a procedure that will receive the rank value to be converted in one variable and place the result in a separate variable for use by the caller.

This procedure has an interesting wrinkle to it, though. This procedure needs to be able to be called from within both a Label script and a PreReq script. The Label script starts with an initial context of a pick/thing, while the PreReq script starts with an initial context of a container. As such, the two script types have nothing in common, so there is no procedure context we can use that the two can share. The solution is to define a procedure with a script type of "none". This results in a procedure that has no context whatsoever, which means there is no "this" context for the procedure (implied or otherwise). Since we only need to convert a numeric value to a string, there is no context required, so we can use this technique.

Open the file "procedures.dat", where we can now add the new procedure that we'll call "RankName". We can steal the logic out of the file "tab_basics.dat" for use within our procedure. The net result is something that should look like the definition below.

<pre>
<procedure id="RankName" scripttype="none"><![CDATA[
~declare variables that are used to communicate with our caller
var rankvalue as number
var ranktext as string
~map the value to the corresponding string
if (rankvalue = 0) then
ranktext = "Novice"
elseif (rankvalue = 1) then
ranktext = "Seasoned"
elseif (rankvalue = 2) then
ranktext = "Veteran"
elseif (rankvalue = 3) then
ranktext = "Heroic"
elseif (rankvalue = 4) then
ranktext = "Legendary"
else
ranktext = "Invalid Value: " & rankvalue
endif
]]></procedure>
</pre>

Once the procedure is in place, we need to go back and convert the two existing references to rank over to call the new procedure. We'll start with the Label script for showing the rank on the Basics tab. Open the file "tab_basics.dat" and locate the "baRank" portal. We change the Label script to call the "RankName" procedure to perform the conversion, which yields a new script that mirrors the one below.

<pre>
var rankvalue as number
var ranktext as string
rankvalue = herofield[acRank].value
call RankName
@text = ranktext & " (" & hero.child[resXP].field[resMax].value & " XP)"
</pre>

Next, we'll revise the logic within the "MinRank" component. Open up the file "components.core" and locate the "MinRank" component, then find its PreReq element. We replace the if/then/else block with a suitable call to the "RankName" procedure, resulting in a new PreReq element that looks like the one below.

<pre>
<prereq iserror="yes" message="Minimum Rank required.">
<valid><![CDATA[
var rankvalue as number
var ranktext as string
~get the minimum rank required for the thing to be valid
rankvalue = altthing.field[rnkMinRank].value
~if the minimum rank is satisfied, we're good to go
if (herofield[acRank].value >= rankvalue) then
@valid = 1
done
endif
~mark the panel as invalid
altthing.linkvalid = 0
~synthesize an appropriate validation error message
call RankName
@message = ranktext & " rank required."
]]></valid>
</prereq>
</pre>

===Revise the Header===

Now that we've got the new "RankName" procedure in place, we can put it to use within the header of the Journal tab. Open the file "tab_journal.dat" and locate the "jrHeader" template, then find its "info" portal. This portal contains a Label script that synthesizes the text to be shown within the header. We'll amend it to add a new entry that shows the character's rank, yielding a revised script similar to the following.

<pre>
var rankvalue as number
var ranktext as string
rankvalue = herofield[acRank].value
call RankName
@text = "{text a0a0a0}Total $: " & herofield[acCashNet].value
@text &= "{horz 40} Total XP: " & hero.usagepool[TotalXP].value
@text &= "{horz 40} Rank: " & ranktext
</pre>