[vtk-developers] The new Tcl package structure

[Sebastien BARRE]

Hi dev

The dashboard might go crazy tonight as I updated hundreds of file to 
comply with the final Tcl packages stuff for VTK 4.0 :) This has been 
tested thoroughly but if everything goes wrong, I'll fix it tomorrow morning.

We switched from catch {load vtktcl} to a more sophisticated Tcl package 
structure.

Everything needed is explained in the README:
http://public.kitware.com/cgi-bin/cvsweb.cgi/~checkout~/VTK/Wrapping/Tcl/README

To sum up:

a) 99% of VTK users will now use:

	package require vtk

...and everything gets loaded.


b) Some users will definitely want to load the VTK API on a 
component-by-component basis. This is now possible. Example:

	package require vtkrendering

...and everything (including all others package like vtkimaging, vtkcommon, 
etc.) gets loaded to make the Rendering component work. In that case (and 
in all packages relying on Rendering), Tk is loaded too. In all other cases 
(vtkcommon, vtkfiltering, vtkgraphics, vtkimaging) a Tcl shell (tclsh) is 
good enough.


c) Users or developers relying either on the basic Tcl command interactor 
(press 'u' to see the .vtkInteract widget) or the simple bindings for the 
vtkTk*Widget widgets will *additionally* use:

	package require vtkinteraction

Many developers (including me) use their own (enhanced) Tcl command 
interactor so I thought it would be best not to include it in the 
vtkrendering package by default.


d) In some rare Tcl scripts, testers will additionally use:

	package require vtktesting

which provides the colors.tcl, backdrop.tcl, mccases.tcl stuff


That's it.
Thanks to people of CRD (Dan, Jim) for helping setting this up.Tcl