Difference between revisions of "Index to Architecture Documents"
Tom Parker (talk | contribs) (→Loading) |
Tom Parker (talk | contribs) |
||
Line 20: | Line 20: | ||
# When retrieving items from the Rules Data Store, it's important to [[Identifying Objects|Identify the right Object]] | # When retrieving items from the Rules Data Store, it's important to [[Identifying Objects|Identify the right Object]] | ||
+ | # You will also need to know about [[Accessing Information]] | ||
=Processing a PC= | =Processing a PC= |
Revision as of 18:23, 4 March 2018
This is effectively a "shorthand" list of documents (and a tiny bit of context around the links) for "A Day in the Life of PCGen"
Resources
Before reading about the details of the PCGen architecture, it is likely helpful to understand our key Design Concepts for PCGen and Architecture Document Conventions
Loading
- The Startup System initializes PCGen and loads the initial user interface
- Files from Disk are loaded by the Rules Persistence System
- These files use CDOM References to resolve order of operations conflicts during load and Refer to Groups in LST Data to identify multiple possible objects (for say, a choice)
- The Load Commit Subsystem is used to commit information into the Rules Data Store
- Post Processing is completed as described in the Full Load Order Detail
Using Data
- When retrieving items from the Rules Data Store, it's important to Identify the right Object
- You will also need to know about Accessing Information
Processing a PC
- After Adding items to the PC, we begin Calculating Items on the PC
- This calculation heavily depends on the Formula Systems
- Some of the items on a PC can be conditional, so it's valuable to understand Prerequisites and Requirements