A rough calling scheme
out of date
This representation is intended to ease the understanding of the interdependance of the individual TRIPP routines for the growing commmunity of developpers. Beware that, as the code changes, this overview may not always be up to date. As several of you will only be interested in particular aspects at a given time, the listing is oriented at the actual usage of the routine rather than at some abstract design criterion. The hope is that most questions will already be answered by looking at the first two rows of the following table, which list the calls specific to a certain highest-level routine. The more frequently used subroutines to the right are roughly sorted by order of appearance; changing them will have an effect on more than one routine by which they are called and therefore requires a deeper overall understanding of the code (for which this listing is certainly no more than a mere staring point). In particular, the subroutines to the right might be nested, so that even if there is a cross indicating that this subroutine is called by a highest-level routine this may not happen directly but instead from somewhere to the "right" of it. Also, not all subroutines especially of the non-TRIPP parts may be listed, some which may be hidden in deeper levels most probably have escaped my attention so far.Clicking on the name of any routine leads you (provided you are a local user) to the local CVSweb entry of that routine so that its immediate history is easily accessible. That entry will in case of doubt be more authorative than what is listed here.
Finally, does anyone have any idea about how to rotate the names of everything to the right without having to create those ugly pictures and rotating those?
