Proposed FREQ Roadmap
Introduction
This page covers future planning of version 6.0+, see the individual roadmaps for details of the confirmed plans for 5.10, 5.12, 5.14 and 5.16.
6.0 CDOM Milestone - PRIMARY OBJECTIVE
- Approved for implementation in 6.0
- CDOM theme (many freqs will fall under this banner as CDOM will resolve several outstanding freqs)
- Implicit 6.0 FREQs
6.0 Editor Milestone - SECONDARY OBJECTIVE
- 6.x Editor Rebuild FREQs
- So this requires an honest assessment of whether we can ship 6.0 without a GUI editor. The existing editor *will* irrevokably break, because it is heavily dependent upon function in the old core.... if we don't do a new one, 6.0 ships with no editor. Given past feedback I've received, I think "no editor is acceptable" is a minority opinion... besides, I've effectively committed one in comments on enWorld ;)
6.0 Community Development Milestone - SECONDARY OBJECTIVE
- Approved for implementation in 6.0
- This one is on the Admin team - web site with forums, our own wiki, etc.
6.0 Internationalization Milestone - SECONDARY OBJECTIVE
- Approved for implementation in 6.0
- I18n, language bundles and the first release of a new language
- If this is really going to happen, we need to buckle down on getting the spec for internationalization of the datasets and game modes worked out. It has been hashed around at a theoretical level, but requires more work to understand the consequences. CDOM today is *NOT* internationalized at the LST I/O level. (There is nothing that necessarily prevents it, but the fact is, the data format is undefined, so one can't exactly write parsers to process the text).
6.0 UI Milestone
- Refactoring of hard coded UI approved for 6.0
- First cut of the new UI
6.0 Ability Data Milestone - SECONDARY OBJECTIVE
- Approved for implementation in 6.0
- Finish PCGen-shipped data conversion to Ability objects
6.0/6.2 Function Enablement Milestone
- There are numerous FREQs which are simple adds to the existing structure that are d20-ish, but which I don't (necessarily) want to distract from 6.0. Examples include: 1697595, 1689172, 1678170, 1629726, ... there are probably dozens of them. I think these should be planned as a separate group, but perhaps we need to evaluate progress (specifically speed of implementation) on 6.0 to determine whether this defines 6.2 or is part of 6.0.
6.2 UI Milestone - PRIMARY OBJECTIVE
- Overhaul the basic UI for creating PCs, e.g. A Wizard for creating new PC's
6.2 CDOM Performance Milestone
- Not approved for implementation in 6.0
- Look at the new CDOM core and assess whether there are performance issues, and address those.
- The reason I at least want the performance item is that we may expose a hotspot or two that are major code items (for example, but not limited to: bonuses, prerequisites, and/or JEP) that require a more significant rebuild than CDOM should address in the first pass.
6.2+ Formula Milestone
- Not approved for implementation in 6.0
- At some point - and this could be minor or it could be very painful - I suspect we want to deprecate non-JEP formulae. This *requires* a method of catching problems at LST load (and probably an automatic converter), so this must be deferred to at least 6.2, if not 6.4 (more on how at a later point)
6.2+ d20 System Depth Milestone
- Not approved for implementation in 6.0
- Gestalt, spellcasters with multiple spell lists (e.g. Arcane and Divine), 1072152, Equipment Variables, Workaround LST, Skill & Template Levels
- Perhaps Equipment containers and composition falls here (though it might be in the 6.x Function Enablement Milestone)
6.2+ System Breadth Milestone
- Not approved for implementation in 6.0
- Might even be better phrased 7.0 System Breadth Milestone
- Start enabling strange campaign settings and perhaps even non-d20 systems
6.2+ Update code from within PCGen
- Like modern browsers do
Freqs (To be split into Milestones)
The following are the categories of FREQs as Tom (PCGen Architecture Second) sees them:
Low-Moderate Difficulty 6.2-6.4 FREQs
Moderate-High Difficulty FREQs, to be Scheduled
High Difficulty FREQs, to be Scheduled
Complex or Insufficiently Specified FREQs
Non-Core FREQs (implementation not significantly constrained by CDOM/6.0)
