Difference between revisions of "DCE Generator"
(Imported document) |
Mstovenour (Talk | contribs) m (Added to Category: Programmer's Guide) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | [[Category: Programmer's Guide]] | |
| + | |||
| + | <p>To create a new [[LinuxMCE DCE Devices]] to start receive commands immediately.</p> | ||
<p>DCEGen creates a Command class that has stubs for all the commands you need to implement. The default implementation just echoes to the screen that the command was received and lists the parameters. The Command class will also have member variables for the device's data, and methods to call to fire events.</p> | <p>DCEGen creates a Command class that has stubs for all the commands you need to implement. The default implementation just echoes to the screen that the command was received and lists the parameters. The Command class will also have member variables for the device's data, and methods to call to fire events.</p> | ||
<p>If you later change the device, adding commands, changing event parameters, removing data, etc., just re-run DCEGen. It will fix your project file with these changes. If you already began implementing the commands and changing the class that is not a problem. DCEGen will simply merge the changes in, creating new methods for new commands, and changing the declarations and definitions for commands that have changed. It will also re-write the 'Events' and 'Data' section each time since there is nothing for you to implement there.</p> | <p>If you later change the device, adding commands, changing event parameters, removing data, etc., just re-run DCEGen. It will fix your project file with these changes. If you already began implementing the commands and changing the class that is not a problem. DCEGen will simply merge the changes in, creating new methods for new commands, and changing the declarations and definitions for commands that have changed. It will also re-write the 'Events' and 'Data' section each time since there is nothing for you to implement there.</p> | ||
Latest revision as of 15:37, 11 August 2007
To create a new LinuxMCE DCE Devices to start receive commands immediately.
DCEGen creates a Command class that has stubs for all the commands you need to implement. The default implementation just echoes to the screen that the command was received and lists the parameters. The Command class will also have member variables for the device's data, and methods to call to fire events.
If you later change the device, adding commands, changing event parameters, removing data, etc., just re-run DCEGen. It will fix your project file with these changes. If you already began implementing the commands and changing the class that is not a problem. DCEGen will simply merge the changes in, creating new methods for new commands, and changing the declarations and definitions for commands that have changed. It will also re-write the 'Events' and 'Data' section each time since there is nothing for you to implement there.
