Difference between revisions of "Launcher Planning List"
Jump to navigation
Jump to search
Sylph Knight (talk | contribs) |
|||
Line 7: | Line 7: | ||
==List of Development Milestones== | ==List of Development Milestones== | ||
*Settle on whether to continue existing launcher, or migrate to another programming language. | *Settle on whether to continue existing launcher, or migrate to another programming language. | ||
+ | **Ease-of-entry to develop the software should be a priority to resolve limitations with available developers. | ||
+ | **Issues with Sunrise are that there may be a lack of experience surrounding Python with QT to continue development. | ||
==List of Requirements== | ==List of Requirements== |
Revision as of 17:43, 14 November 2019
Contents
Preliminary Requirements
- Verify and outline replacement for Manifests.
- TCP ACK is the current methodology being explored.
- Verify any additional server-side requirements that must be developed to work with this data management model.
- Settle on launcher's server list management methodology.
List of Development Milestones
- Settle on whether to continue existing launcher, or migrate to another programming language.
- Ease-of-entry to develop the software should be a priority to resolve limitations with available developers.
- Issues with Sunrise are that there may be a lack of experience surrounding Python with QT to continue development.
List of Requirements
- Launcher "must" be in the same directory as the game executable. Forcing this as a standard will resolve several problems with administrative rights requirements previously seen in earlier launchers.
Tertiary Goals
- User interface layout and design requirements.
- Detailed view of transfer speeds
- Detailed view of progress
- Confirm and work around compatibility problems across OS platforms.
- Meaningful Error messages
- Detailed messages will help with troubleshooting experience