Opened 11 years ago
Last modified 9 years ago
#66 confirmed task
Separate XML file loader out as a seperate project
Reported by: | ibboard | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | WarFoundry-API | Version: | |
Keywords: | Cc: | ||
Blocked By: | Blocking: | #65, #67 |
Description
The XML file loader should be broken out in to its own project, along with custom classes that extend the main "staged loading" classes. This would let us add custom "XML in a zip file" behaviour, as would be necessary for #65.
Change History (6)
comment:1 Changed 11 years ago by
Blocking: | 67 added |
---|
comment:2 Changed 11 years ago by
Owner: | ibboard deleted |
---|
comment:3 Changed 10 years ago by
Milestone: | WarFoundry 0.1 → WarFoundry 0.2 |
---|
Migrate to WarFoundry 0.2, since it isn't an important "first release" requirement.
comment:4 Changed 10 years ago by
Milestone: | WarFoundry 0.2 → WarFoundry 0.3 |
---|
Move plugin tickets to v0.3
comment:5 Changed 10 years ago by
Status: | new → confirmed |
---|
Move tickets to new "confirmed" status to show that they've been checked
Note: See
TracTickets for help on using
tickets.
Remove owner so that the team can more easily see bugs. Using default owners seems good at first but is bad practice when a team can be working on any part of the project.