As a matter of fact, all of the Tcl procs in the $HCIROOT tclprocs directory which are referenced in tclIndex file are referenceable in any site.
So you could put your own reusable, generic procs there and they would be available to all sites.
There is a caveat however. When you get a new release of Cloverleaf that directory is rebuilt with what is distributed and everything you put there is gone.
What we do is to use soft links from the $HCIROOT tclprocs directory to the directory where the procs actually exist (you still need to do a mktclindex in $HCIROOT tclprocs directory). The resident location for us is a site we created which is only used to be a repository for global objects. No real integrations are defined in this site.
We can discuss this further as to how we at M. D. Anderson Cancer Center accomplish global engine objects (more than just procs) at the User Conference next week.
I as of yet have never found a need for global Xlates – but the methodology we employ would allow that to occur.
Jim Kosloskey
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
