SASTEP: Difference between revisions
From Step Mods | Change The Game
(#milestones for semi automatic installer) |
|||
Line 1: | Line 1: | ||
==Semi Automatic STEP Tool== | ==Semi Automatic STEP Tool== | ||
===Milestones=== | ===Milestones=== | ||
Milestones for the proof-of-concept-tools that will set the base for a complete installation program/ MO plugin etc. Once we are done with betatesting there should be a reset to an alpha that will incorporate all (probably) separated tools. | Milestones for the proof-of-concept-tools that will set the base for a complete installation program/ MO plugin etc. Once we are done with betatesting there should be a reset to an alpha that will incorporate all (probably) separated tools into a unified codebase. | ||
*Alpha state: | *Alpha state: |
Revision as of 16:44, November 27, 2013
Semi Automatic STEP Tool
Milestones
Milestones for the proof-of-concept-tools that will set the base for a complete installation program/ MO plugin etc. Once we are done with betatesting there should be a reset to an alpha that will incorporate all (probably) separated tools into a unified codebase.
- Alpha state:
- Define and assemble a list of all archives (filename and checksum) that'll be used for the STEP core installation (WIP)
- (parallel to #1) get a working tool that returns the changed filestructure as config file for MG's ASI.
- (needs #2)
- install all mods according to the STEP core guide (+ our definition of STEP core)
- run the tool from #2. Adjust the tool if necessary
- Milestone is reached once all config files for STEP core are completed.
- create a tool that installs STEP core in separate folders.
- A simple batch file (for now) will just copy them all together for testing / or we create a switch in the ASI tool
- Bundle it all in one toolkit / one downloadable zip file.
- documentation
- bugfixing, catch errors/exceptions
- Beta state:
- let the community give feedback and suggestions.
later/not time critical, yet:
- a: define how data should be imported into the wiki (filelists for each mod? file archive based?)
- 1: import data into the STEP wiki; make it editable for mod authors
- 2: create a query that returns data ready for our tool
- b: MO metafile-write support (have to check if I already got this working)
- 1: a function that will edit the metas after the installation is complete
- c: get a version control up and running