Agenda Next Meeting Deep Dive
Ongoing Discussion
Handling Incompatible Change
This is a discussion primarily rooted in replacing JEP as the formula system The first discussion took place at The June 6th Meeting.
This is an ongoing discussion to be picked up at the next deep dive session.
Future Discussion Topics
Selection User Experience
This is a strategy question for how we want users to make choices within PCGen. Right now we have various constructs (popup windows, pools (some that require certain items to be selected - see spells). While I'd like to keep the discussion away from data constructs, it's probably appropriate to point out that right now we have multiple methods of driving a selection (CHOOSE, ADD, Ability Pools, and a few others).
Especially for choices driven by the data, what is the user experience that we want? Specifically:
- How are selections deferred, if at all
- What types of choices are there (e.g. Archetypes, selecting a skill for Skill Focus, etc - this is a RULES question not a data token question) and do they justify different behavior?
- Should the data EVER be able to enforce a popup?
- Should data be able to provide a default choice if no other choice is made?
- How can selections be done efficiently without forcing popups?
- What specifically is the best user experience for a selection?
Abstract Documentation
Requires: Eric
This is a strategy question around our documentation. We are getting to a point where there will be things transferred from code to data.
There are multiple examples of this situation:
- We expect with the new variable system that there are no longer built in terms
- The output system will be moving to Freemarker rather than the existing output tokens
What is required to address this issue in terms of proper documentation when the data is controlling features and therefore features vary by game mode? Specifically:
- Where are variable lists captured?
- Are variable lists consolidated?
- How does a user know what output functions are valid in Freemarker?
