Architecture:RPD Server - Revision history

Jlblanco: /* RPD_Server */

2009-05-29T08:59:17Z

‎RPD_Server

2009-05-27T07:02:41Z

2009-05-27T07:00:38Z

‎Visual RPD Editor

2009-05-25T07:20:47Z

‎RPD_Server

2009-05-20T20:16:58Z

‎Visual RPD Editor

2009-05-20T01:00:22Z

‎Definition of RPD_SERVER data types in BDL

2009-05-20T00:05:10Z

‎RPD Visual Editor

2009-05-19T21:06:08Z

‎RPD_Server

2009-05-19T21:05:18Z

‎RPD_Server

2009-05-19T21:03:01Z

‎RPD_Server

@@ Line 35: / Line 35: @@
   <td> <!-- DECLARATION -->
 <cpp>
-::getRobotName(
+::getParam(
-out string name
+in string name,
+)
 </cpp>
   </td>
   <td> <!-- COMMENTS -->
-Returns the name of the currently selected RPD, as appearing in the selected_RPD table
+A generic way to retrieve a parameter from the table "global_params".
   </td>
 </tr>
@@ Line 92: / Line 62: @@
 </tr>
 </table>
@@ Line 150: / Line 70: @@
 <br>
 = Definition of RPD_SERVER data types in BDL =

@@ Line 1: / Line 1: @@
 <table width="95%"><tr>
 <td align="left"> <small>Previous: [[Architecture:Unique Event Codes | Event Codes]]</small> </td>
-<td align="right"> <small>Next: [[Architecture:High Level ACHRIN layer | ACHRIN]]</small></td></tr>
+<td align="right"> <small>Next: [[Architecture:Visual_RPD_Editor | Visual RPD Editor]]</small>
 </table>

← Older revision		Revision as of 07:00, 27 May 2009
Line 151:		Line 151:
	<br>		<br>

−	~~= Visual RPD Editor =~~

−	This GUI application is the most common way an end user of BABEL should set up the block of parameters for each individual module, what was previously done by means of several configuration (.ini) files.
−
−	~~Now, all the configurations are stored as [[Architecture:Robotic_Platform_Descriptors\|RPDs]] in one ".xml" file, which can be edited with this application.~~
−
−
−	~~'''DOWNLOAD:'''~~
−	~~[http://babel.isa.uma.es/~jlblanco/VisualRPDEditor/VisualRPDEditor-1.0.0-win32.exe VisualRPDEditor-1.0.0-win32.exe] (2.3Mb), last update: May 20, 2009.~~
−
−
−
−	~~<center>~~
−	~~[[Image:screenshot_RPDeditor.jpg]]~~
−	~~</center>~~
−
−
−
−
−	~~<br>~~

	= Definition of RPD_SERVER data types in BDL =		= Definition of RPD_SERVER data types in BDL =

← Older revision		Revision as of 07:20, 25 May 2009
Line 16:		Line 16:

	'''NOTE:''' The most important service here for now is ''getSettingsForModule'', which is a replacement for individual .ini files in modules.		'''NOTE:''' The most important service here for now is ''getSettingsForModule'', which is a replacement for individual .ini files in modules.
		+
		+
		+	TO DO: Remote binary file storage...

← Older revision		Revision as of 20:16, 20 May 2009
Line 153:		Line 153:

	Now, all the configurations are stored as [[Architecture:Robotic_Platform_Descriptors\|RPDs]] in one ".xml" file, which can be edited with this application.		Now, all the configurations are stored as [[Architecture:Robotic_Platform_Descriptors\|RPDs]] in one ".xml" file, which can be edited with this application.
		+
		+
		+	'''DOWNLOAD:'''
		+	[http://babel.isa.uma.es/~jlblanco/VisualRPDEditor/VisualRPDEditor-1.0.0-win32.exe VisualRPDEditor-1.0.0-win32.exe] (2.3Mb), last update: May 20, 2009.
		+

← Older revision		Revision as of 01:00, 20 May 2009
Line 166:		Line 166:
	= Definition of RPD_SERVER data types in BDL =		= Definition of RPD_SERVER data types in BDL =

		+
		+	('''Not used yet''')

	<cpp>		<cpp>

@@ Line 148: / Line 148: @@
 <br>
-= RPD Visual Editor =
+= Visual RPD Editor =
 = Definition of RPD_SERVER data types in BDL =

@@ Line 91: / Line 91: @@
 <tr>
   <td> <!-- DECLARATION -->
 <cpp>
 ::getAllLogicalDevices(
@@ Line 104: / Line 105: @@
 <tr>
   <td> <!-- DECLARATION -->
 <cpp>
 ::findLogicalDevicesByType(
@@ Line 118: / Line 120: @@
 <tr>
   <td> <!-- DECLARATION -->
 <cpp>
 ::getLogicalDevicePose(

@@ Line 54: / Line 54: @@
   <td> <!-- COMMENTS -->
 Returns the 2D shape of the robot, as stored in the RPD_shape2D… table of its descriptor.
 </td>
 </tr>

@@ Line 68: / Line 68: @@
   </td>
   <td> <!-- COMMENTS -->
-Returns a multi-line text in the form “key=value” with settings for a specific calling module name (and optionally an alias name, left blank if not used). This text is the content of the field “ini” for the table “INI_<moduleName>[+<myAlias>]@<robotName>”.
+Returns a multi-line text in the form “key=value” with settings for a specific calling module name (and optionally an alias name, left blank if not used).
 </td>
 </tr>