revisit RwDefinedProject>>addNewComponentNamed:...condition:... and RwDefinedProject>>addPlatformComponentNamed:...pathNameArray:conditionPathArray:...

[dalehenrich]

Right now, I think that we should rename RwDefinedProject >> addPlatformComponentNamed:toComponentNamed:pathNameArray:conditionPathArray: to RwDefinedProject >> addStructureComponentNamedToComponentNamed:pathNameArray:conditionPathArray: (see RwTestProjectLibraryGenerator>>_addDefinitionsFor_0059: for the canonical example) and remove the RwDefinedProject>>addNewComponentNamed:...condition:... family of methods...

Currently the example in RwTestProjectLibraryGenerator>>genSpec_0059: is building the kind of structure that I think makes sense .. as other structural patterns appear as useful, then add additional methods ...

Evaluate RwDefinedProject >> addNewComponentNamed:toComponentNamed:condition: for the ability to compose structures a component at a time (the addPlatformComponentNamed:... protocol builds the intermediate component structure for you... so it is a convenient shorthad) ....

• [x] Get rid of all of the variety's of the addNewComponent... and addPlatformComponent... variants to simplify the kinds of choices that need to be made ... to many subtle (and not useful) variations are currently present ...
• [ ] restructure RwAbstractProject .. Rw(Loaded)Project and RwDefinedProject share a lot of protocol, so they should share a common superclass ... RwResolvedProject has minimal protocol ...
• [x] Use new naming conventions for classes and methods
• [x] move RwResolvedLoadComponentsV2 (and rename to RwResolvedProjectComponentsV2) to be a PEER of RwProjectDefinitionV2 ... should simplify the handling of "loaded components"
• [x] skip the creation of definitions for the loaded things (asDefinition) and do the compare directly between definitions and loaded things (see #677)
• [ ] Need to flesh out the component API (see #573) this is at the RwAbstractProject level ...
• [x] restructure bootstrap .gs file directories ... need to allow for the fact that a single 3.x gemstone version may need to have separate .gs files for each dot release (i.e., 3.6.0 and 3.6.1) and the current structure with scripts embedded in the 3.x.x directory is too cumbersome to maintain ... should be able to have central list of scripts for each version and 3.x.x directories that just hold the .gs files ...
• [x] collapse RwAbstractProjectComponentVisitorV2 and RwResolvedProjectComponentVisitorV2

[dalehenrich]

Decided to use selector addComponentStructureFor:pathNameArray:conditionPathArray:comment: for the new method

[dalehenrich]

condition is either a single condition string or an array of strings ... the strings in the array are or'ed together and the single condition must match .... so the both are accepted in the conditionaPathArray argument in addComponentStructureFor:pathNameArray:conditionPathArray:comment: (see RwTestProjectLibraryGenerator>>>>_addDefinitionsFor_0059:)

[dalehenrich]

@LisaAlmarode has defined a the names for the Component classes, so it's time now to start incorporating the new names into the system, changing both class names and method names to match ...