[Rock-dev] Roby::Planning::PlanningMethod

[Sylvain Joyeux]

On 12/05/2011 11:45 AM, Chris Mueller wrote:
> Does anyone have an idea how to filter this structure between
> planning_methods and 'defines'? Or do
> we have an instance in the system, which can provide only an array of
> 'defines' ?
Why do you want to distinguish ?

> If not so, can we maybe extend the Roby::Planning::PlanningMethod
> structure with an additional field, which marks the type of
> PlanningMethod (e.g. type = :define or type = :planner) ?
The orocos/roby plugin automatically defines new planning methods based 
on the defines. This was a good first step, but sucks in the long term. 
In the future, I would like to make these exports "explicit", i.e. have 
people say in the planner class, "orogen_import_define <define_name>" or 
"orogen_import_all_defines" to get this functionality)

By the way, you will have the same issues with devices, which have a 
corresponding interface method called #{device_name}_device
-- 
Sylvain Joyeux (Dr.Ing.)
Space & Security Robotics

!!! Achtung, neue Telefonnummer!!!

Standort Bremen:
DFKI GmbH
Robotics Innovation Center
Robert-Hooke-Straße 5
28359 Bremen, Germany

Phone: +49 (0)421 178-454136
Fax:   +49 (0)421 218-454150
E-Mail: robotik at dfki.de

Weitere Informationen: http://www.dfki.de/robotik
-----------------------------------------------------------------------
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
(Vorsitzender) Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
Amtsgericht Kaiserslautern, HRB 2313
Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
USt-Id.Nr.:    DE 148646973
Steuernummer:  19/673/0060/3
-----------------------------------------------------------------------