SDSX Requirements - Revision history

BASys at 19:41, 4 January 2008

2008-01-04T19:41:37Z

← Older revision		Revision as of 14:41, 4 January 2008
Line 96:		Line 96:
	* managed NET libraries		* managed NET libraries
	* avoid using COM based		* avoid using COM based

			[[category:FSX]]

Arno at 05:43, 12 November 2007

2007-11-12T05:43:31Z

← Older revision		Revision as of 00:43, 12 November 2007
Line 96:		Line 96:
	* managed NET libraries		* managed NET libraries
	* avoid using COM based		* avoid using COM based

	~~[[category:Scenery design]]~~

135.196.161.66: /* Objective */ - added tweaking of 3D models - more tweaks should probably be added

2006-10-09T11:36:57Z

Objective: - added tweaking of 3D models - more tweaks should probably be added

← Older revision		Revision as of 06:36, 9 October 2006
Line 35:		Line 35:
	* operate in either a stand alone mode or in client/server mode for co-operative working with design teams		* operate in either a stand alone mode or in client/server mode for co-operative working with design teams
	* be flexible in design so that new objects, simple or compound can be added without the need to change or re-compile the base program. These should be addable by using plug-in components		* be flexible in design so that new objects, simple or compound can be added without the need to change or re-compile the base program. These should be addable by using plug-in components
			* Allow teaking of 3D objects
			** Automatically create LoD
			** Seasonal texture (can be part of general texture tweaks supporting renaming, adding or removing night maps etc).
			** Convert polygons to ground polygons (FS2002 style or FSX ground textures now resolution can be OK)
			** Add or remove shadows from parts of an object

	==Target Audience==		==Target Audience==

Scruffyduck: /* Target Audience */

2006-10-06T21:27:44Z

Target Audience

← Older revision		Revision as of 16:27, 6 October 2006
Line 37:		Line 37:

	==Target Audience==		==Target Audience==
	* The tool should be usable by a wide range of users from casual to scenery design teams.		* The tool should be usable by a wide range of users from casual to scenery design teams.
			* It should also be usuable by AI Traffic Designers.

	==Target Sim==		==Target Sim==

Scruffyduck at 21:26, 6 October 2006

2006-10-06T21:26:16Z

← Older revision		Revision as of 16:26, 6 October 2006
Line 8:		Line 8:
	Draft Version 0.2 (Sept 30, 2006)		Draft Version 0.2 (Sept 30, 2006)

	~~WORKING NAME~~		==Working Name==
	* Scenery Design Studio X [SDSX]		* Scenery Design Studio X [SDSX]

	~~PROGRAM LICENSE~~		==Program License==
	* Freeware		* Freeware

	~~DEVELOPER~~		==Developer==
	* FSDevelopers.com		* FSDevelopers.com

	~~INTRODUCTION~~		==Introduction==
	This is a new Scenery Design Tool for use with FSX. It is being developed on a co-operative basis by members of FSDevelopers.com.		This is a new Scenery Design Tool for use with FSX. It is being developed on a co-operative basis by members of FSDevelopers.com.

	It is expected to be a multi phase development and this description covers Phase 1. Future extensions such as adding new scenery elements should be possible via plug-in technology. These would include land class, mesh etc		It is expected to be a multi phase development and this description covers Phase 1. Future extensions such as adding new scenery elements should be possible via plug-in technology. These would include land class, mesh etc

	~~OBJECTIVE~~		==Objective==
	To develop a Scenery Design Tool with the ability to:		To develop a Scenery Design Tool with the ability to:
	* read FS9 and FSX XML based scenery BGLs		* read FS9 and FSX XML based scenery BGLs
