@@ -1,3 +1,36 @@ + The Orocos Real-Time Toolkit v1.6.0. + ==================================== + + The Orocos development team is pleased to announce the next major +feature release of the Real-Time Toolkit, a C++ toolkit for building + component based, real-time robotics and machine control applications. + +You can download this release from + <http://www.orocos.org/stable/rtt/v1.6.0/orocos-rtt-1.6.0-src.tar.bz2> +and read the installation instructions on + <http://www.orocos.org/stable/documentation/rtt/v1.6.x/doc-xml/orocos-installation.html> + + +The Real-Time Toolkit (RTT) library allows application designers to +build highly configurable and interactive component-based real-time +control applications. This release's major feature highlights are: + + * Much improved error reporting and usability in various places + * Improved the scripting language and state machine definitions + * More transparent network communication + * Many small improvements suggested by the user community. + +If you'd like a high level overview of the Orocos libraries, visit + <http://www.orocos.org/stable/documentation/rtt/v1.6.x/doc-xml/orocos-overview.html> +If you'd like to get started building your own components, visit + <http://www.orocos.org/stable/documentation/rtt/v1.6.x/doc-xml/orocos-components-manual.html> + +This release is backwards compatible with the 1.0.x and 1.2.x releases, although +some functionality has been deprecated or alternative usage patterns +are preferred. These and other changes and improvements can be found +in the Orocos RTT Changes document on + <http://www.orocos.org/stable/documentation/rtt/v1.6.x/doc-xml/orocos-rtt-changes.html> + The Orocos Real-Time Toolkit v1.4.1. ==================================== NEWS @@ -138,6 +138,19 @@ the transitions of the current state. </para> </listitem> + <listitem> + <para> + There was a bug in the parser such that calling a method on an + unknown object resulted in calling the method on the current object. + This had very confusing consequences, such as when using: + <programlisting> do scripting.loadProgram("the_program.ops"); + do the_program.start();</programlisting> + Which would load fine, but start() would return in error. The + correct behaviour is to signal an error during loading that + 'the_program' is not yet known (It only becomes known after + loadProgram is executed). + </para> + </listitem> </itemizedlist> </section> <section> @@ -145,8 +158,19 @@ <itemizedlist> <listitem> <para> - An initial Max OSX port has been done, and stable enough for broader testing. - If you like to contribute, see + The RTT has been adapted for the Preempt-RT Linux kernel + patch, using the monotonic real-time clock infrastructure for + real-time periodic execution. See + <ulink url="https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id="> + + </ulink>. + </para> + </listitem> + <listitem> + <para> + An initial Max OSX port has been done (RTT and OCL), and + stable enough for broader testing. If you like to + contribute, see <ulink url="https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=533"> Mac OS X port </ulink>. @@ -157,7 +181,8 @@ The main() function has been removed from the Orocos library and is now a macro that expands in user code. This greatly improves debugging, as some (most) debuggers don't - look in libraries for the main() function. + look in libraries for the main() function. Also, this makes + it easier to define your own ORO_main function. </para> </listitem> </itemizedlist> @@ -329,6 +354,12 @@ <itemizedlist> <listitem> <para> + Most components in the OCL are now at run-time loadable + by the DeploymentComponent (deployer application). + </para> + </listitem> + <listitem> + <para> Orocos better intercepts lost connections to remote TaskContexts. The Orocos Component Library's deployer and taskbrowser use this infrastructure to detect and cope with lost connections. doc/xml/orocos-rtt-changes.xml @@ -22,7 +22,7 @@ <para> This document describes the &orocos; Component Model, which allows to design Real-Time software components which - transparantly communicate with each other. + transparently communicate with each other. </para> </abstract> @@ -67,7 +67,7 @@ <caption> <para> Components run in (periodic) threads and can communicate - transparantly. The Orocos RTT does a 'best effort' to + transparently. The Orocos RTT does a 'best effort' to deliver the highest performance to the highest priority threads. </para> doc/xml/orocos-task-context.xml 24b09c27323204e83590af60b5ee1d73627a8f01 psoetens psoetens@ce417995-dfc9-0310-95a0-acdaff106893 http://github.com/doudou/orocos-rtt/commit/002b454ed51c2a1b0651b64c592ff16fc80c30ab 002b454ed51c2a1b0651b64c592ff16fc80c30ab 2008-08-28T03:35:33-07:00 2008-08-28T03:35:33-07:00 Further preparing release notes for RTT 1.6.0 git-svn-id: https://svn.mech.kuleuven.be/repos/orocos/trunk/rtt@29572 ce417995-dfc9-0310-95a0-acdaff106893 c05faa4987a67f26c9eeb777fb0c87849cda1396 psoetens psoetens@ce417995-dfc9-0310-95a0-acdaff106893