XML files in this directory are simple tests to check the engine behaviour.
To play with them, you should compile the library named sample in ../../sample.

Here is a list of the main files and the functionnalities they are testing :

loop.xml
--------
Simple and basic example.


log.xml
-------
This example shows the ARCS builtin logging capability.
When ran, this application should generate a file name "arcs_runtime.log"

stack.xml
---------
This application demonstrates that it is possible to prevent function stack 
explosion using Qt4 queued signal/slot connections.
You can toy with it by changing the parameter "queued" from "0" to "1" inside 
the "link" markup you will find in the XML file.


script.xml
----------
This application demonstrates scripting capabilities.

nest.xml
--------
This application is testing the nesting of components i.e. if passing a 
component as a parameter of another component is possible.


appmain.xml
-----------
This application is toying with composite components. It checks if composite
component are handled the right way. Please also notice that a method described
in the composite component named "composite.xml" is connected to two different
components inside of it.


app2main.xml
------------
This application creates composite components inside of composite components
and checks the behaviour of the engine.


composite.xml
-------------
This is the description of a simple composite component.


subdir/composite.xml
--------------------
This is the description of a composite component embedding itself composite 
components.

multi.xml
---------
This application is here to test the multi-process feature.

profile_1.xml
-------------
This file is not an application but a profile intended to use with the loop
application. To launch it, use the following command :
$ arcsengine loop.xml -p profile_1.xml

constantmodify.xml
------------------
This application can modify itself its constant.
Try using it with the following command :
$ arcsengine constantmodify.xml -o constants.xml


network examples: service_loop.xml service_displayint.xml client[1-3].xml
-------------------------------------------------------------------------
You must check libnetwork has been compiled.
Run both service_loop.xml and service_displayint.xml (if possible, on different
consoles in order to see the results).
Then run successively client1.xml, client2.xml and client3.xml
client1.xml is testing master signal to slave slot connections ;
client2.xml is testing slave signal to master slot connections ;
client3.xml is testing slave signal to slave slot connections.

