I have made some changes, there's not more gz_name elements and some other=
changes done for the sake of consistency.
I'd like to start tomorrow writting the parsers.
I do mean plural here. Because each parser will be in charge of a small set=
the full XML.
One parser for the xode format
One parser for each interface.
There will be a base class (XMLModel) with pointers to init, fini and updat=
functions and pointers to data.=20
Each parser will add a function to the init, fini and update pointers. So t=
code will be called when the model is loaded, unloaded and updated.=20
The data pointer is needed for all the data of the model that must be=20
preserved between updates.
=46rom tomorrow I'll start writting the parsers and migrating the models to=
How can we solve the=20
<data to=3D"pos.x" to=3D"pos.y" to=3D"rot.z" to=3D"vel.x" to=3D"vel.y" to=
Any other issue?
Tuesday 11 April 2006 17:14=E3=80=81Nate Koenig =E3=81=95=E3=82=93=E3=81=AF=
> So I'm beginning to have some major issues with the current XML
> interfaces. Nothing in the interfaces correlates to ODE, therefore it
> makes no sense to use XODE to describe interfaces. We should only use
> XODE to describe how a model is constructed. This description should
> be a self contained unit, with no extensions. If we have to use <ext
> ename=3D"..."> all over the place, then we should not use XODE. I would
> rather see a nice clean and intuitive XML file, than conform to a
> pseudo standard.
> I also dislike the extensive use of attributes. I don't want to see lines
> like: <data to=3D"pos.x" to=3D"pos.y" to=3D"rot.z" to=3D"vel.x" to=3D"vel=
> to=3D"vel_rot.z" />
> Check the spelling in the position interface (differential not
> On 4/10/06, Jordi <mumismo@...> wrote:
> > I've created the XML position interface:
> > http://gazeboxml.pbwiki.com/gz_position2d_iface
> > Surely it has a lot of problems that can be pointed out.
> > Except for some code on the models that I don't understand (the mail wi=
> > doubts is around), all the other code related to robot position, speed,
> > etc. Will be able to be generated with the data in that XML format.
> > Tomorrow I'll review the file format as it is up to now. There's some
> > inconsistences, for instance, most of the time we use "attach" attribut=
> > except in one case where "attach" is an element.
> > Since thursday I'll start writting parsers for that format and surely I
> > will find some more carveats.
> > I'll try in a couple of weeks to migrate most of our current models to
> > XML files.
> > I'm trying to do this with Gazebo:=20
> > http://gazeboxml.pbwiki.com/general_design
> > Nate, did you decide about the Ogre3d/Delta3d/Yake issue?
> > ^_^/
> > Jordi
> > -------------------------------------------------------
> > This SF.Net email is sponsored by xPML, a groundbreaking scripting
> > language that extends applications into web and mobile media. Attend the
> > live webcast and join the prime developer group breaking into this new
> > coding territory!
> > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=
> > _______________________________________________
> > Playerstage-gazebo mailing list
> > Playerstage-gazebo@...
> > https://lists.sourceforge.net/lists/listinfo/playerstage-gazebo
> This SF.Net email is sponsored by xPML, a groundbreaking scripting langua=
> that extends applications into web and mobile media. Attend the live
> webcast and join the prime developer group breaking into this new coding
> Playerstage-gazebo mailing list