Difference between revisions of "Component databases"

From OpenRocket wiki
Jump to navigation Jump to search
(initial design)
 
Line 1: Line 1:
 +
== Introduction ==
 +
 
This page is for planning the implementation of component databases in OpenRocket and splitting the implementation into smaller tasks.
 
This page is for planning the implementation of component databases in OpenRocket and splitting the implementation into smaller tasks.
  
 +
== Use Cases ==
 +
 +
 +
== Software Design ==
 +
 +
 +
=== Tasks ===
  
 
* Design XML format for storing component databases:  [[Component database XML format]]
 
* Design XML format for storing component databases:  [[Component database XML format]]

Revision as of 10:25, 28 August 2011

Introduction

This page is for planning the implementation of component databases in OpenRocket and splitting the implementation into smaller tasks.

Use Cases

Software Design

Tasks

  • Implement framework for using standard components
    • RocketComponentPreset class?
    • loadPreset(PresetComponent) method in RocketComponent?
    • Remember what is used as a preset component
    • When changing critical variables preset component is cleared (e.g. diameter of body tube), but not when changing others (e.g. length of body tube)
  • Implement database for storing standard components
    • Maintain user-selectable presets list (user can choose which components are in an easy-to-access presets list)
  • Implement methods for reading XML format
  • Implement methods for reading CSV format
  • Implement GUI for component selection
    • Preset dropdown
    • Button for opening selection dialog
    • Dialog allows selecting which components are displayed in the preset list
  • Implement GUI for creating components(?)
    • Useful for manufacturers
  • How to store the preset info in ORK file? Should the entire preset info be included, or just a digest that is used in case the preset is already loaded and available?