Line 36:		Line 36:
	* be flexible in design so that new objects, simple or compound can be added without the need to change or re-compile the base program. These should be addable by using plug-in components		* be flexible in design so that new objects, simple or compound can be added without the need to change or re-compile the base program. These should be addable by using plug-in components

	~~TARGET AUDIENCE~~		==Target Audience==
	* The tool should be usable by a wide range of users from casual to scenery design teams.		* The tool should be usable by a wide range of users from casual to scenery design teams.

	~~TARGET SIM~~		==Target Sim==
	* FSX		* FSX

	~~INPUT FORMATS~~		==Input Formats==
	* FS9 and FSX bgl and mdl		* FS9 and FSX bgl and mdl
	* Shape Files		* Shape Files
	* GIS Data		* GIS Data

	~~OUTPUT FORMATS~~		==Output Formats==
	* The program needs to be able to generate FSX Scenery BGL Files		* The program needs to be able to generate FSX Scenery BGL Files
	* It may also generate XML or other format output if required and useful		* It may also generate XML or other format output if required and useful

	~~DATA STORAGE FORMAT~~		==Data Storage Formats==
	* To be agreed		* To be agreed

	~~USER INTERFACE~~		==User Interface==
	* In this phase it will provide a 2D top down GUI using the Visual Studio IDE as a model		* In this phase it will provide a 2D top down GUI using the Visual Studio IDE as a model
	Scenery objects/elements in toolboxes with drag and drop to the work area		Scenery objects/elements in toolboxes with drag and drop to the work area
Line 60:		Line 60:
	A 3D interface would be expected as part of a later phase		A 3D interface would be expected as part of a later phase

	~~DESIGN PHILOSOPHY~~/~~PATTERNS~~		=Tools, Design Standards, etc.=

			==Design Philosophy/Patterns==
	* Microsoft Smart Client Factory based Client		* Microsoft Smart Client Factory based Client
	* Separation of GUI from Data using the Model View Presenter (MVP) Pattern		* Separation of GUI from Data using the Model View Presenter (MVP) Pattern
Line 66:		Line 68:
	* Extensions to the program for new/additional scenery object types via plug ins which will require an SDK. It should also be possible to add new compiler/decompiler options via plug-ins		* Extensions to the program for new/additional scenery object types via plug ins which will require an SDK. It should also be possible to add new compiler/decompiler options via plug-ins

	~~TOOLS, DESIGN STRANDARDS. PLATFORM ETC~~		==Tools==

	~~TOOLS~~
	* IDE – minimum C# Express		* IDE – minimum C# Express
	* Standards - FXCop		* Standards - FXCop
Line 74:		Line 74:
	* Testing - ??		* Testing - ??

	~~DESIGN PLATFORM~~		==Design Platform==
	* dotNet 2.0 or 3.0		* dotNet 2.0 or 3.0

	~~OPERATING SYSTEM~~		==Operating System==
	* minimum requirements – XP SP2 Home Edition		* minimum requirements – XP SP2 Home Edition

	~~PRIMARY DESIGN LANGUAGE~~		==Primary Design Language==
	* C# although plug-in modules and self contained parts of the program could be created in any CLR compliant language and compiled to dlls (i.e must be managed)		* C# although plug-in modules and self contained parts of the program could be created in any CLR compliant language and compiled to dlls (i.e must be managed)
	Display handled by (choice of GDI+, DirectX, OpenGL OR WPF)		Display handled by (choice of GDI+, DirectX, OpenGL OR WPF)

	~~DESIGN STANDARDS~~		==Design Standards==
	* Microsoft Standards as embodied in FXCop - rules to be defined		* Microsoft Standards as embodied in FXCop - rules to be defined

	~~COMPONENTS~~		==Components==
	* managed NET libraries		* managed NET libraries
	* avoid using COM based		* avoid using COM based

	[[category:Scenery design]]		[[category:Scenery design]]

Scruffyduck: Second Draft

2006-10-05T12:38:41Z

Second Draft

