Difference between revisions of "Tom's Arch "TO DO" List"
LegacyKing (talk | contribs) (To Do List for the Arch Team) |
LegacyKing (talk | contribs) |
||
| Line 2: | Line 2: | ||
* 1) Tighter integration on the Wiki to articulate what packages are part of which components in PCGen (references both directions don't exist today) | * 1) Tighter integration on the Wiki to articulate what packages are part of which components in PCGen (references both directions don't exist today) | ||
| − | * 2) Visualisations of [the graph concept] on the wiki? We will need some examples for the "thought cases"/"counter-cases" that drive us to the current design | + | * 2) Visualisations of [[the graph concept]] on the wiki? We will need some examples for the "thought cases"/"counter-cases" that drive us to the current design |
* 3) Commented sample of how to ties two nodes together with a relationship on the wiki would be very useful, though this is data structure dependent. | * 3) Commented sample of how to ties two nodes together with a relationship on the wiki would be very useful, though this is data structure dependent. | ||
* 4) How to take advantage of the type safety now available in the core and truly improve performance | * 4) How to take advantage of the type safety now available in the core and truly improve performance | ||
Revision as of 20:24, 16 June 2009
Tom Parker, has identified the following items as "TO DO" list to continue progress on the Arch Front
- 1) Tighter integration on the Wiki to articulate what packages are part of which components in PCGen (references both directions don't exist today)
- 2) Visualisations of the graph concept on the wiki? We will need some examples for the "thought cases"/"counter-cases" that drive us to the current design
- 3) Commented sample of how to ties two nodes together with a relationship on the wiki would be very useful, though this is data structure dependent.
- 4) How to take advantage of the type safety now available in the core and truly improve performance
