Component databases - Revision history

73.171.159.186: /* Introduction */

2020-10-10T13:41:48Z

Introduction

← Older revision		Revision as of 13:41, 10 October 2020
Line 3:		Line 3:
	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.

	Currently in OpenRocket, details about rocket components must be entered by hand every time a rocket is designed. For example, when a body tube is added both the inner diameter, outer diameter, and material need to be specified. However, many of the rocket components generally used are standard commercial items whose design specifications are already ~~know~~. It would be useful to allow OpenRocket users to, for example, select a body tube by manufacturer and type, and only have to specify the variable dimensions: ie, select an Estes BT-60 tube (which will set the tube dimensions and material), then specify a length of 50 cm.		Currently in OpenRocket, details about rocket components must be entered by hand every time a rocket is designed. For example, when a body tube is added both the inner diameter, outer diameter, and material need to be specified. However, many of the rocket components generally used are standard commercial items whose design specifications are already known. It would be useful to allow OpenRocket users to, for example, select a body tube by manufacturer and type, and only have to specify the variable dimensions: ie, select an Estes BT-60 tube (which will set the tube dimensions and material), then specify a length of 50 cm.

	== OpenRocket Component (.orc) XML File Format ==		== OpenRocket Component (.orc) XML File Format ==

182.253.52.186 at 08:48, 23 May 2014

2014-05-23T08:48:37Z

