Orbiter refactoring - the new design - Revision history

Wierdbeard65 at 15:55, 5 May 2010

2010-05-05T15:55:50Z

←Older revision		Revision as of 15:55, 5 May 2010
Line 1:		Line 1:
			{{versioninfo}}
	== Orbiter Renderers ==		== Orbiter Renderers ==

Lozzo at 03:06, 1 October 2007

2007-10-01T03:06:09Z

←Older revision		Revision as of 03:06, 1 October 2007
Line 70:		Line 70:

	NOTE: The datagrid renderers are passive objects. They cannot handle users input events by themselves. Another step in refactoring process will be needed in order to accomplish this.		NOTE: The datagrid renderers are passive objects. They cannot handle users input events by themselves. Another step in refactoring process will be needed in order to accomplish this.

			[[Category:Orbiters]]

Juliet at 08:34, 19 March 2007

2007-03-19T08:34:30Z

←Older revision		Revision as of 08:34, 19 March 2007
Line 1:		Line 1:
	<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>== Orbiter Renderers ==		== Orbiter Renderers ==

	=== General information ===		=== General information ===

Jerry finn at 08:39, 16 March 2007

2007-03-16T08:39:25Z

←Older revision		Revision as of 08:39, 16 March 2007
Line 9:		Line 9:


	~~PlutoGraphic~~ class is isolated in a new h/cpp since it’s not directly related to DesignObj_Orbiter class.		LinuxMCE Graphic class is isolated in a new h/cpp since it’s not directly related to DesignObj_Orbiter class.


Line 46:		Line 46:


	The AnimatedDatagridRenderer is not implemented now, only DatagridRenderer which has the same behavior as the one we are using today. Additionally, we are using now a custom datagrid for Bluetooth_Dongle : DataGridRenderer_Bluetooth (which does extra things on overriden RenderObject method) and one for Proxy_Orbiter : DataGridRenderer_Proxy.cpp (RenderCell is ~~overriden~~ in order to create the xml with touch zones for datagrid's cells).		The AnimatedDatagridRenderer is not implemented now, only DatagridRenderer which has the same behavior as the one we are using today. Additionally, we are using now a custom datagrid for Bluetooth_Dongle : DataGridRenderer_Bluetooth (which does extra things on overriden RenderObject method) and one for Proxy_Orbiter : DataGridRenderer_Proxy.cpp (RenderCell is overridden in order to create the xml with touch zones for datagrid's cells).

Wikiadmin at 08:52, 7 June 2006

2006-06-07T08:52:24Z

←Older revision		Revision as of 08:52, 7 June 2006
Line 50:		Line 50:

	[[Image:Orbiter_refactor_Object_Renderer.png]]		[[Image:Orbiter_refactor_Object_Renderer.png]]


	=== DataGridRenderer class ===		=== DataGridRenderer class ===

Wikiadmin at 08:51, 7 June 2006

2006-06-07T08:51:41Z

←Older revision		Revision as of 08:51, 7 June 2006
Line 30:		Line 30:


	=== Orbiter creation and destruction		=== Orbiter creation and destruction ===

	Here's a sequence diagram. Orbiter's framework thread should be handled by the framework. Additional threads like OpenGL's thread will be handled (created/destroyed) in OrbiterRenderer_OpenGL.		Here's a sequence diagram. Orbiter's framework thread should be handled by the framework. Additional threads like OpenGL's thread will be handled (created/destroyed) in OrbiterRenderer_OpenGL.

Wikiadmin at 08:51, 7 June 2006

2006-06-07T08:51:20Z

←Older revision		Revision as of 08:51, 7 June 2006
Line 1:		Line 1:
	<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>== Orbiter Renderers ==		<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>== Orbiter Renderers ==

			=== General information ===

	All the methods from Orbiter which have rendering functionality have been moved in OrbiterRenderer. Same for functions used to display dialogs or a progress.		All the methods from Orbiter which have rendering functionality have been moved in OrbiterRenderer. Same for functions used to display dialogs or a progress.
Line 26:		Line 28:

	[[Image:Orbiter_Refactoring_Orbiter_Renderers.png]]		[[Image:Orbiter_Refactoring_Orbiter_Renderers.png]]


			=== Orbiter creation and destruction

			Here's a sequence diagram. Orbiter's framework thread should be handled by the framework. Additional threads like OpenGL's thread will be handled (created/destroyed) in OrbiterRenderer_OpenGL.

			[[Image:Orbiter_Seq_diagram.png]]



	== Object Renderers ==		== Object Renderers ==

Wikiadmin: /* General information */

2006-06-07T08:08:45Z

General information

