![]() |
Houdini Development Toolkit - Version 6.5Side Effects Software Inc. 2004 |
The DSO's will be automatically "tagged" with some information which
can be viewed the the program sesitag. To change the tag information,
you can set the environment variable SESI_TAGINFO to contain
a tag of information which you'd like to see displayed. For example:
Stand alone applications are programs which are linked with the Houdini
libraries. Unlike DSO's they must have a "main()" function defined. These
applications can easily read in the Houdini database and make modifications.
They will automatically pick up any extensions which have been installed
as well. The examples
contain two simple programs. One which mimics the Houdini
hscript application, and the other which illustrates
traversal of the node hierarchy.
The header files for the toolkit are stored in a database for quick access.
However, for development, the programmer will often need to see the
methods available for a specific class. The hcbrowse program is
the Houdini Class Browser. This is a program which has a graphical user
interface to browse classes. On the left hand side is a list of all the
classes. On the right hand side is the header file containing the selected
class. You can cut and paste between the text display and your favorite
editor.
This is a non-graphical application which will extract the named file
from the header file archive and display the contents on stdout.
This is a non-graphical application which will extract the named class
from the header file archive and display the contents on stdout.
This program can be used to package a DSO for export to foreign sites.
The program reads a configuration file and creates an archive file
which can be extracted at the foreign site by using the proto_install
command.
The configuration file must be called MANIFEST and
contains a list of files which should be installed. The structure of
the file is:
The filename should specify a file found in the directory where the
program is being run.
The target_path should specify the location within the standard
houdini path where the file should be located. For example, to
specify an icon file, the target_path should be specified as
"config/Icons/". The filename specification should not be
included in the path specification. For README files, this field is
ignored.
If the command specifies that the file should be executed, the
filename given will be extracted to $HOUDINI_TEMP_DIR and the program
will be started by running csh. Though the file is extracted into
a temporary directory, the current directory will be the target_path
specified in the third field.
The install_mode specifies the permissions for the file after
extraction.
Example 1:
hcustom [-g] [-s] [-i install_path] source.C [source2.C]
hcbrowse
hviewfile filename
hviewclass filename
proto_install
Example 2:
The file installHelp.sh would be run, with the current
directory set to the help/ sub-directory. The helpInstall.sh
file might look something like:
Operators |
Surface Operations |
Particle Operations |
Composite Operators |
Channel Operators
Material & Texture |
Objects |
Command and Expression |
Render Output |
Mantra Shaders |
Utility Classes |
Geometry Library |
Image Library |
Clip Library
Customizing UI |
Questions & Answers
477 Richmond Street West, Toronto, Ontario, Canada M5V 3E7