<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:black;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";
        color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";
        color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:10.0pt;
        margin-left:.5in;
        line-height:115%;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";
        color:black;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;
        color:black;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";
        color:black;}
span.EmailStyle22
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle23
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle24
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle25
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hello,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>As for Orocos, If there is no need to know it to use Rock then it would be simply enough to say it but I agree it is still important to say that it is based on Orocos in introductions and so to take profit from its popularity/community. I saw there is an object called Orocos used in the ruby script, maybe you could rename it. As I said, those are just details but sometimes details make a point, especially for beginners.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The PDF manual is the classical way to describe a system so I thought you would do it. In the PDF everything is accessible through one scroll so you can quickly have an overview of the system. Plus, you have the “number of pages” criterion to judge … ;). But, using a website only documentation might be a good idea since it forces the users to “navigate”. Just for the sake of equivalence with PDF, you could prepare a download-able version of your website for offline users . <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Jan<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>-----------------------------------------------------------------<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>Jan SLIWKA<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Dr. Eng. Contractor at ETD CMRE</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Software engineering, algorithms, robotics<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>web: <a href="http://www.jan-sliwka.net/">www.jan-sliwka.net</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> Sylvain Joyeux [mailto:sylvain.joyeux@dfki.de] <br><b>Sent:</b> Monday, September 17, 2012 10:57 AM<br><b>To:</b> Jan Sliwka<br><b>Cc:</b> 'Thomas Roehr'; rock-dev@dfki.de<br><b>Subject:</b> Re: [Rock-dev] Fwd: RE: Avalon's Middleware<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On 09/14/2012 12:11 PM, Jan Sliwka wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sometimes it is just details like for example the fact that you are based Orocos. As a beginner I would go and read about Orocos and maybe say “<i>oh, that’s so complicated, If I have to learn how to use Orocos and Rock I will never make it…</i>” <span style='font-family:Wingdings'>ß</span> this is just a simulation <o:p></o:p></p></blockquote><p class=MsoNormal>Interesting point. I already saw people comment on "I'm using Rock and I am reading this and that from the orocos documentation ...". The whole point is that one does NOT have to read the orocos documentation ...<br><br>What do you think ? Would it be enough to simply stress that one does not have to know Orocos to use Rock ? It is important to me that the link to orocos is shown, as their work is very important for the well-being of Rock.<br><br><br><o:p></o:p></p><p class=MsoNormal>. Another detail (but you can’t help it and I find it fine), there are two languages to which you have to integrate the code: C++ and Ruby. ROS uses only one. <o:p></o:p></p><p class=MsoNormal>True for the beginning, not true for more advanced projects (they often need some Python)<br><br><o:p></o:p></p><p class=MsoNormal>Anyhow, I am closely following your project. <o:p></o:p></p><p class=MsoNormal>Tell me when you have a Pdf version of the manual.<o:p></o:p></p><p class=MsoNormal>Is there a reason why do you need a PDF version of the manual ?<br><br><o:p></o:p></p><pre>-- <o:p></o:p></pre><pre>Sylvain Joyeux (Dr.Ing.)<o:p></o:p></pre><pre>Senior Researcher<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Space & Security Robotics<o:p></o:p></pre><pre>Underwater Robotics<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>!!! Achtung, neue Telefonnummer!!!<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Standort Bremen:<o:p></o:p></pre><pre>DFKI GmbH<o:p></o:p></pre><pre>Robotics Innovation Center<o:p></o:p></pre><pre>Robert-Hooke-Straße 5<o:p></o:p></pre><pre>28359 Bremen, Germany<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Phone: +49 (0)421 178-454136<o:p></o:p></pre><pre>Fax: +49 (0)421 218-454150<o:p></o:p></pre><pre>E-Mail: <a href="mailto:robotik@dfki.de">robotik@dfki.de</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Weitere Informationen: <a href="http://www.dfki.de/robotik">http://www.dfki.de/robotik</a><o:p></o:p></pre><pre>-----------------------------------------------------------------------<o:p></o:p></pre><pre>Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH<o:p></o:p></pre><pre>Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern<o:p></o:p></pre><pre>Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster<o:p></o:p></pre><pre>(Vorsitzender) Dr. Walter Olthoff<o:p></o:p></pre><pre>Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes<o:p></o:p></pre><pre>Amtsgericht Kaiserslautern, HRB 2313<o:p></o:p></pre><pre>Sitz der Gesellschaft: Kaiserslautern (HRB 2313)<o:p></o:p></pre><pre>USt-Id.Nr.: DE 148646973<o:p></o:p></pre><pre>Steuernummer: 19/673/0060/3<o:p></o:p></pre><pre>----------------------------------------------------------------------- <o:p></o:p></pre></div> <BR/><BR>
<HR><Font face=arial size=2 color=black><I>
*** PRIVILEGED AND CONFIDENTIAL ***<BR>
<BR>Centre for Maritime Research and Experimentation (CMRE, formerly NURC)<BR><BR>
The information contained in this e-mail message (including any attached files)<BR>
is intended for the use of the addressee(s) only and is privileged information.<BR>
The information should neither be posted to the Internet, nor published in any<BR>
other public domain, without the express permission of the sender. If you are<BR>
not the intended recipient(s) or the recipient's representative, you are hereby<BR>
notified that any use, disclosure, copying or distribution of this communication<BR>
is prohibited. If you have received this communication in error please notify us<BR>
immediately at postmaster@cmre.nato.int and remove this message from <BR>
your system.
</I>
</font><HR>
</body></html>