Le 08/03/2010 23:50, Peter Soetens a écrit :
> Given it's a beta, and some major features are lacking, it's still great stuff.
> Until now, development of the 2.0 mainline had two major focusses: API
> usability and providing an upgrade path for existing users. The first one
> required major API changes, the second one conversion scripts.

Hello, great work, thanks !

If you want you can find some more win32 related fixes in my fork of RTT
on github. Mainly:
* Some windows "cross platform (I know this can sound funny)" (x86, IPF,
x64) fixes
* Restore the high precision time functions and lightweight threading
* Some minor compilation fixes and missing export symbols

On Mar 8, 2010, at 17:50 , Peter Soetens wrote:

> Given it's a beta, and some major features are lacking, it's still great stuff.
> Until now, development of the 2.0 mainline had two major focusses: API
> usability and providing an upgrade path for existing users. The first one
> required major API changes, the second one conversion scripts.
>
> This beta release allows you to check most 'C++' and 'scripting' aspects of
> 2.0 and allows you to grasp a first 'look-and-feel' of what RTT 2.0 offers.
> Following beta releases (1.99.x) will expose the improved CORBA transport and
> data type generation. The core API and primitives of 2.0.0 will only differ
> slightly (or not) from this release. From now on, it's getting the add-ons to
> work.
>
> For the latest information, check out the 2.0.0-beta1 wiki page:
> http://www.orocos.org/wiki/rtt/rtt-20/rtt-200-beta1
>
> It links to a bunch of useful sub-pages concerning what changed and how users
> can upgrade.
>
> Where to find it ?
>
> There are tar balls and online docs available in the devel section of the
> server kindly provided by the University of Leuven:
>
> http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.1/doc/api/html/
> http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.1/orocos-
> rtt-1.99.1-src.tar.gz
> http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.1/doc/api/html/
> http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.1/orocos-
> ocl-1.99.1-src.tar.gz
>
> And the updated exercises:
> http://people.mech.kuleuven.be/~orocos/pub/devel/examples/rtt/tutorial
>
> Other official code resources for 2.0 are my git repositories on github: rtt-
> examples, orocos-rtt and orocos-ocl. Check out the ocl-2.0-mainline and
> rtt-2.0-mainline code. I will not host 2.0 in an SVN repository.

RTT does not compile on Koala nor Snow Leopard. With or without Corba on. The list of errors is impressively long ... :-)

About the only constructive things I can add are

1) Looks like the "typedef ... Signature" in internal/RemoteMethod should be in internal/RemoteMethodBase

2) The cmake logic does not look for dia nor inkscape before trying to build docs

3) The docs reference files that aren't in the source (eg /home/kaltan/...)

Sorry this isn't more constructive ...
Stephen

Sorry for the late comment, but I had no time until today to look carefully
at the specs of RTT-2.0. The concept of messages seems increasingly used in
the new architecture. Has there been any discussions to replace the current
CORBA transport layer or add a message-oriented middleware (MOM [1]) like
the Apache Qpid [2] implementation of the AMQP [3] standard ?

[1] http://en.wikipedia.org/wiki/Message-oriented_middleware
[2] http://qpid.apache.org/
[3] http://www.amqp.org/

2010/3/8 Peter Soetens <peter [..] ...>