← Older revision		Revision as of 07:38, 5 October 2006
Line 2:		Line 2:


	'''~~FIRST~~ DRAFT DESCRIPTION FOR NEW SCENERY DESIGN TOOL'''		'''SECOND DRAFT DESCRIPTION FOR NEW SCENERY DESIGN TOOL'''

	~~WORKING NAME: Scenery Design Studio X [SDSX]~~

	~~DESIGN PLATFORM: dotNet 2.0~~

			Draft Version 0.2 (Sept 30, 2006)

	~~PRIMARY DESIGN LANGUAGE: C# (although plug-in modules and self contained parts of the program could be created in any CLR compliant language and compiled to dlls)~~		WORKING NAME
			* Scenery Design Studio X [SDSX]

	PROGRAM LICENSE: Freeware		PROGRAM LICENSE
			* Freeware

	~~This covers a Phase 1 tool~~. ~~- Future extensions such as adding new scenery elements should be possible via plug-in technology. These would include land class, mesh etc~~		DEVELOPER
			* FSDevelopers.com

	OBJECTIVE:		INTRODUCTION
			This is a new Scenery Design Tool for use with FSX. It is being developed on a co-operative basis by members of FSDevelopers.com.

			It is expected to be a multi phase development and this description covers Phase 1. Future extensions such as adding new scenery elements should be possible via plug-in technology. These would include land class, mesh etc

			OBJECTIVE
	To develop a Scenery Design Tool with the ability to:		To develop a Scenery Design Tool with the ability to:

	* read FS9 and FSX XML based scenery BGLs		* read FS9 and FSX XML based scenery BGLs
	* enable users to view, modify and create FSX scenery in a graphical environment using drag and drop techniques.		* enable users to view, modify and create FSX scenery in a graphical environment using drag and drop techniques.
	* handle all existing FS9 and FSX XML based objects and effects		* handle all existing FS9 and FSX XML based objects and effects
	* create 'compound objects' such as fence lines, area fills and so on.		* create 'compound objects' such as fence lines, area fills and so on.
	* ~~Display~~ background images		* display background images
	* ~~Display~~ background geographical information (road, rail, coastlines, elevation data etc) either by reading from the Sim or from GIS data Sources.		* display background geographical information (road, rail, coastlines, elevation data etc) either by reading from the Sim or from GIS data Sources.
	* be flexible in design so that new objects, simple or compound can be added without the need to change or re-compile the base program. These should be addable by using plug-in components
	* compile and deploy FSX scenery bgls.		* compile and deploy FSX scenery bgls.
	* provide analysis tools related to scenery		* provide analysis tools related to scenery
	* manage object libraries		* manage object libraries
	* ~~Operate~~ in either a stand alone mode or in client/server mode for co-operative working with design teams		* operate in either a stand alone mode or in client/server mode for co-operative working with design teams
			* be flexible in design so that new objects, simple or compound can be added without the need to change or re-compile the base program. These should be addable by using plug-in components

			TARGET AUDIENCE
			* The tool should be usable by a wide range of users from casual to scenery design teams.

			TARGET SIM
			* FSX

			INPUT FORMATS
			* FS9 and FSX bgl and mdl
			* Shape Files
			* GIS Data

			OUTPUT FORMATS
			* The program needs to be able to generate FSX Scenery BGL Files
			* It may also generate XML or other format output if required and useful

			DATA STORAGE FORMAT
			* To be agreed

			USER INTERFACE
			* In this phase it will provide a 2D top down GUI using the Visual Studio IDE as a model
			Scenery objects/elements in toolboxes with drag and drop to the work area
			objects parameters using property lists.
			A 3D interface would be expected as part of a later phase

			DESIGN PHILOSOPHY/PATTERNS
			* Microsoft Smart Client Factory based Client
			* Separation of GUI from Data using the Model View Presenter (MVP) Pattern
			* Observer Pattern for interaction between objects
			* Extensions to the program for new/additional scenery object types via plug ins which will require an SDK. It should also be possible to add new compiler/decompiler options via plug-ins

	~~TARGET AUDIENCE: Cater for casual as well as power users~~		TOOLS, DESIGN STRANDARDS. PLATFORM ETC

	~~TARGET SIM: FSX~~		TOOLS
			* IDE – minimum C# Express
			* Standards - FXCop
			* Documentation - ??
			* Testing - ??

	~~INPUT FORMATS: FS9, FSX, Shape Files, GIS Data~~		DESIGN PLATFORM
			* dotNet 2.0 or 3.0

	~~OUTPUT FORMATS: FSX (May also include an XML output)~~		OPERATING SYSTEM
			* minimum requirements – XP SP2 Home Edition

	~~DATA STORAGE FORMAT: To~~ be ~~agreed~~		PRIMARY DESIGN LANGUAGE
			* C# although plug-in modules and self contained parts of the program could be created in any CLR compliant language and compiled to dlls (i.e must be managed)
			Display handled by (choice of GDI+, DirectX, OpenGL OR WPF)

	~~USER INTERFACE: 2D top down GUI using the Visual Studio IDE~~ as ~~a model enabling drag and drop from toolboxes, creation of objects parameters using property lists and so on.~~		DESIGN STANDARDS
			* Microsoft Standards as embodied in FXCop - rules to be defined

	~~A 3D interface would be expected as part of a later phase~~		COMPONENTS
			* managed NET libraries
			* avoid using COM based

	[[category:Scenery design]]		[[category:Scenery design]]

