This section describes some of the aRts work that is in progress. Development progresses quickly, so this information may be out of date. You should check the TODO list file and the mailing list archives to see what new functionality is planned. Feel free to get involved in new design and implementation.
This is a draft document which tries to give you an overview how new technologies will be integrated in aRts. Namely, it does cover the following:
This is work in progress. However, it should be the base if you want to see new technology in aRts. It should give you a general idea how these problems will be adressed. However, feel free to correct anything you see here.
Things that will be use aRts technology (so please, coordinate your efforts):
MCOP interfaces are the base of the aRts concept. They are the network transparent equivalent to C++ classes. Whenever possible you should orient your design towards interfaces. Interfaces consist of four parts:
These can be mixed in any way you like. New technologies should be defined in terms of interfaces. Read the sections about asynchronous streams and synchronous streams, as well as the KMedia2 interfaces, which are a good example how such things work
Interfaces are specified in .idl code and run through the mcopidl compiler. You derive the Interfacename_impl class to implement them, and use REGISTER_IMPLEMENTATION(Interfacename_impl) to insert your object implementations into the MCOP object system.