> Given it's a beta, and some major features are lacking, it's still great
> stuff.
> Until now, development of the 2.0 mainline had two major focusses: API
> usability and providing an upgrade path for existing users. The first one
> required major API changes, the second one conversion scripts.
>
> This beta release allows you to check most 'C++' and 'scripting' aspects of
> 2.0 and allows you to grasp a first 'look-and-feel' of what RTT 2.0 offers.
> Following beta releases (1.99.x) will expose the improved CORBA transport
> and
> data type generation. The core API and primitives of 2.0.0 will only differ
> slightly (or not) from this release. From now on, it's getting the add-ons
> to
> work.
>
> For the latest information, check out the 2.0.0-beta1 wiki page:
> http://www.orocos.org/wiki/rtt/rtt-20/rtt-200-beta1
>
> It links to a bunch of useful sub-pages concerning what changed and how
> users
> can upgrade.
>
> Where to find it ?
>
> There are tar balls and online docs available in the devel section of the
> server kindly provided by the University of Leuven:
>
> http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.1/doc/api/htm... />
> http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.1/orocos-
> rtt-1.99.1-src.tar.gz<http://people.mech.kuleuven.be/%7Eorocos/pub/devel/rtt/v1.99.1/orocos-%0Artt-1.99.1-src.tar.gz>
> http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.1/doc/api/htm... />
> http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.1/orocos-
> ocl-1.99.1-src.tar.gz<http://people.mech.kuleuven.be/%7Eorocos/pub/devel/ocl/v1.99.1/orocos-%0Aocl-1.99.1-src.tar.gz>
>
> And the updated exercises:
> http://people.mech.kuleuven.be/~orocos/pub/devel/examples/rtt/tutorial<h...
>
> Other official code resources for 2.0 are my git repositories on github:
> rtt-
> examples, orocos-rtt and orocos-ocl. Check out the ocl-2.0-mainline and
> rtt-2.0-mainline code. I will not host 2.0 in an SVN repository.
>
> What's not in here ?
>
> See the caveats section on the wiki. Most notably, CORBA transport is still
> broken, which means no remote access to applications. Also some unit tests
> will fail.
>
> What will this release allow you to do ?
>
> - Test porting effort to the RTT 2.0 API.
> We have created scripts for converting application code to the 2.0 API,
> regarding the C++ part. CORBA interfaces will change after this beta, so no
> scripts for these exist yet.
> - Test RTT 2.0 on your distribution/target.
> A lot of code changed, not all compilers or operating systems could be
> tested.
> Now is the time to see if 2.0 *at least compiles* on your system.
>
> What can you do to help ?
>
> - Test the conversion scripts and update the wiki or scripts if you find
> issues.
> - Update wiki pages, installation notes etc if you encounter
> inconsistencies.
> - Send patches against this codebase, preferably using a git repository.
> - Provide feedback on documentation or API changes.
>
> Are we there yet ?
>
> I hope to have beta2 ready this month with CORBA transport and your
> feedback.
> We'll see what April brings.
>
> My special thanks go out to Sylvain Joyeux (data flow rework), Stephen
> Roderick
> (TLSF stuff) , Jean Sreng (Win32 porting), the team at Onera
> (beta-testing),
> Markus Klotzbuecher (yammering about consistency) and Klaas Gadeyne
> (whining
> about usability). We would be lost without us.
>
> Enjoy !
> Peter
> --
> Orocos-Dev mailing list
> Orocos-Dev [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>

Sorry for the late comment, but I had no time until today to look carefully
at the specs of RTT-2.0. The concept of messages seems increasingly used in
the new architecture. Has there been any discussions to replace the current
CORBA transport layer or add a message-oriented middleware (MOM [1]) like
the Apache Qpid [2] implementation of the AMQP [3] standard ?

[1] http://en.wikipedia.org/wiki/Message-oriented_middleware
[2] http://qpid.apache.org/
[3] http://www.amqp.org/

2010/3/8 Peter Soetens <peter [..] ...>

> Given it's a beta, and some major features are lacking, it's still great
> stuff.
> Until now, development of the 2.0 mainline had two major focusses: API
> usability and providing an upgrade path for existing users. The first one
> required major API changes, the second one conversion scripts.
>
> This beta release allows you to check most 'C++' and 'scripting' aspects of
> 2.0 and allows you to grasp a first 'look-and-feel' of what RTT 2.0 offers.
> Following beta releases (1.99.x) will expose the improved CORBA transport
> and
> data type generation. The core API and primitives of 2.0.0 will only differ
> slightly (or not) from this release. From now on, it's getting the add-ons
> to
> work.
>
> For the latest information, check out the 2.0.0-beta1 wiki page:
> http://www.orocos.org/wiki/rtt/rtt-20/rtt-200-beta1
>
> It links to a bunch of useful sub-pages concerning what changed and how
> users
> can upgrade.
>
> Where to find it ?
>
> There are tar balls and online docs available in the devel section of the
> server kindly provided by the University of Leuven:
>
> http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.1/doc/api/htm... />
> http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.1/orocos-
> rtt-1.99.1-src.tar.gz<http://people.mech.kuleuven.be/%7Eorocos/pub/devel/rtt/v1.99.1/orocos-%0Artt-1.99.1-src.tar.gz>
> http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.1/doc/api/htm... />
> http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.1/orocos-
> ocl-1.99.1-src.tar.gz<http://people.mech.kuleuven.be/%7Eorocos/pub/devel/ocl/v1.99.1/orocos-%0Aocl-1.99.1-src.tar.gz>
>
> And the updated exercises:
> http://people.mech.kuleuven.be/~orocos/pub/devel/examples/rtt/tutorial<h...
>
> Other official code resources for 2.0 are my git repositories on github:
> rtt-
> examples, orocos-rtt and orocos-ocl. Check out the ocl-2.0-mainline and
> rtt-2.0-mainline code. I will not host 2.0 in an SVN repository.
>
> What's not in here ?
>
> See the caveats section on the wiki. Most notably, CORBA transport is still
> broken, which means no remote access to applications. Also some unit tests
> will fail.
>
> What will this release allow you to do ?
>
> - Test porting effort to the RTT 2.0 API.
> We have created scripts for converting application code to the 2.0 API,
> regarding the C++ part. CORBA interfaces will change after this beta, so no
> scripts for these exist yet.
> - Test RTT 2.0 on your distribution/target.
> A lot of code changed, not all compilers or operating systems could be
> tested.
> Now is the time to see if 2.0 *at least compiles* on your system.
>
> What can you do to help ?
>
> - Test the conversion scripts and update the wiki or scripts if you find
> issues.
> - Update wiki pages, installation notes etc if you encounter
> inconsistencies.
> - Send patches against this codebase, preferably using a git repository.
> - Provide feedback on documentation or API changes.
>
> Are we there yet ?
>
> I hope to have beta2 ready this month with CORBA transport and your
> feedback.
> We'll see what April brings.
>
> My special thanks go out to Sylvain Joyeux (data flow rework), Stephen
> Roderick
> (TLSF stuff) , Jean Sreng (Win32 porting), the team at Onera
> (beta-testing),
> Markus Klotzbuecher (yammering about consistency) and Klaas Gadeyne
> (whining
> about usability). We would be lost without us.
>
> Enjoy !
> Peter
> --
> Orocos-Dev mailing list
> Orocos-Dev [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>

On Mon, Mar 08, 2010 at 11:50:59PM +0100, Peter Soetens wrote:
> Given it's a beta, and some major features are lacking, it's still great stuff.
> Until now, development of the 2.0 mainline had two major focusses: API
> usability and providing an upgrade path for existing users. The first one
> required major API changes, the second one conversion scripts.
>
> This beta release allows you to check most 'C++' and 'scripting' aspects of
> 2.0 and allows you to grasp a first 'look-and-feel' of what RTT 2.0 offers.
> Following beta releases (1.99.x) will expose the improved CORBA transport and
> data type generation. The core API and primitives of 2.0.0 will only differ
> slightly (or not) from this release. From now on, it's getting the add-ons to
> work.
>
> For the latest information, check out the 2.0.0-beta1 wiki page:
> http://www.orocos.org/wiki/rtt/rtt-20/rtt-200-beta1
>
> It links to a bunch of useful sub-pages concerning what changed and how users
> can upgrade.
>
> Where to find it ?
>
> There are tar balls and online docs available in the devel section of the
> server kindly provided by the University of Leuven:
>
> http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.1/doc/api/html/
> http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.1/orocos-
> rtt-1.99.1-src.tar.gz
> http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.1/doc/api/html/
> http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.1/orocos-
> ocl-1.99.1-src.tar.gz
>
> And the updated exercises:
> http://people.mech.kuleuven.be/~orocos/pub/devel/examples/rtt/tutorial
>
> Other official code resources for 2.0 are my git repositories on github: rtt-
> examples, orocos-rtt and orocos-ocl. Check out the ocl-2.0-mainline and
> rtt-2.0-mainline code. I will not host 2.0 in an SVN repository.
>
> What's not in here ?
>
> See the caveats section on the wiki. Most notably, CORBA transport is still
> broken, which means no remote access to applications. Also some unit tests
> will fail.
>
> What will this release allow you to do ?
>
> - Test porting effort to the RTT 2.0 API.
> We have created scripts for converting application code to the 2.0 API,
> regarding the C++ part. CORBA interfaces will change after this beta, so no
> scripts for these exist yet.
> - Test RTT 2.0 on your distribution/target.
> A lot of code changed, not all compilers or operating systems could be tested.
> Now is the time to see if 2.0 *at least compiles* on your system.
>
> What can you do to help ?
>
> - Test the conversion scripts and update the wiki or scripts if you find
> issues.
> - Update wiki pages, installation notes etc if you encounter inconsistencies.
> - Send patches against this codebase, preferably using a git repository.
> - Provide feedback on documentation or API changes.
>
> Are we there yet ?
>
> I hope to have beta2 ready this month with CORBA transport and your feedback.
> We'll see what April brings.
>
> My special thanks go out to Sylvain Joyeux (data flow rework), Stephen Roderick
> (TLSF stuff) , Jean Sreng (Win32 porting), the team at Onera (beta-testing),
> Markus Klotzbuecher (yammering about consistency) and Klaas Gadeyne (whining
> about usability). We would be lost without us.

Excellent work Peter!

Best regards
Markus

On Mon, Mar 08, 2010 at 11:50:59PM +0100, Peter Soetens wrote:
> Given it's a beta, and some major features are lacking, it's still great stuff.
> Until now, development of the 2.0 mainline had two major focusses: API
> usability and providing an upgrade path for existing users. The first one
> required major API changes, the second one conversion scripts.
>
> This beta release allows you to check most 'C++' and 'scripting' aspects of
> 2.0 and allows you to grasp a first 'look-and-feel' of what RTT 2.0 offers.
> Following beta releases (1.99.x) will expose the improved CORBA transport and
> data type generation. The core API and primitives of 2.0.0 will only differ
> slightly (or not) from this release. From now on, it's getting the add-ons to
> work.
>
> For the latest information, check out the 2.0.0-beta1 wiki page:
> http://www.orocos.org/wiki/rtt/rtt-20/rtt-200-beta1
>
> It links to a bunch of useful sub-pages concerning what changed and how users
> can upgrade.
>
> Where to find it ?
>
> There are tar balls and online docs available in the devel section of the
> server kindly provided by the University of Leuven:
>
> http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.1/doc/api/html/
> http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.1/orocos-
> rtt-1.99.1-src.tar.gz
> http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.1/doc/api/html/
> http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.1/orocos-
> ocl-1.99.1-src.tar.gz
>
> And the updated exercises:
> http://people.mech.kuleuven.be/~orocos/pub/devel/examples/rtt/tutorial
>
> Other official code resources for 2.0 are my git repositories on github: rtt-
> examples, orocos-rtt and orocos-ocl. Check out the ocl-2.0-mainline and
> rtt-2.0-mainline code. I will not host 2.0 in an SVN repository.
>
> What's not in here ?
>
> See the caveats section on the wiki. Most notably, CORBA transport is still
> broken, which means no remote access to applications. Also some unit tests
> will fail.
>
> What will this release allow you to do ?
>
> - Test porting effort to the RTT 2.0 API.
> We have created scripts for converting application code to the 2.0 API,
> regarding the C++ part. CORBA interfaces will change after this beta, so no
> scripts for these exist yet.
> - Test RTT 2.0 on your distribution/target.
> A lot of code changed, not all compilers or operating systems could be tested.
> Now is the time to see if 2.0 *at least compiles* on your system.
>
> What can you do to help ?
>
> - Test the conversion scripts and update the wiki or scripts if you find
> issues.
> - Update wiki pages, installation notes etc if you encounter inconsistencies.
> - Send patches against this codebase, preferably using a git repository.
> - Provide feedback on documentation or API changes.
>
> Are we there yet ?
>
> I hope to have beta2 ready this month with CORBA transport and your feedback.
> We'll see what April brings.
>
> My special thanks go out to Sylvain Joyeux (data flow rework), Stephen Roderick
> (TLSF stuff) , Jean Sreng (Win32 porting), the team at Onera (beta-testing),
> Markus Klotzbuecher (yammering about consistency) and Klaas Gadeyne (whining
> about usability). We would be lost without us.

Excellent work Peter!

Best regards
Markus