← Older revision		Revision as of 08:48, 23 May 2014
Line 27:		Line 27:
	==== Import and Export Tools for the OpenRocket Component Format ====		==== Import and Export Tools for the OpenRocket Component Format ====

	Component data will somehow have to converted into ORC XML files, either by the manufacturers themselves or hobby volunteers. It is unreasonable to expect that manufacturer's staff or hobbyists will have the expertise and time to hand-code component XML files. It is more likely that intermediate spreadsheet files will be created with component data. Therefore, we will need a utility to convert both ways between the ORC XML format and standard comma-separated (CSV) value spreadsheet files.		Component data will somehow have to converted into ORC XML files, either by the manufacturers themselves or hobby volunteers. It is unreasonable to expect that manufacturer's staff or hobbyists will have the expertise and time to hand-code component XML files. It is more likely that intermediate spreadsheet files will be created with component data. Therefore, we will need a utility to convert both ways between the ORC XML format and standard comma-separated (CSV) value spreadsheet files [http://digiadvertise.wordpress.com/2014/04/07/jasa-seo-di-jakarta Jasa seo], [http://digiadvertise.wordpress.com/2014/04/07/jasa-seo-di-jakarta Jasa seo jakarta], [http://andreweweww.wordpress.com/2014/01/19/lovely-mwo-muslim-wedding-organizer Wedding organizer].

	The import/export utility could be built into the OpenRocket software itself, or could be a separate program.		The import/export utility could be built into the OpenRocket software itself, or could be a separate program.

Soupwizard: /* Introduction */

2013-06-09T23:22:40Z

Introduction

← Older revision		Revision as of 23:22, 9 June 2013
Line 5:		Line 5:
	Currently in OpenRocket, details about rocket components must be entered by hand every time a rocket is designed. For example, when a body tube is added both the inner diameter, outer diameter, and material need to be specified. However, many of the rocket components generally used are standard commercial items whose design specifications are already know. It would be useful to allow OpenRocket users to, for example, select a body tube by manufacturer and type, and only have to specify the variable dimensions: ie, select an Estes BT-60 tube (which will set the tube dimensions and material), then specify a length of 50 cm.		Currently in OpenRocket, details about rocket components must be entered by hand every time a rocket is designed. For example, when a body tube is added both the inner diameter, outer diameter, and material need to be specified. However, many of the rocket components generally used are standard commercial items whose design specifications are already know. It would be useful to allow OpenRocket users to, for example, select a body tube by manufacturer and type, and only have to specify the variable dimensions: ie, select an Estes BT-60 tube (which will set the tube dimensions and material), then specify a length of 50 cm.

	== OpenRocket Component (.orc) XML File Format		== OpenRocket Component (.orc) XML File Format ==

	XML format for storing component databases: [[Component database XML format]]		XML format for storing component databases: [[Component database XML format]]

Soupwizard at 23:22, 9 June 2013

2013-06-09T23:22:22Z

← Older revision		Revision as of 23:22, 9 June 2013
Line 4:		Line 4:

	Currently in OpenRocket, details about rocket components must be entered by hand every time a rocket is designed. For example, when a body tube is added both the inner diameter, outer diameter, and material need to be specified. However, many of the rocket components generally used are standard commercial items whose design specifications are already know. It would be useful to allow OpenRocket users to, for example, select a body tube by manufacturer and type, and only have to specify the variable dimensions: ie, select an Estes BT-60 tube (which will set the tube dimensions and material), then specify a length of 50 cm.		Currently in OpenRocket, details about rocket components must be entered by hand every time a rocket is designed. For example, when a body tube is added both the inner diameter, outer diameter, and material need to be specified. However, many of the rocket components generally used are standard commercial items whose design specifications are already know. It would be useful to allow OpenRocket users to, for example, select a body tube by manufacturer and type, and only have to specify the variable dimensions: ie, select an Estes BT-60 tube (which will set the tube dimensions and material), then specify a length of 50 cm.

			== OpenRocket Component (.orc) XML File Format

			XML format for storing component databases: [[Component database XML format]]

	== Functionality To Be Built ==		== Functionality To Be Built ==

Sampo Niskanen: 17 revisions: Import existing wiki English pages

2013-02-15T21:17:00Z

17 revisions: Import existing wiki English pages

← Older revision	Revision as of 21:17, 15 February 2013
(No difference)

Plaa: /* OpenRocket Component (ORC) Format */ comment

2011-10-08T19:24:23Z

OpenRocket Component (ORC) Format: comment

← Older revision		Revision as of 19:24, 8 October 2011
Line 18:		Line 18:

	The initial specification of the XML fields and structure can be generated by looking at the ORK rocket design format for what it stores for parts data.		The initial specification of the XML fields and structure can be generated by looking at the ORK rocket design format for what it stores for parts data.

			''Should the component db extension be tied to OpenRocket (ORC)? Ideally the format would be adopted by other software as well... [[User:Plaa\|Plaa]] 19:24, 8 October 2011 (UTC)''

	==== Import and Export Tools for the OpenRocket Component Format ====		==== Import and Export Tools for the OpenRocket Component Format ====

Soupwizard at 07:28, 30 August 2011

2011-08-30T07:28:08Z

← Older revision		Revision as of 07:28, 30 August 2011
Line 53:		Line 53:
	** From an online connection to the library web api		** From an online connection to the library web api
	** From a snapshot set of updated ORC files, for users who do not have internet access (for example, out at a launch site).		** From a snapshot set of updated ORC files, for users who do not have internet access (for example, out at a launch site).
			* Allow creation and uploading of custom components

	== Software Design ==		== Software Design ==

Soupwizard at 07:27, 30 August 2011

2011-08-30T07:27:02Z

← Older revision		Revision as of 07:27, 30 August 2011
Line 9:		Line 9:
	The functionality needed to support the above use case can be broken down into the following:		The functionality needed to support the above use case can be broken down into the following:

	=== OpenRocket Component (ORC) Format ===		=== Phase 1 ===

			==== OpenRocket Component (ORC) Format ====

	An open and extensible standard for specifying all relevant details about rocket components. The obvious choice is an XML format. OpenRocket will need to be able to read and write this format.		An open and extensible standard for specifying all relevant details about rocket components. The obvious choice is an XML format. OpenRocket will need to be able to read and write this format.
Line 17:		Line 19:
	The initial specification of the XML fields and structure can be generated by looking at the ORK rocket design format for what it stores for parts data.		The initial specification of the XML fields and structure can be generated by looking at the ORK rocket design format for what it stores for parts data.

	=== Import and Export Tools for the OpenRocket Component Format ===		==== Import and Export Tools for the OpenRocket Component Format ====

	Component data will somehow have to converted into ORC XML files, either by the manufacturers themselves or hobby volunteers. It is unreasonable to expect that manufacturer's staff or hobbyists will have the expertise and time to hand-code component XML files. It is more likely that intermediate spreadsheet files will be created with component data. Therefore, we will need a utility to convert both ways between the ORC XML format and standard comma-separated (CSV) value spreadsheet files.		Component data will somehow have to converted into ORC XML files, either by the manufacturers themselves or hobby volunteers. It is unreasonable to expect that manufacturer's staff or hobbyists will have the expertise and time to hand-code component XML files. It is more likely that intermediate spreadsheet files will be created with component data. Therefore, we will need a utility to convert both ways between the ORC XML format and standard comma-separated (CSV) value spreadsheet files.

	The import/export utility could be built into the OpenRocket software itself, or could be a separate program.		The import/export utility could be built into the OpenRocket software itself, or could be a separate program.

			==== Modifications to OpenRocket Client ====

			Changes needed to the OpenRocket application to make use of the component functionality:

			* OpenRocket must support reading and writing of ORC XML files.
			* Store all component data outside the program code (ie, in ORC XML files).
			* Don't allow user to modify or overwrite standard OpenRocket supported part, instead allow user to copy, modify, and store new customized parts.
			* When user chooses to add a part to a design, allow user to pick one from the component library, or to create a new part using the existing parts specification UI.

			=== Phase 2 ===

	=== Online Library of OpenRocket Components ===		=== Online Library of OpenRocket Components ===

	A useful feature for OpenRocket users would be an online library of OpenRocket component files, a canonical location for the latest version of component files. This would allow the OpenRocket software to obtain the latest component files via the internet.		A useful feature for OpenRocket users would be an online library of OpenRocket component files, a canonical location for the latest version of component files. This would allow the OpenRocket software to obtain the latest component files via the internet, and provide both a web UI for people to view the library, and a web api to allow software to update or retrieve component info.

	In addition to commercial rocket components, the library could store non-commercial components, such as combinations of components that form a larger useful piece. For example, an ejection baffle can be created from 3 smaller components: a tube coupler and 2 thin bulkheads with holes drilled in the in various patterns.		In addition to commercial rocket components, the library could store non-commercial components, such as combinations of components that form a larger useful piece. For example, an ejection baffle can be created from 3 smaller components: a tube coupler and 2 thin bulkheads with holes drilled in the in various patterns.
Line 35:		Line 48:
	Potential messiness: someone will have to maintain the library. Maybe divide the library between official OpenRocket supported components (data from manufacturers, approved submitters and/or rocketry clubs, etc), and a general open-upload section.		Potential messiness: someone will have to maintain the library. Maybe divide the library between official OpenRocket supported components (data from manufacturers, approved submitters and/or rocketry clubs, etc), and a general open-upload section.

	=== ~~Changes~~ to OpenRocket ~~Program~~ ===		==== Modifications to OpenRocket Client ====

	~~Changes needed to the OpenRocket application to make use of the above new functionality:~~

	* OpenRocket must support reading and writing of ORC XML files.		* Allow updating of component files from the OpenRocket component library:
	* Store all component data outside the program code (ie, in ORC XML files).		** From an online connection to the library web api
	* Allow updating of component files from the OpenRocket component library ~~(or from~~ a snapshot set of updated ORC files, for users who do not have internet access).		** From a snapshot set of updated ORC files, for users who do not have internet access (for example, out at a launch site).
	* Don't allow user to modify or overwrite standard OpenRocket supported part, instead allow user to copy, modify, and store new customized parts.
	* When user chooses to add a part to a design, ~~allow user to pick one from the component library, or to create~~ a ~~new part using the existing parts specification UI~~.

	== Software Design ==		== Software Design ==

Soupwizard: /* Functionality To Be Built */

2011-08-28T08:58:38Z

Functionality To Be Built

← Older revision		Revision as of 08:58, 28 August 2011
Line 14:		Line 14:

	The format could also allow non-structural components such as rocket motors, wadding or nomex sheets for recovery device protection, etc - any item that is attached to a rocket.		The format could also allow non-structural components such as rocket motors, wadding or nomex sheets for recovery device protection, etc - any item that is attached to a rocket.

			The initial specification of the XML fields and structure can be generated by looking at the ORK rocket design format for what it stores for parts data.

	=== Import and Export Tools for the OpenRocket Component Format ===		=== Import and Export Tools for the OpenRocket Component Format ===

Soupwizard at 08:54, 28 August 2011

2011-08-28T08:54:06Z

← Older revision		Revision as of 08:54, 28 August 2011
Line 40:		Line 40:
	* Store all component data outside the program code (ie, in ORC XML files).		* Store all component data outside the program code (ie, in ORC XML files).
	* Allow updating of component files from the OpenRocket component library (or from a snapshot set of updated ORC files, for users who do not have internet access).		* Allow updating of component files from the OpenRocket component library (or from a snapshot set of updated ORC files, for users who do not have internet access).
	* Don't allow user to modify or overwrite of standard ~~parts files~~, instead allow user to copy, modify, and store customized parts.		* Don't allow user to modify or overwrite standard OpenRocket supported part, instead allow user to copy, modify, and store new customized parts.
	* When user chooses to add a part to a design, allow user to pick one from the component library, or to create a new part using the existing parts specification UI.		* When user chooses to add a part to a design, allow user to pick one from the component library, or to create a new part using the existing parts specification UI.