PDA

View Full Version : Reduce Windows in SRD



blake67
November 5th, 2010, 22:22
I hope I'm asking this in the right place, and in the right way.

First things first, my coding skills are laughable at best, so forgive if this is painfully obvious to those with rudimentary ability.

Anyway, I'd like to modify the 3.5 SRD module my campaign uses to reduce the amount of window spam when referencing information. I would like to consolidate the first and second level of windows such that instead of popping up a second window, the options within the second window merely drop down within the first window when the link is clicked.

Ok, that was a terrible way to say it, so let me try via example.

Currently, if I'd like to pull up the Weapons Table in the SRD, I open my library, click the SRD Basics, and click Equipment in the right side of that window. This gives me a window with a few links. I then click Weapons, which opens up a second window, from which I select the Weapons Table.

Instead, I'd like for the first window to look like this after I click Weapons:

Equipment
[] Wealth and Money
Weapons
. [] Weapon Categories
. [] Weapon Qualities
. [] Weapons Table
. [] Weapon Descriptions
. [] Masterwork Weapons
[] Armor
[] Goods and Services

I realize that the answer most likely lies somewhere within the difference in code between the Races window, which accesses the new info in the same window, and the Equipment one. I can't figure out exactly how to code it.

Races

<adraces>
<librarylink type="windowreference"><class>referenceinlineindex</class><recordname>..</recordname></librarylink>
<name type="string">Races</name>
<index>
<agraces>
<name type="string">Races</name>
<text type="formattedtext">
<h>Favored Class, etc.</h>
</text>
</agraces>
</index>
</adraces>

Equipment

<ahequipment>
<librarylink type="windowreference"><class>referenceindex</class><recordname>..</recordname></librarylink>
<name type="string">Equipment</name>
<index>
<blweapons>
<listlink type="windowreference"><class>referenceindex</class><recordname>..</recordname></listlink>
<name type="string">Weapons</name>
<index>
<aaweaponcategories>
<listlink type="windowreference"><class>referencetextwide</class><recordname>..</recordname></listlink>
<name type="string">Weapon Categories</name>
<text type="formattedtext">
<p>Weapons are grouped into several interlocking sets of categories.</p>
</text>
</aaweaponcategories>
</index>
</blweapons>
</index>
</ahequipment>

Thanks in advance for any assistance.

Moon Wizard
November 5th, 2010, 23:37
The module data links hand-in-hand with the reference windows defined in the ruleset. If you want to change the layout of the module data in the ruleset, you may need to change the module data as well.

To change the layout of the module data as it is shown in FG, you need to find the "windowclass" objects that are defined in the module data, and change the layout/behavior of the windows.

For example, in the 3.5E Spells module, these windowclass entries are used:
* reference_classspelllist
* reference_schoolspelllist
* reference_domainlist
* spelldesc

Once you find the files with these windowclasses, just browse through them to get a sense of how the various entries link to the fields on the screen. Then, you can look into moving and manipulating these.

You can even implement your windowclass replacement objects in an extension for portability to future updates.

Cheers,
JPG

blake67
November 9th, 2010, 20:43
Thank you very much for your assistance, and thank you even more for all the work you've done for this community.

I've been using your d20 ruleset from the beginning of my campaign, and its a major reason why I purchased this software package.

That said, as a programming idjet, I'm going to put the creation of new reference windows on the backburner. I'm currently remaking the CSRD .mods into Pathfinder SRD .mods, since there doesn't seem to be a set of those anywhere just yet, and that's already an undertaking in itself.

Thanks again :)