orca-robotics INTRODUCTION Overview Download and Install Quick Start Documentation Publications REPOSITORY Interfaces Components Libraries Utilities Software Map DEVELOPER Tutorials Examples Dev Guide Dashboard Wiki login/pass: orca/orca PEOPLE Contributors Users Project Download Mailing lists

Guide to Beginning Development Note: Reviewed for release 2.4.0. Whether you have big development plans or just want to see what is envolved in using Orca, you have to start by writing a single component. You can add a new component to the Orca source tree which downloaded or checked out from SVN but it is inconvenient (mostly because it is large, seems complicated, and can be slow to recompile). You can follow these instructions to set up your own Orca-based project and create the first component. Step 1. Create a separate project for yourself. Read: Starting Your Own Orca Project Make sure this generic project compiles. One component you already have: it's called somecomponent and it came with your Empty Project. (The source is in [EMPTY_PROJ_SRC]/src/components/somecomponent ). This is not a very good example, however, because it just creates a couple of data structures. Step 2. Copy an existing component. Read these instructions first which tell you how to add any new code to your project. Concentrate on the parts which talk about adding a new component. Read: Adding Souce Code to Orca Which component to copy? If you are developing something specific, then you probably want start with a component similar to what you have in mind. Try to find it in the Orca distribution. Ideally it would have interfaces similar to yours or a similar data flow. For example, if you are developing a server for a new robotic platform, then perhaps start with SegwayRmp component. (The source is in [ORCA_SRC]/src/components/segwayrmp ) If you just want to evaluate Orca, then you probably want to write a simple generic component. We maintain a component called Brick in the Orca source tree. We use it as a standard implementation to test IceGrid services but it's also a useful template to start playing with. It does not setup or connect to any interfaces. (The source is in [ORCA_SRC]/src/tests/brick ). Another simple option is LaserMon. This is just a client for a single interface. (The source is in [ORCA_SRC]/src/components/lasermon ). Make sure the project compiles and the new component runs. Step 3. Modify the component to suit your needs. As you start looking at the source code for Orca component, keep in mind that most the non-Ice functions and classes are in one library: libOrcaIce. All functions and classes are in the same namespace "orcaice" and all are fairly well documented .

Webmaster: Tobias Kaupp (tobasco at users.sourceforge.net)

---