Scruffyduck at 12:29, 5 October 2006

2006-10-05T12:29:18Z

← Older revision		Revision as of 07:29, 5 October 2006
Line 44:		Line 44:
	A 3D interface would be expected as part of a later phase		A 3D interface would be expected as part of a later phase

	[[~~Category~~:~~Manuals~~]]		[[category:Scenery design]]

Wikiadmin at 20:04, 2 October 2006

2006-10-02T20:04:20Z

← Older revision		Revision as of 15:04, 2 October 2006
Line 43:		Line 43:

	A 3D interface would be expected as part of a later phase		A 3D interface would be expected as part of a later phase

			[[Category:Manuals]]

Arno: Improved formatting

2006-09-29T17:40:27Z

Improved formatting

← Older revision		Revision as of 12:40, 29 September 2006
Line 18:		Line 18:
	To develop a Scenery Design Tool with the ability to:		To develop a Scenery Design Tool with the ability to:

	- read FS9 and FSX XML based scenery BGLs		* read FS9 and FSX XML based scenery BGLs
			* enable users to view, modify and create FSX scenery in a graphical environment using drag and drop techniques.
	- enable users to view, modify and create FSX scenery in a graphical environment using drag and drop techniques.		* handle all existing FS9 and FSX XML based objects and effects
			* create 'compound objects' such as fence lines, area fills and so on.
	- handle all existing FS9 and FSX XML based objects and effects		* Display background images
			* Display background geographical information (road, rail, coastlines, elevation data etc) either by reading from the Sim or from GIS data Sources.
	- create 'compound objects' such as fence lines, area fills and so on.		* be flexible in design so that new objects, simple or compound can be added without the need to change or re-compile the base program. These should be addable by using plug-in components
			* compile and deploy FSX scenery bgls.
	- Display background images		* provide analysis tools related to scenery
			* manage object libraries
	- Display background geographical information (road, rail, coastlines, elevation data etc) either by reading from the Sim or from GIS data Sources.		* Operate in either a stand alone mode or in client/server mode for co-operative working with design teams

	- be flexible in design so that new objects, simple or compound can be added without the need to change or re-compile the base program. These should be addable by using plug-in components

	- compile and deploy FSX scenery bgls.

	- provide analysis tools related to scenery

	- manage object libraries

	- Operate in either a stand alone mode or in client/server mode for co-operative working with design teams

	TARGET AUDIENCE: Cater for casual as well as power users		TARGET AUDIENCE: Cater for casual as well as power users

Scruffyduck: First Wiki Version

2006-09-29T17:31:59Z

First Wiki Version

← Older revision		Revision as of 12:31, 29 September 2006
Line 7:		Line 7:

	DESIGN PLATFORM: dotNet 2.0		DESIGN PLATFORM: dotNet 2.0


	PRIMARY DESIGN LANGUAGE: C# (although plug-in modules and self contained parts of the program could be created in any CLR compliant language and compiled to dlls)		PRIMARY DESIGN LANGUAGE: C# (although plug-in modules and self contained parts of the program could be created in any CLR compliant language and compiled to dlls)

	PROGRAM LICENSE: Freeware		PROGRAM LICENSE: Freeware

Line 40:		Line 43:

	TARGET SIM: FSX		TARGET SIM: FSX

	INPUT FORMATS: FS9, FSX, Shape Files, GIS Data		INPUT FORMATS: FS9, FSX, Shape Files, GIS Data

	OUTPUT FORMATS: FSX (May also include an XML output)		OUTPUT FORMATS: FSX (May also include an XML output)

	DATA STORAGE FORMAT: To be agreed		DATA STORAGE FORMAT: To be agreed