#61 closed task (released)
Complete structure of WarFoundry API objects
Reported by: | ibboard | Owned by: | ibboard |
---|---|---|---|
Priority: | blocker | Milestone: | WarFoundry 0.1 |
Component: | WarFoundry-API | Version: | |
Keywords: | Cc: | ||
Blocked By: | Blocking: | #50 |
Description
Following the WarFoundry schema work, the classes in the API don't all relate to the new location of attributes and the importance of different objects (some focus has been shifted). All of the classes should be brought up to date with the new schema.
Change History (19)
comment:1 Changed 11 years ago by
Status: | new → accepted |
---|
comment:2 Changed 11 years ago by
comment:3 Changed 11 years ago by
(In r90) Re #61 - Complete structure of WarFoundry API objects
- Update to using UnitEquipmentItem where properties have moved from EquipmentItem
- Add UnitEquipmentChoice as replacement for UnitEquipmentItemObj
comment:4 Changed 11 years ago by
(In r92) Re #61 - Complete structure of WarFoundry API objects
- Add adding of abilities and equipment to UnitType
- Add getting of all, required and optional abilities
- Add UnitAbility class to store UnitType's reference to Ability object
Also:
- Convert UnitType to using Genericed collections
- Reduce visibility of properties to private
comment:5 Changed 11 years ago by
(In r93) Re #61 - Complete structure of WarFoundry API objects
- Add methods for adding and getting Notes and contained UnitTypes of a UnitType
- Add method to get requirements of a unit
- Separate out required abilities from optional abilities
- Remove UnitAbility and handle by passing a boolean to the AddAbility method
comment:6 Changed 11 years ago by
(In r94) Re #61 - Complete structure of WarFoundry API objects
- Migrate AddUnit/RemoveUnit methods to Army for easier army loading
- Migrate requirement checking call to Army, since ArmyCategory just called parent army anyway
Also:
- Use genericed collections in Army
- Remove failed unit requirements from ArmyCategory
- Alter army.xsd to stop negatives in equipment amounts
comment:7 Changed 11 years ago by
(In r95) Re #61 - Complete structure of WarFoundry API objects
- Allow units to have zero members to handle meta-units where all members are individuals "contained" by the unit
comment:8 Changed 11 years ago by
(In r96) Re #61 - Complete structure of WarFoundry API objects
- Add containership in Army schema so that it can be stored and retrieved
comment:9 Changed 11 years ago by
(In r97) Re #61 - Complete structure of WarFoundry API objects
- Add containership support to Unit class
- Add method to UnitType to check if a UnitType is of an allowed type
comment:10 Changed 11 years ago by
(In r98) Re #61 - Complete structure of WarFoundry API objects
- Add CompositeEquipmentItem to handle composite items in Army schema
comment:11 Changed 11 years ago by
(In r99) Re #61 - Complete structure of WarFoundry API objects
- Use correct name for variable in constructor
comment:12 Changed 11 years ago by
(In r102) Re #61 - Complete structure of WarFoundry API objects
- Make Unit work with EquipmentItem objects as it doesn't need to know about the limits
- Add methods to UnitType to check limits on an EquipmentItem
Also:
- Remove some unnecessary casting now that we're using genericed lists
comment:13 Changed 11 years ago by
(In r103) Re #61 - Complete structure of WarFoundry API objects
- Add parent links to Units (inverse of r97)
comment:14 Changed 11 years ago by
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Closing - we seem to have everything so far.
comment:15 Changed 11 years ago by
comment:16 Changed 11 years ago by
comment:18 Changed 10 years ago by
released: | 1 → yes |
---|
Mark released fixes as released using radio values
comment:19 Changed 10 years ago by
Resolution: | fixed → released |
---|
Mark fix as released under a previous version
(In r89) Re #61 - Complete structure of WarFoundry API objects
Re #9 - Use smaller methods
Also: