Sep 21 2004
w.bethel

In order to make these examples work on your machine, you will need to
hack on a bunch of files and rebuild everything (except VTK).

The "valid" examples are:
 CCA-ConeRender1
 CCA-Example1
 CCA-ConeGen1
 CCA-ConeGen2

Inside each directory you'll find:
- A .sidl file, containing the component interface definition written in SIDL.
- A Makefile that will invoke babel to generate code from the
	SIDL interface definition.
- A cca directory and a component directory.



To "port" to your machine:

Unpack the tarball into some directory. If you unpack the tarball into
the directory /tmp/CCA-July04, you won't need to change any of the files. ;-)
However, if you insist on dumping the tarball into some other location,
such as /tmp/foo, then you need to make the following edits
(caveat emptor - the following list is believed to be correct and complete,
but you know how it goes)

1. edit component/libexample1-c++.scl and replace the string /tmp/CCA-July04
with /tmp/foo.

2. edit the Makefile so that *all* occurances of /tmp/CCA-July04 are
replaced with /tmp/foo. How many such occurances are there? (Answer: 
more than two).

3. In theory, you need to edit all the component/*.cca files and replace
occurances of /tmp/CCA-July04 with /tmp/foo, however I'm not so sure
this step is really required (due to some testing just now where I
had some garbage directories listed in the *.cca files yet the
components loaded/ran).

After all those edits, cd back into the top-level component directory
(CCA-ConeRender1, etc.) and type make. This will run babel on your
SIDL file.

Next, cd into CCA-ConeRender1/cca and type make.
Next, cd into CCA-ConeRender1/component and type make.


To run the framework, GUI on *one* of these components:

0. cd to CCA-ConeRender1/component
1. In one shell, type:
ccafe-client --type server --ccafe-io2tty --cafe-rc ./CcaffeineRC --port 5050 

NOTE: I have found that you must not have the --cafe-rc <file> option as the
last one in the command line, otherwise ccafe-client gets confused and
can't find the initRC file (./CcaffeineRC).

2. In another shell on the same machine:
runGUI --builderPort 5050

Instantiate the component(s), connect up ports as needed and punch GO.

If you get an error while instantiating the component that says something
like "ConeGen1.VTKRendererSimple class not found", then you've most
likely made a boo-boo in your edits (1-3 above).


Manifest

bin - contains some FLTK binaries - not needed for these CCA demos.
CCA-ConeGen1 - 2-component example, one component generates cone
	geometry that is passed via a port to another component that
	contains the VTK renderer.
CCA-ConeGen2 - 2-component example. One component generates cone geometry
	that is passed via a port to another component that contains
	an FLTK-wrapped VTK renderer. The renderer component has an
	FLTK slider that sends integers via a port back to the
	cone-generator component. This one is the most complex of all
	the examples.
CCA-Example1 - simple, single-component example that is simply a CCA-wrapped
	version of the VTK-based conegen-render example.
CCA-ConeRender1- basically the same as CCA-Example1, but is renamed so we
	can endure the bumps and bruises of moving components around.
Examples - original src for the pre-CCA versions.
include - include files for FLTK and VTK.
lib - libs for FLTK and VTK.
vtkbuild - src dir used for building VTK libs.
man
share
vtkbuild