RTT and OCL 2.0.0-beta3 released

The third beta release of RTT 2.0 is availabIe from:

http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.3/
http://github.com/psoetens/orocos-rtt
http://github.com/psoetens/orocos-ocl

The main change with beta2 is the plugin framework and the conversion of RTT
marshalling, scripting and typekit into plugins. (see also [1]). The deployer
has been modified to pick the plugins up automatically, and can easily be
extended to find some more. The RTT_COMPONENT_PATH environment variable and
deployer property both list the places where to look for components, plugins
and typekits. The TaskBrowser can be queried for available types and plugins.
A configure() run on the deployer will lead to a re-scan for plugins and
components.

Both the typekit and plugin manuals[3,4] have been updated as well as the 1.x
to 2.0 conversion scripts on the wiki[2]. Please skim the manuals to get an
impression of the API changes for typekits.

Also the TLSF/RT-logging for OCL has been ported from the 1.x line to 2.0, but
this still qualifies as 'experimental'. It also requires a patched version of
log4cpp.

There are no more major changes planned leading to 2.0.0, except that we
wanted the OCL directory structure to be refactored in order to group
components according to maintainer and to cleanup the cmake settings. The RTT
could have some cmake cleanup too. This should have no influence on the API
though.

We're very close to being 'there'. These are the open issues:
* Support event transitions in state machines. Currently, only reacting to new
port data is possible, not the 1.x style multi-argument transition syntax.
* Fix the component lifecycle as discussed earlier on the orocos-dev list.

Both don't require API changes (iirc).

Peter

[1] http://www.orocos.org/forum/rtt/rtt-dev/rtt-2-naming-convention-suggestion
[2] http://www.orocos.org/wiki/rtt/rtt-20/rtt-20-renaming-table
[3] http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.3/doc/doc-
xml/orocos-typekit-plugin.html
[4] http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.3/doc/doc-
xml/orocos-rtt-plugins.html

RTT and OCL 2.0.0-beta3 released

Hi Konrad,

Please keep the list on CC so others can learn something too.

On Wed, Jun 30, 2010 at 11:35:41AM +0200, Konrad Banachowicz wrote:
> Which version of boost are you using ?
>
> There is an other problem.
> In type_discovery.hpp if statment require boost 104200, but API change happend
> in 104100. This might cause your problem.

I'm using boost-1.42. What you describe might bite 1.41 users, but in
my case I'm almost certain that my problem is that BOOST_VERSION is
not defined when the type discovery test is compiled...

But thanks for the hint!

Markus

RTT and OCL 2.0.0-beta3 released

There is missing include in type_discovery.hpp, <boost/version.hpp> provides
BOOST_VERSION definition.

Konrad Banachowicz

2010/6/30 Markus Klotzbuecher <markus [dot] klotzbuecher [..] ...>

> Hi Konrad,
>
> Please keep the list on CC so others can learn something too.
>
> On Wed, Jun 30, 2010 at 11:35:41AM +0200, Konrad Banachowicz wrote:
> > Which version of boost are you using ?
> >
> > There is an other problem.
> > In type_discovery.hpp if statment require boost 104200, but API change
> happend
> > in 104100. This might cause your problem.
>
> I'm using boost-1.42. What you describe might bite 1.41 users, but in
> my case I'm almost certain that my problem is that BOOST_VERSION is
> not defined when the type discovery test is compiled...
>
> But thanks for the hint!
>
> Markus
>
>

RTT and OCL 2.0.0-beta3 released

On Wed, Jun 30, 2010 at 11:51:59AM +0200, Konrad Banachowicz wrote:
> There is missing include in type_discovery.hpp, <boost/version.hpp> provides
> BOOST_VERSION definition.

Right, thanks! Peter, please fix!

Markus