APIs that ease migration from classic #325
Labels
enhancement
New feature or request
help wanted
We accept pull requests!
migration
Helps with migration from Gazebo classic to Ignition
Classes like ignition::gazebo::Model are meant to provide helpful wrappers around entities and components which are simpler to use. This is important for users that are not accustomed to C++. This should also ease migration from Gazebo-classic, because the APIs would be more similar.
Not all functions from Gazebo-classic make sense in the new paradigm though. For example, one could query time information like
SimTime
,RealTime
,IsPaused
fromgazebo::physics::World
, but on Ignition, these properties don't belong to the world entity and should be obtained fromUpdateInfo
instead.Here's a preliminary list of some APIs that we could offer on Ignition to mimic Gazebo-classic. The underlying implementation would use calls like
ecm.Component
,ecm.EntityByComponents
, etc.World
,Model
,Link
,Joint
,Light
,Actor
,Sensor
, etc.World::LightByName()
World::Gravity()
,World::MagneticField()
, etc.Status:
The text was updated successfully, but these errors were encountered: