Difference between revisions of "Orbiter Programmer's Guide"

From LinuxMCE
Jump to: navigation, search
(Imported document)
 
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><p>The Orbiter is really a [[Pluto DCE Devices]] just like any other.  The main class, Orbiter, is a normal **DCE command** implementation.  However, the Orbiter class was written so that it has no platform-specific functions, such as graphics and sound.  It handles the basic logic, and calls pure virtual functions that derived classes must implement to handle the platform-specific commands.  OrbiterSDL is derived from Orbiter and implements these functions using the SDL library, such as DrawRectangle, DrawImage, PlaySound, etc.  You will see that most of the code and virtually all of the logic is contained in the base Orbiter class.  Therefore, it is a fairly easy task to make a new version of Orbiter for a platform other than SDL, perhaps one that uses Windows SDK calls, or another image library.</p>
+
<p>The Orbiter is really a [[LinuxMCE DCE Devices]] just like any other.  The main class, Orbiter, is a normal **DCE command** implementation.  However, the Orbiter class was written so that it has no platform-specific functions, such as graphics and sound.  It handles the basic logic, and calls pure virtual functions that derived classes must implement to handle the platform-specific commands.  OrbiterSDL is derived from Orbiter and implements these functions using the SDL library, such as DrawRectangle, DrawImage, PlaySound, etc.  You will see that most of the code and virtually all of the logic is contained in the base Orbiter class.  Therefore, it is a fairly easy task to make a new version of Orbiter for a platform other than SDL, perhaps one that uses Windows SDK calls, or another image library.</p>
 
<p>Orbiter devices are also embedded within [[Bluetooth Dongle]] for details.</p>
 
<p>Orbiter devices are also embedded within [[Bluetooth Dongle]] for details.</p>
−
<p>Use the [[Pluto Admin Website]] to build an entirely new user interface of your own, or change Pluto's stock UI.</p>
+
<p>Use the [[LinuxMCE Admin Website]] to build an entirely new user interface of your own, or change LinuxMCE's stock UI.</p>
−
 
+

Revision as of 16:29, 16 March 2007

The Orbiter is really a LinuxMCE DCE Devices just like any other. The main class, Orbiter, is a normal **DCE command** implementation. However, the Orbiter class was written so that it has no platform-specific functions, such as graphics and sound. It handles the basic logic, and calls pure virtual functions that derived classes must implement to handle the platform-specific commands. OrbiterSDL is derived from Orbiter and implements these functions using the SDL library, such as DrawRectangle, DrawImage, PlaySound, etc. You will see that most of the code and virtually all of the logic is contained in the base Orbiter class. Therefore, it is a fairly easy task to make a new version of Orbiter for a platform other than SDL, perhaps one that uses Windows SDK calls, or another image library.

Orbiter devices are also embedded within Bluetooth Dongle for details.

Use the LinuxMCE Admin Website to build an entirely new user interface of your own, or change LinuxMCE's stock UI.

Retrieved from "http://wiki.linuxmce.org/index.php?title=Orbiter_Programmer%27s_Guide&oldid=3406"