←Older revision		Revision as of 08:08, 7 June 2006
Line 30:		Line 30:

	=== General information ===		=== General information ===


	Each class derived from DesignObj_Data has an ObjectRenderer associated. The classes derived from ObjectRenderer is created using ObjectRendererFactory and can differ from engine to engine or shared between engines. We can create an AnimatedDatagridRender_OpenGL which will work only with opengl, but we can create a ClassicColoredDatagridRenderer which can be used for all engines.		Each class derived from DesignObj_Data has an ObjectRenderer associated. The classes derived from ObjectRenderer is created using ObjectRendererFactory and can differ from engine to engine or shared between engines. We can create an AnimatedDatagridRender_OpenGL which will work only with opengl, but we can create a ClassicColoredDatagridRenderer which can be used for all engines.

	The AnimatedDatagridRenderer is not implemented now, only DatagridRenderer which has the same behavior as the one we are using today.
	Additionally, we are using now a custom datagrid for Bluetooth_Dongle : DataGridRenderer_Bluetooth (which does extra things on overriden RenderObject method) and one for Proxy_Orbiter : DataGridRenderer_Proxy.cpp (RenderCell is overriden in order to create the xml with touch zones for datagrid's cells).		The AnimatedDatagridRenderer is not implemented now, only DatagridRenderer which has the same behavior as the one we are using today. Additionally, we are using now a custom datagrid for Bluetooth_Dongle : DataGridRenderer_Bluetooth (which does extra things on overriden RenderObject method) and one for Proxy_Orbiter : DataGridRenderer_Proxy.cpp (RenderCell is overriden in order to create the xml with touch zones for datagrid's cells).


	[[Image:Orbiter_refactor_Object_Renderer.png]]		[[Image:Orbiter_refactor_Object_Renderer.png]]

Wikiadmin: /* Orbiter Renderers */

2006-06-07T08:08:26Z

Orbiter Renderers

←Older revision		Revision as of 08:08, 7 June 2006
Line 2:		Line 2:

	All the methods from Orbiter which have rendering functionality have been moved in OrbiterRenderer. Same for functions used to display dialogs or a progress.		All the methods from Orbiter which have rendering functionality have been moved in OrbiterRenderer. Same for functions used to display dialogs or a progress.


	Orbiter creates a custom renderer when it starts, using an OrbiterRendererFactory. Based on the graphic engine used, a specific OrbiterRenderer is created. Orbiter has a method Renderer() which gives access to renderer functionality to other classes.		Orbiter creates a custom renderer when it starts, using an OrbiterRendererFactory. Based on the graphic engine used, a specific OrbiterRenderer is created. Orbiter has a method Renderer() which gives access to renderer functionality to other classes.


	PlutoGraphic class is isolated in a new h/cpp since it’s not directly related to DesignObj_Orbiter class.		PlutoGraphic class is isolated in a new h/cpp since it’s not directly related to DesignObj_Orbiter class.


	From Orbiter there are derived classes with specific implementation:		From Orbiter there are derived classes with specific implementation:
Line 19:		Line 22:

	These changes didn't affect Orbiter’s behavior.		These changes didn't affect Orbiter’s behavior.
			Here's a simplified partial UML:

	~~Here's a simplified partial UML:~~

	[[Image:Orbiter_Refactoring_Orbiter_Renderers.png]]		[[Image:Orbiter_Refactoring_Orbiter_Renderers.png]]

Wikiadmin: /* Orbiter Renderers */

2006-06-07T08:08:09Z

Orbiter Renderers

←Older revision		Revision as of 08:08, 7 June 2006
Line 8:		Line 8:

	From Orbiter there are derived classes with specific implementation:		From Orbiter there are derived classes with specific implementation:

	- Orbiter_Win32 (which overrides SelfUpdate method - uses OrbiterSelfUpdate class to update orbiter's binary)		- Orbiter_Win32 (which overrides SelfUpdate method - uses OrbiterSelfUpdate class to update orbiter's binary)

	- OrbiterLinux (X11 stuff, XRecording, GrabPointer/GrabKeyboard, window manager)		- OrbiterLinux (X11 stuff, XRecording, GrabPointer/GrabKeyboard, window manager)

	- OrbiterBluetooth (creates a BDCommandProcessor and uses PhoneDetection to detect/connect to smartphones)		- OrbiterBluetooth (creates a BDCommandProcessor and uses PhoneDetection to detect/connect to smartphones)

	- Proxy_Orbiter (has a tcp server, communicates with apache, creates xml for cisco phone).		- Proxy_Orbiter (has a tcp server, communicates with apache, creates xml for cisco phone).


	These changes didn't affect Orbiter’s behavior.		These changes didn't affect Orbiter’s behavior.